Port forwarding for server #69
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
|
LGTM. Thanks Ilya, Merging your PR... |
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.
In my case I am using wireguard behind reverse proxy. This PR contains implementation of setting.EndpointAddress parsing, so that client config contains desired hostname and port, if EndpointAddress string contains ":int" suffix. Default behavior maintained otherwise.
Usage:
Fill Endpoint Address field in Global Settings with hostname:port format e.g. example.com:443
ListenPort setting in server configuration will remain as set in Wireguard Server page, but example.com:443 will be used as Endpoint of server's peer in every client config.