-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Killswitch Broken under ProtonVPN w/ WireGuard #26
Comments
Hi @mattgeowild interesting because the rules allow any traffic from the peer IP
and then run:
Is just a guess, because the rules are already allowing all on |
Hi @nbari, unfortunately it looks like that isn't working either |
hi @mattgeowild did you add:
Can you share your |
Hi @mattgeowild , modify the file
if you run again just in case, to reset your firewall rules run:
|
Killswitch stopped working for me as soon as I updated to the new version of the ProtonVPN MacOS client, which adds WireGuard capabilities -- and I don't see any way to disable it.
First, it won't pick up the VPN IP so enabling it without providing the IP with
-ip
immediately blocks all traffic. Second, when you do provide the IP address it seems to work only 20-ish percent of the time -- it shows a PEER IP address but it still blocks all traffic. I've verified this is the correct IP. When I disable the killswitch, internet works again.The text was updated successfully, but these errors were encountered: