Skip to content
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 support for randomly chosen *.ovpn files #22

Closed
wants to merge 1 commit into from

Conversation

@cybrnook
Copy link

cybrnook commented Jul 7, 2019

Add ability to have docker container randomly choose from multiple .ovpn files located in /config/openvpn. This is good for moving your location from time to good to provide a better sense of protection while behind a VPN. As well, server are known to become saturated at times, so a potential restart of your container would solve this issue by rotating you to another.

This is a simple/graceful solution to implement server rotation without attempting to support "remote-random" which is integrated into openvpn, however would require a larger rework of the existing scripting logic, which is unnecessary.

To use, include multiple *.ovpn files from your current VPN provider into the /config/openvpn folder. On container restart, one of the *.ovpn files will be randomly chosen for use, using the credentials stored in your docker template.

Signed-off-by: Hans Geiblinger cybrnook2002@yahoo.com

Add ability to have docker container randomly choose from multiple .ovpn files located in /config/openvpn. This is good for moving your location from time to good to provide a better sense of protection while behind a VPN. As well, server are known to become saturated at times, so a potential restart of your container would solve this issue by rotating you to another.

This is a simple/graceful solution to implement server rotation without attempting to support "remote-random" which is integrated into openvpn, however would require a larger rework of the existing scripting logic, which is unnecessary.

To use, include multiple *.ovpn files from your current VPN provider into the /config/openvpn folder. On container restart, one of the *.ovpn files will be randomly chosen for use, using the credentials stored in your docker template.

Signed-off-by: Hans Geiblinger <cybrnook2002@yahoo.com>
@ljmerza

This comment has been minimized.

Copy link

ljmerza commented Aug 4, 2019

Any updates for this pr? I'd like to see this feature. Thanks!

@cybrnook

This comment has been minimized.

Copy link
Author

cybrnook commented Aug 4, 2019

@ljmerza - @binhex and I had a brief conversation about this ability here: https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=757244

While my PR would work fine for what we want to do. He is nervous about users with potentially misconfigured systems I think (more than 1 x ovpn file inside of the openvpn folder?). So he expressed that he would more prefer to see this go the direction of utilizing support for remote-random within the ovpn file. That would be a lot more work on my end (more than I am willing to do) since his current logic modifies existing ovpn files and strips all other occurrences of a remote server from the given ovpn file, would make it difficult to retain multiple remote servers for your pool. So it would be more digging to clean up his current code to support that.

As an alternative, I just wrapped my unraid server as a whole inside a VPN tunnel......

@binhex binhex closed this Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.