AdguardTeam / AdGuardVPNForMac

AdGuard VPN Mac app open bug tracker
https://adguard-vpn.com/
37 stars 5 forks source link

AdGuard VPN is not working along Sophos Home Premium installed #7

Open sergerosenthaler opened 3 years ago

sergerosenthaler commented 3 years ago

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

Issue Details

Expected Behavior

If clicking on "Connect" a VPN tunnel should be established.

Actual Behavior

Clicking on "Connect" nothing happens. After that browsing is no longer possible and device must be restarted.

Screenshots

Screenshot:

Additional Information

I assume this is the problem. https://support.home.sophos.com/hc/en-us/articles/360000129706-Known-issues-in-Sophos-Home-

macOS 11 - Big Sur - Network filtering applications such as Little Snitch or VPN software running in tandem with Sophos Home or other software with network filtering capabilities, may trigger errors or not work at all. If you experience issues with Sophos Home or another network-based program, we recommend either disabling or removing the other program and re-testing functionality. Technical details can be found below: https://community.sophos.com/intercept-x-endpoint/big-sur-eap/f/recommended-reads/124249/big-sur-eap-known-issues-list

ameshkov commented 3 years ago

As I recall, there's a similar issue with AdGuard as well. It seems that using any network filtering software alongside Sophos is quite problematic.

Probably, if adding IPSec support (which is supported natively by macOS) may help so let's keep this open for a while.

sergerosenthaler commented 3 years ago

@ameshkov This problem still persists. Right now, AdGuard VPN vor macOS is useless for me.

ameshkov commented 3 years ago

@sergerosenthaler we're planning to add an option to use native IPSec in the future versions, but meanwhile I suggest you reporting this issue to Sophos as well. The way they opted to filter traffic on macOS makes it incompatible with lots of software, there're better ways (see AG, Little Snitch, etc, we all somehow manage).

sergerosenthaler commented 3 years ago

@sergerosenthaler we're planning to add an option to use native IPSec in the future versions, but meanwhile I suggest you reporting this issue to Sophos as well. The way they opted to filter traffic on macOS makes it incompatible with lots of software, there're better ways (see AG, Little Snitch, etc, we all somehow manage).

@ameshkov Did this, Sophos Home request (85602). Informed Sophos that they should get in touch with you.

sergerosenthaler commented 3 years ago

@ameshkov Following, the answer I got and a workaround if you have other affected users: Answer Hi Serge,

I hope you are well.

I have taken over ticket 85602 where you are having issues browsing when connected to AdGuard VPN and Sophos Home's Web Protection and Malicious traffic detection enabled.

This issue looks similar to an issue we have identified with another VPN software that should be addressed in Sophs Home version 10.2.2 I will talk with the developers to confirm and get back to you with this clarification and a timeline.

Thanks for identifying this issue and for your patience while we investigate. Regards, Mark - Sophos Home Support

Workaround Hello Serge,

Thank you for your patience.

I reviewed AdGuard VPN and I have found the following workaround for it.

To use AdGuard VPN along with Sophos Home:

Open Sophos Home dashboard [my.sophos.com] Log in to your Sophos Home account. Select the computer, go to the Protection tab Turn off "Malicious Traffic detection" Under "Web" tab, turn off "Web Protection" Reboot and connect the VPN.

Please let me know if that workaround resolves your issue.

I look forward to hearing from you. Regards, Jainam - Sophos Home Support

sergerosenthaler commented 3 years ago

This has been solved by Sophos with release of a new version of Sophos Home.

ameshkov commented 2 years ago

Awesome!

sergerosenthaler commented 2 years ago

@ameshkov Please reopen this issue. The problem is back with the latest version of Sophos Home Premium 10.2.2a2

ameshkov commented 2 years ago

@sergerosenthaler I did, but it probably needs to be reported to Sophos again:(