WIP: Add NAT support through the use of /advertise(Addr|Port)/ #50
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.
Fixes #8
This could benefit some hypothetical cloud-to-cloud situation that had to be communicated though internet, e.g. interconnect from AWS to GCP without using their overpriced VPN service.
By default the advertise address would be
the same as the final bind addressanything you want if and only if it is a valid IP address otherwise empty to keep track with the default in memberlist, and advertise port is not yet changeable (implied by ClusterPort). The behavior is the same as before if you don't use the advertise address.This is not yet finished due to missing tests