-
-
Notifications
You must be signed in to change notification settings - Fork 51
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 in app allowedIps calculator #446
Comments
Hello! Please see the FAQ for how to resolve this. In the near future, I'm looking to add settings to the config screen to exclude private IPs from the tunnel w/custom ranges, but (for now) the directions in the FAQ are the best way to resolve this. |
Thanks for your reply. |
I propose to leave it open as long as the additional settings aren't yet implemented and close it only afterwards. That way people will know about the implementation having taken place. |
Sounds good. I've changes to name to better reflect what feature this one is requesting in order to be closed. |
Looks like my feature request #402. Simple toggle switch to allow LAN traffic. |
You are right. The only reason, why I opened a "BUG" was, because the configuration file should know anything about the devices paticular network. |
When a tunnel defines a default route, i.e. AllowedIPs = 0.0.0.0/0
The access to the local network is not possible anymore.
This is different on Linux desktop and at least the tunnel packets themselves MUST run throuch the local net.
No way to reach the local resources
Smartphone (please complete the following information):
To Reproduce
Just define a default route in conf file.
Expected behavior
Apart from the default route throght the tunnel an additional route to the local network.
The text was updated successfully, but these errors were encountered: