Skip to content
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
3 commits merged into from
Apr 20, 2021

Conversation

tomaka
Copy link
Contributor

@tomaka tomaka commented Apr 20, 2021

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).

@tomaka tomaka added A0-please_review Pull request needs code review. B5-clientnoteworthy C1-low PR touches the given topic and has a low impact on builders. labels Apr 20, 2021
client/cli/src/params/network_params.rs Outdated Show resolved Hide resolved
Co-authored-by: Andronik Ordian <write@reusable.software>
@tomaka
Copy link
Contributor Author

tomaka commented Apr 20, 2021

bot merge

@ghost
Copy link

ghost commented Apr 20, 2021

Trying merge.

@ghost
Copy link

ghost commented Apr 20, 2021

Bot will approve on the behalf of @tomaka, since they are a team lead, in an attempt to reach the minimum approval count

@ghost ghost merged commit ebf2591 into paritytech:master Apr 20, 2021
@tomaka tomaka deleted the tweak-allow-non-globals branch April 20, 2021 13:42
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants