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 to Oz for WireGuard VPN exits #121

Open
dma opened this issue Sep 7, 2017 · 0 comments
Open

Add support to Oz for WireGuard VPN exits #121

dma opened this issue Sep 7, 2017 · 0 comments

Comments

@dma
Copy link
Contributor

dma commented Sep 7, 2017

One way to do it is similar to how we do it w/OpenVPN:

  • wg interface traffic gets clearnet in ferm.conf config, as with tun devices

  • oz launches wg at sandbox creation time, bridge created at sandbox creation time

  • specialized oz route-up gets invoked that creates routing table, routes, & policy rules that forward traffic to/from wg interface to bridge

  • openvpn client has options to reconnect on timeout and on SIGUSR1, route down is run, then route up is run again .. this would maybe need to be implemented for wireguard

  • need to deal with possibility of 1918 CIDR address space collisions

  • there may be a right way to do it: https://www.wireguard.com/netns/

@dma dma added the enhancement label Sep 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant