-
Notifications
You must be signed in to change notification settings - Fork 91
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
Windscribe is leaking IPv6 when running in inclusive split tunneling mode #206
Comments
Hi. Please give our recent beta release a try and let us know if the issue still exists for you. We've improved IPv6 behavior in the 2.13 release. However, please note that IPv6 will be blocked. We do not yet support IPv6 over the tunnel. Thanks! |
@bernerdad Inclusive mode is not working at all (no application is tunneled) so every application (even those which were supposed to be tunneled) are leaking IPv4 and IPv6. I understand how difficult it can be to implement split tunneling on Linux; I'm available to help with testing. |
Thank you for the testing update. All the engineers are away now for Christmas break. We'll revisit this in early January. Cheers! |
In the meantime, please ensure you are not trying to split tunnel a symlink or a launcher app. This often happens with e.g. firefox, where the .desktop file points to a launcher script that runs the actual binary. If this is the case, you'll need to use the + icon to add the correct binary manually. |
Describe the bug
While IPv4 is tunneled through Windscribe, IPv6 is leaked.
OS and app information:
To Reproduce
Steps to reproduce the behavior:
0. Make sure your internet connection is providing both IPv4 and IPv6
Expected behavior
Both IPv4 and IPv6 should be tunneled through Windscribe while currently only IPv4 is tunneled.
The text was updated successfully, but these errors were encountered: