-
-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add killswitch to prevent clearnet leaks #181
Comments
It's already this way with on-demand. No kill switch needed. |
Sorry for disturbing you, but have you checked this? Because as I know, on-demand on iOS is not a killswitch and can leak. This is an example of on-demand leak ike2-2019. |
Which is about Apple’s IPSec, so apples and oranges here. Have you had any leak with this app? Cause if you report an issue, you should at least prove that you had the issue. |
OK, let's dig into this. Using AirVPN UDP profile. Connect On-Demand is turned on. Steps to reproduce:
$ sudo tcpdump -n -i en0 udp port 53 tcpdump
Diagnostics
|
Fair enough! |
Does v2.0.0 suffer from this issue? |
Self note: https://developer.apple.com/documentation/networkextension/nevpnprotocol/3131931-includeallnetworks @MahdiNazemi not sure if this test is relevant. |
@x13a hey, can you please share why you closed this issue on Jul 23? It's quite important, thanks. |
Agreed this is a really important task. |
Hey @keeshux , I was in a bad mood and closed all the issues I have opened. Sorry for this. |
For the macOS version it will be very useful to add
killswitch
. Many VPN providers have this builtin in their clients. Main purpose of this to pass traffic only through VPN and block through clearnet, except DNS resolution for VPN only, and local networks traffic.The text was updated successfully, but these errors were encountered: