reth
reth copied to clipboard
How to configure to use the intranet address?
Describe the bug
I want to create a private chain。 How to configure to use the intranet address? I found that if --disable-discovery is set, the intranet address can be used, but in this case, --bootnodes cannot be used to establish a connection.Currently, only external network addresses can be used to establish connections.
Steps to reproduce
I want to create a private chain。 How to configure to use the intranet address? I found that if --disable-discovery is set, the intranet address can be used, but in this case, --bootnodes cannot be used to establish a connection. Currently, only external network addresses can be used to establish connections.
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
reth release 1.0.3
What database version are you on?
reth release 1.0.3
Which chain / network are you on?
private
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
- [X] I agree to follow the Code of Conduct
not sure about discv4, but you can use LAN addresses and localhost with discv5. as long as the ENR address matches the source address in discv5, you're fine. so make sure that your machines only communicate over the interface of the ENR udp address. flags would be --disable-discv4-discovery and --enable-discv5-discovery, and remember to set the discv5 address explicitly with --discovery.v5.addr or --discovery.v5.addr.ipv6
i try , use --trusted-peers can connectted,but --bootnodes can not
which version are you on? should be fixed since https://github.com/paradigmxyz/reth/pull/9885
This issue is stale because it has been open for 21 days with no activity.
--disable-discv4-discovery --enable-discv5-discovery --discovery.v5.addr=127.0.0.1 --discovery.v5.port=9001 be config, and use --trusted-peers can connect,but --bootnodes can not in version 1.0.5. the same config in version 1.0.6 can not connect
This issue is stale because it has been open for 21 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.