mirror of
https://github.com/AdguardTeam/AdguardKnowledgeBase.git
synced 2025-02-20 11:13:10 +08:00
Added info about Monterey issues
This commit is contained in:
Anastasiia Fedotova
parent
a640c1a8ae
commit
e88eea20c2
@ -1,18 +1,18 @@
|
||||
---
|
||||
title: 'Issues specific to macOS 11 Big Sur'
|
||||
title: 'Issues specific to macOS 11 Big Sur and later versions'
|
||||
taxonomy:
|
||||
category:
|
||||
- docs
|
||||
visible: true
|
||||
---
|
||||
|
||||
* [Currently existing problems (Big Sur 11.2)](#current)
|
||||
* [Compatibility with local proxies](#local-proxies)
|
||||
* [Configuring an upstream Shadowsocks proxy](#shadowsocks)
|
||||
* [Cofiguring an upstream Surge proxy](#surge)
|
||||
* [Compatibility with Cisco AnyConnect](#cisco)
|
||||
* [Compatibility with Flutter](#flutter)
|
||||
* [VPN apps with legacy API](#legacy-api)
|
||||
* [Currently existing problems](#current)
|
||||
* [Big Sur 11.6: currently existing problems](#BigSur)
|
||||
* [Compatibility with Cisco AnyConnect](#cisco)
|
||||
* [Compatibility with Flutter](#flutter)
|
||||
* [VPN apps with legacy API](#legacy-api)
|
||||
* [Monterey 12: currently existing problems](#Monterey)
|
||||
* [Compatibility with iCloud Private Relay](#private-relay)
|
||||
* [Already fixed problems](#fixed)
|
||||
* [Compatibility with Little Snitch 5](#little-snitch)
|
||||
* [Alternatives to Network Extension](#alternatives)
|
||||
@ -20,84 +20,18 @@ visible: true
|
||||
* [Enabling Kernel Extension in Big Sur](#kernel-extension)
|
||||
|
||||
|
||||
|
||||
|
||||
The newest version of macOS, **Big Sur**, has been released in late 2020. It introduces the new API, Network Extensions API to replace the old Kernel Extensions API. And it already causes some problems to many applications, AdGuard not being an exception. In this article we go over the known issues and possible ways to solve them.
|
||||
|
||||
<a id="current"></a>
|
||||
|
||||
## Currently existing problems (Big Sur 11.2)
|
||||
## Currently existing problems
|
||||
|
||||
Every year Apple releases a new version of macOS, introducing innovative solutions and adding new useful features. But some of them, such as Network Extensions API (Big Sur) or iCloud Private Relay (Monterey), causes some problems to many applications, AdGuard not being an exception. In this article we go over the known issues spesific to each macOS version and possible ways to solve them.
|
||||
|
||||
<a id="BigSur"></a>
|
||||
|
||||
## Big Sur 11.6: currently existing problems
|
||||
|
||||
These problems aren't fixed by Apple yet, or fixed only partially.
|
||||
|
||||
<a id="local-proxies"></a>
|
||||
|
||||
### Compatibility with local proxies
|
||||
|
||||
> Note: in Big Sur 11.1 (and newer macOS versions) AdGuard can filter local proxies (mostly) without any problems. If you encounter any issues in OS versions 11.1+, or if you're using Big Sur 11.0, remove the local proxy from System settings and configure an upstream proxy in AdGuard by following the instruction below.
|
||||
|
||||
> After Big Sur 11.3 update, the problems with local proxies came back. Apple will likely roll out a fix soon, and we're also working on a workaround. All required changes are already made to the [Nightly version](http://agrd.io/mac_nightly) of AdGuard for Mac.
|
||||
|
||||
To configure an upstream proxy in AdGuard for Mac in Big Sur, you need to go to *AdGuard menu -> Advanced -> Advanced Settings...*. Click on the *Value* area of the `upstream.proxy` setting to configure a proxy.
|
||||
|
||||
<img src="https://cdn.adguard.com/public/Adguard/kb/BigSur/problems/proxy_en.png" style="max-width: 650px;">
|
||||
|
||||
Enter a string that looks like `scheme://user:password@host:port`, where
|
||||
|
||||
* `scheme` is either `http`, `https`, `socks4` or `socks5`, depending on your proxy type.
|
||||
|
||||
>If you use `socks5` proxy type, set the value of the `upstream.proxy.socks5udp` setting to `true` to make AdGuard route UDP traffic to the proxy server.
|
||||
|
||||
* `user` and `password` are corresponding username and password of your proxy (if needed). Ignore either or both when not applicable
|
||||
* `host` is the IP address of your proxy server
|
||||
* `port` is the desired port number to be used by the proxy server
|
||||
|
||||
>Example: `socks5://localhost:6322` will configure a SOCKS5 local proxy that listens to port 6322 and doesn't require a username or a password.
|
||||
|
||||
Click *Apply* to make AdGuard route all traffic that went through it to the configured proxy server.
|
||||
|
||||
If you run into any problems, please contact our tech support: support@adguard.com.
|
||||
|
||||
<a id="shadowsocks"></a>
|
||||
#### Example 1: Configuring an upstream Shadowsocks proxy
|
||||
|
||||
Here's an example of how to configure an upstream proxy for [Shadowsocks](https://shadowsocks.org/en/index.html).
|
||||
|
||||
First of all, you need a working server side for your proxy. Most likely, to set it up, you would use a JSON file like this (`server` and `password` values were chosen randomly here):
|
||||
|
||||
```
|
||||
{
|
||||
"server":"111.222.333.444",
|
||||
"server_port":8388,
|
||||
"local_port":1080,
|
||||
"password":"barfoo!",
|
||||
"timeout":600,
|
||||
"method":"chacha20-ietf-poly1305"
|
||||
}
|
||||
```
|
||||
|
||||
>You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/en/config/quick-guide.html).
|
||||
|
||||
Then you'd have to install Shadowsocks client on your Mac. Make sure that you select 'Manual Mode' or 'Auto Mode' in its settings! The configuration won't work if you select 'Global Mode' (or 'Auto Mode' in Big Sur versions prior to 11.1).
|
||||
|
||||
<img src="https://cdn.adguard.com/public/Adguard/kb/BigSur/problems/shadowsocks.png" style="max-width: 350px;">
|
||||
|
||||
Now go to *AdGuard menu -> Advanced -> Advanced Settings...* and set the *Value* area of the `upstream.proxy` setting to `socks5://localhost:1080`. Notice that you need to use "local_port" value from the JSON file here.
|
||||
|
||||
Because Shadowsocks uses SOCKS5, you also need to set the value of the `upstream.proxy.socks5udp` setting in AdGuard Advanced Settings to `true` to make AdGuard route UDP traffic to the proxy server.
|
||||
|
||||
<a id="surge"></a>
|
||||
#### Example 2: Configuring an upstream Surge proxy
|
||||
|
||||
In Big Sur v11.1+, there are no known conflicts between AdGuard and Surge proxy. If you are using an older version of Big Sur (prior to 11.1), check that **System Proxy** in the bottom right corner is disabled. Otherwise, Surge won't work with AdGuard. On the other hand, **Enhanced Mode** can be enabled without causing a conflict in any Big Sur version.
|
||||
|
||||
<img src="https://cdn.adguard.com/public/Adguard/kb/BigSur/problems/surge.png" style="max-width: 800px;">
|
||||
|
||||
Now go to *AdGuard menu -> Advanced -> Advanced Settings...* and set the *Value* area of the `upstream.proxy` setting to `socks5://localhost:6153` or `http://localhost:6152`, depending on which type of proxy you want to use. Notice that you need to use **port** value that's indicated in the **Events** area of the **Activity** tab in your Surge client.
|
||||
|
||||
If you chose SOCKS5 protocol, you also need to set the value of the `upstream.proxy.socks5udp` setting in AdGuard Advanced Settings to `true` to make AdGuard route UDP traffic to the proxy server.
|
||||
|
||||
|
||||
<a id="cisco"></a>
|
||||
|
||||
### Compatibility with Cisco AnyConnect
|
||||
@ -130,6 +64,32 @@ Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any
|
||||
|
||||
<img src="https://cdn.adguard.com/public/Adguard/kb/BigSur/problems/legacy-api.png" style="max-width: 650px;">
|
||||
|
||||
<a id="Monterey"></a>
|
||||
|
||||
## Monterey 12: currently existing problems
|
||||
|
||||
These problems aren't fixed by Apple yet, or fixed only partially.
|
||||
|
||||
<a id="private-relay"></a>
|
||||
|
||||
### Compatibility with iCloud Private Relay
|
||||
|
||||
By default, AdGuard uses the "default route" which disables iCloud Private Relay.
|
||||
|
||||
Currently, AdGuard and iCloud Private Relay cannot work at the same time. AdGuard has no ability to block ads because iCloud Private Relay encrypts traffic before AdGuard can filter network connections. When iCloud Private Relay is active, any filtering (including local filtering) becomes impossible. Thus, AdGuard can't filter traffic or perform DNS filtering in Safari.
|
||||
|
||||
For a deeper understanding of this problem, follow the link and read [the article](https://github.com/AdguardTeam/AdguardKnowledgeBase/blob/master/03.macos/05.solving-problems/07.icloud-private-relay/docs.en.md).
|
||||
|
||||
**Recommended solution**
|
||||
|
||||
We recommend using AdGuard together with a more traditional VPN service such as [AdGuard VPN](https://adguard-vpn.com/).
|
||||
|
||||
**Alternative solution**
|
||||
|
||||
You can prevent AdGuard from using the "default route" by disabling the "default route". It can be done via Advanced Settings -> ```network.extension.monterey.force.split.tunnel```.
|
||||
|
||||
<img src="https://cdn.adguard.com/public/Adguard/kb/MAC/mac_adguard_advanced_settings.png">
|
||||
|
||||
|
||||
<a id="fixed"></a>
|
||||
|
||||
@ -150,13 +110,13 @@ Needs to be said that this problem can't be solved by disabling connections moni
|
||||
|
||||
## Alternatives to using a Network Extension
|
||||
|
||||
It's impossible to foresee each and every possible problem that can pop up in Big Sur, there are countless various hardware/software and settings configurations. If you face any compatibility issues, please contact our support team, but feel free to try one of these workarounds first:
|
||||
It's impossible to foresee each and every possible problem that can pop up in Big Sur or Monterey, there are countless various hardware/software and settings configurations. If you face any compatibility issues, please contact our support team, but feel free to try one of these workarounds first.
|
||||
|
||||
<a id="automatic-proxy"></a>
|
||||
|
||||
### Using "Automatic proxy" filtering mode
|
||||
|
||||
If you face problems in Big Sur which can't be resolved by any of the methods above, you can try switching AdGuard to *Automatic proxy* mode.
|
||||
If you face problems in Big Sur or Monterey which can't be resolved by any of the methods above, you can try switching AdGuard to *Automatic proxy* mode.
|
||||
|
||||
1) Open AdGuard's menu.
|
||||
2) Select *Preferences...*.
|
||||
@ -173,9 +133,9 @@ Now AdGuard has automatically added a **.pac** file to your Mac's network settin
|
||||
|
||||
<a id="kernel-extension"></a>
|
||||
|
||||
### Enabling Kernel Extension in Big Sur
|
||||
### Enabling Kernel Extension in Big Sur and Monterey
|
||||
|
||||
By default AdGuard uses Network Extension framework in Big Sur as the old Kernel Extension framework is disabled there. This can cause some compatibility problems, but to enable Kernel Extension back, you need to disable System Integrity Protection (SIP) first. To disable SIP, follow this instruction:
|
||||
By default AdGuard uses Network Extension framework in Big Sur and Monterey as the old Kernel Extension framework is disabled there. This can cause some compatibility problems, but to enable Kernel Extension back, you need to disable System Integrity Protection (SIP) first. To disable SIP, follow this instruction:
|
||||
|
||||
1) Click the *Apple symbol* in the Menu bar.
|
||||
2) Click *Restart…*
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user