|
|
|
|
|
by Someone
636 days ago
|
|
> At this point, it’s unclear exactly what is the issue So, is this a bug in Sequoia or a change that affects these low-level tools? If the latter, they may not like it, but that’s par for the game on MacOS. (Tried reading https://x.com/patrickwardle/status/1836862900654461270, referenced by sephamorr, but that link isn’t working for me) |
|
There are two «firewalls» in OS X: the IP packet filter (controlled pfctl) and the application level one (controlled by /usr/libexec/ApplicationFirewall/socketfilterfw). The one that is causing a lot of grief for upgraded users is the latter one.
The workaround is to remove/disable the app level blocking rules manually:
1. Get a list of app level firewall rules:
2. Locate the app(s) of interest.3. Disable the app specific rules:
Alternatively, the app can be removed from the list of application firewall rules: That will fix the problem, e.g. with Firefox (tested) or WireGuard (reported by somebody else above, untested).If a DoH DNS configuration is used, it also makes sense to explicitly whitelist the DoH provider in «pfctl» rules at IPv4/IPv6 and domain levels.