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

WireGuard use-case: route all traffic through a WireGuard tunnel #52

Open
stapelberg opened this issue May 28, 2020 · 0 comments
Open
Labels
enhancement New feature or request good-for-stream https://www.twitch.tv/stapelberg

Comments

@stapelberg
Copy link
Contributor

Raw WireGuard support was added in #14, this issue covers a specific use-case.

At a high level: when running an event, we might want to not use the uplink directly, but rather use the uplink to establish a WireGuard tunnel and then route all outgoing traffic through the WireGuard tunnel instead. Semantically, this means uplink0 should be a WireGuard tunnel, and the network interface that’s currently uplink0 should be transit0 and only allow WireGuard traffic.

Side note: this would also be beneficial for https://gokrazy.org/ when using unencrypted WiFi networks. Depending on how the implementation goes, we should probably file a separate issue over there to make the result work on gokrazy, too, not just router7.

@stapelberg stapelberg added enhancement New feature or request good-for-stream https://www.twitch.tv/stapelberg labels May 28, 2020
@stapelberg stapelberg mentioned this issue May 28, 2020
5 tasks
stapelberg added a commit that referenced this issue Jun 6, 2022
Useful for routing IPv6 subnets through a WireGuard tunnel.

related to #52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good-for-stream https://www.twitch.tv/stapelberg
Projects
None yet
Development

No branches or pull requests

1 participant