reth icon indicating copy to clipboard operation
reth copied to clipboard

How to configure to use the intranet address?

Open theone-pang opened this issue 1 year ago • 3 comments

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

theone-pang avatar Jul 30 '24 07:07 theone-pang

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

emhane avatar Jul 30 '24 15:07 emhane

i try , use --trusted-peers can connectted,but --bootnodes can not

theone-pang avatar Aug 05 '24 06:08 theone-pang

which version are you on? should be fixed since https://github.com/paradigmxyz/reth/pull/9885

emhane avatar Aug 05 '24 19:08 emhane

This issue is stale because it has been open for 21 days with no activity.

github-actions[bot] avatar Aug 27 '24 01:08 github-actions[bot]

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

theone-pang avatar Sep 02 '24 08:09 theone-pang

This issue is stale because it has been open for 21 days with no activity.

github-actions[bot] avatar Sep 25 '24 02:09 github-actions[bot]

This issue was closed because it has been inactive for 7 days since being marked as stale.

github-actions[bot] avatar Oct 03 '24 02:10 github-actions[bot]