Post

Replies

Boosts

Views

Activity

Reply to Using NWPathMonitor to catch VPN connections
Thanks Matt. I was aware of ifconfig and aware that there are three utun* interfaces running by default on Big Sur. Most seem to be Apple related. scutil --nc list  doesn't seem to return anything for two VPNS I have tried, TunnelBlick and Viscosity. I get: Available network connection services in the current set (*=enabled): and then nothing. for now I am making the assumption that Apple services using the utun interfaces are ip6 and most VPNS are on ip4 so I test for           "State:/Network/Interface/utun\(n)/IPv4" I listen on: State:/Network/Global/IPv4, which seems to work for all cases of network or interface changes However I am stuck as how to recognise a ip6 VPN. I can surely catch a new iP6 but it might be an additional Apple service. There's no way, as far as I can see, to differentiate between an Apple service running on the network interface and third party services.
Jan ’21
Reply to DNS Proxy on Mac is enabled but not running.
Do you mean "now" creating a Network System Extension? I did actually look at the console log. As it happens I opened a TSI because money is no object and I have a few lying around for free anyway. If we solve it for general we could post it here. Thanks for the information on the os_log. Is that also visible in the Console.app in the Devices streaming part?
May ’21
Reply to Network Extension and Safari DNS
The extension can work on both but I see the safari issue on macOS. I don't think that the NEDNSProxyProvider will work since the decision on what is blocked and what is not blocked is made by the server side and is often quite dynamic. Anyway not confident that there is a fix in doing that, as safari should really be showing our blocked site anyway. If I do this curl http://skynews.com > skynews.html; open skynews.html I get the blocked page. Only safari, of the four browsers I test only safari shows the issue.
Sep ’21
Reply to Xcode 13.2 update is stuck
This is pretty appalling alright. Its the lack of feedback that is most annoying. I can tell that launch daemon is trying to unzip the downloaded package, which I can see in the Finder, but it takes so long that it is impossible to know it is is stuck or not. The logs are not any good. All I can see is that the last log was that installD was extracting the file, and is running at between 150-300% of CPU. When I sample it is in somewhere in deflate or some copy method. I suspect I can just wait around, that is more than the 30 minutes and counting since it actually downloaded. I see a lot of this: 1995 BOMCopierCopyWithOptions (in Bom) + 1952 [0x1aa886154] + 1995 _copyFromCPIO (in Bom) + 968 [0x1aa8a795c] + 1995 _copyDir (in Bom) + 1708 [0x1aa88a6e0] + 1995 _copyFromCPIO (in Bom) + 968 [0x1aa8a795c] Most of the solutions here are to download again, but I have a slow enough connection. Update: I tried to kill launchD in the hope of running the PKG which I could find from running open /var/log/install.log and see what was being extracted, but get this. If you kill the app, ie launchD, that is not clearly working it will deliberately delete that PKG. They have literally put in code on a SIGTerm to delete something that will maybe help you fix the issue. Maybe to be fair that is to recover disk space, however it means I have to download again. Grrr.
Apr ’22