Always listen on both IPv4 and IPv6 sockets on server side. #129
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.
What this PR does / why we need it:
Always listen on both IPv4 and IPv6 sockets on server side.
To simplify the configuration by removing unnecessary options and make it easier to support dual-stack configurations on server side with single-stack on client side, the vpn server is configured to always listen on both IPv4 as well as IPv6 sockets. Unfortunately, this is achieved via the unintuitive
tcp6-server
option. Looking at it via tools likenetstat
orss
, it looks like there is only an IPv6 socket, but you can also address it via IPv4.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: