Feature: add linux network namespace support for wireguard #189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a new wireguard configuration 'WGNamespace', if exist, the wireguard profile will configure in the sub network namespace
|
At first glance this looks excellent, thanks! I'll read up on network namespaces and will come back with a proper review later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Wireguard document here
So I add a new configure option 'WGNamespace', if exist, the wireguard will be moved into the sub interface
Here is my test environment, built by GNS3, with archlinux qemu vm, base-1 and base-2 are peers
Configure origin
Configure with 'WGNamespace=subnet'
