-
-
Notifications
You must be signed in to change notification settings - Fork 234
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 option to only route LAN traffic #252
Comments
I require this too, as I've tried to do it via the config and can't seem to get it to work. This is useful for accessing services inside the machine the VPN is running on that aren't publicly exposed (i.e. database etc) |
After some messing around I managed to get it sort of working. I cloned the repo and edited
Run with This allowed me to connect to the OpenVPN then also access other docker containers that are running. I have an apache2 docker image running bound to 10.8.0.1:8080 which I can only access now when connected to the OpenVPN. I don't know if this is the right way to do it, or if it's secure, but I got it working - however I'm no expert. |
I'm switching to a docker openvpn-server solution from the router solution (Asuswrt-merlin) I have used earlier to access my home network remotely. This server had the option to only route LAN traffic, internet traffic or both. As I only used this to access my home network I quite enjoyed the feature of only routing LAN traffic.
Is it possible to add an option to only route LAN traffic? Not sure if it's as simple as adding an environment variable or if it would require more information such as subnet and/or netmask. In any case I would like to see this feature. :)
The text was updated successfully, but these errors were encountered: