This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Enable --no-private-ipv4 by default for live chains #8642
Merged
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.
The
--no-private-ipv4
option is now enabled by default for "live" chains such as Westend, Rococo, Kusama, and Polkadot.Consequently, I've added a new
--allow-private-ipv4
option, which forces the opposite.Concretely speaking, this means that nodes will no longer connect to any IP address that is considered as private (such as
10.0.0.1
).