Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Solve the --no-private-ipv4 situation #8490

Closed
tomaka opened this issue Mar 30, 2021 · 3 comments
Closed

Solve the --no-private-ipv4 situation #8490

tomaka opened this issue Mar 30, 2021 · 3 comments

Comments

@tomaka
Copy link
Contributor

tomaka commented Mar 30, 2021

The --no-private-ipv4 option really should be enabled by default for live chains, but if we always enable it by default, then starting a chain locally wouldn't work anymore.
@coriolinus
Copy link
Contributor

Would it be reasonable to enable --no-private-ipv4 by default unless --dev is present?

@bkchr
Copy link
Member

bkchr commented Mar 30, 2021 •
edited
Loading

No. --dev is single node anyway and local test networks don't use --dev.

@tomaka
Copy link
Contributor Author

tomaka commented Apr 27, 2021

Done in #8642

@tomaka tomaka closed this as completed Apr 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tomaka @bkchr @coriolinus