feat(p2p): allow listener bind to differ from the tor forward address #5357
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.
Description
Add
p2p.tor.listener_address_override
config to allow a listener bind address that differs from the forward_address for incoming tor connections.Motivation and Context
This is useful for docker setups where containers are addressed by DNS. In this case, the forward_address would be
/dns4/my_base_node/tcp/xxxxx
and thelistener_address_override="/ip4/0.0.0.0/tcp/xxxxx"
How Has This Been Tested?
Manually by setting the override to
"/ip4/0.0.0.0/tcp/12345"
and the forward_address to/dns4/localhost/tcp/12345
What process can a PR reviewer use to test or verify this change?
Breaking Changes