WG and AWG: Subnet IP setting change support #1323
Merged
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
kafeg
force-pushed
the
feature/wg_awg_subnet
branch
from
f28f164 to
719dd7a
Compare
Cleanup after self-review Fix IP generation with new subnet Self-review changes Self-review changes Fix WG connection setting page
kafeg
force-pushed
the
feature/wg_awg_subnet
branch
from
1440e1a to
ba5efe7
Compare
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.
Added new field VPN address subnet to the AWG and WG setting pages. This is a port of the same field from the OpenVPN config.
This is very useful in some cases, for e.g. when you have 2 VPN servers and need to be connected to both of them in the same time (on router for.e.g). So with different subnets you able to have correct routing.
I tested both: docker image successfully rebuilt and restarted on server with new subnets.