oh I have a container for that, and fear not it uses alpine
-
-
I think
@jpetazzo made this one: https://github.com/jessfraz/dockerfiles/blob/master/openvpn/README.md … and you can --net container:openvpn too1 reply 0 retweets 1 like -
That one adds server-provided ips/routes to the host, which is exactly what I'm trying to avoid.
2 replies 0 retweets 1 like -
Replying to @RichFelker @jessfraz and
I want to pick my own local & remote ips & and have openvpn snat/dnat them to whatever the server offers.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @jessfraz and
With openvpn never having opportunity/permissions to change routes on the host.
2 replies 0 retweets 0 likes -
Replying to @RichFelker @evanphx
If "in a container" is OK, then the link posted by
@jessfraz is gold, just remove `net:host` from Compose file …/…1 reply 0 retweets 0 likes -
Replying to @jpetazzo @RichFelker
if you don't even want that, then: create tun/tap device with tunctl (in uml-utilities), pass it to OpenVPN with --dev-node …/…
1 reply 0 retweets 0 likes -
Replying to @jpetazzo @RichFelker
and setup routes by hand (or setup OpenVPN to call a super locked down sudo script to do it). That should do it!
1 reply 0 retweets 0 likes -
Replying to @jpetazzo
I still don't see how to get opepvpn to do --client-nat to match the ips the remote offers.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
You could use the --ipchange flag to configure the IP addresses through a secured script. …/…
2 replies 0 retweets 0 likes
I don't want it to configure ips at all. I want it to --client-nat to remap the ip I choose to the remote-offered one.
-
-
Replying to @RichFelker
Sorry, I'm not familiar with --client-nat; it seems to be relatively recent :(
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.