A new node can not discover all the active peers that boot node connected #164
Comments
|
ip <> peer ids |
|
The es-node uses UDP to broadcast and receive ENR and then puts the received ENRs (nodes) into the disc_v5 routing table. In Therefore, for nodes with public IP, ALL nodes can broadcast their ENR to ALL nodes through routing table, so their Peer number is relatively high. Nodes without public IP can only obtain other nodes through the routing table (only contain nodes with public IP), but cannot connect to other nodes which only have private IP, so there is no connection between private IP nodes. Other nodes: |
|
65.108.236.27 is one of our AX101 which has a public IP, but why it is in the "other nodes"? |
|
This is because it is run in the docker which does not have a public IP in the docker. |
|
I hope that the network problems existing in docker operation will be solved as soon as possible. |
|
Docker may be easy to deploy, but there is an extra layer of networking and storage, could there be a manual on best practices for running in docker. |
|
It is weird that the logs show you can only connect 1 peer, are you following the https://github.com/ethstorage/es-node/blob/main/GUIDE.md here to setup? maybe you can try VPN if you are based in China |
|
@qzhodl Can you please tell me how to use proxy on node, VPN We are going to use rpc and VPN will proxy all the traffic. |
|
I'm not sure if I've understood your question correctly. Are you asking how to set up the VPN to proxy only the es-node traffic, rather than all the traffic on your machine? I believe the ability to do this depends on the specific VPN software |
|
I don't really want to use a VPN, I also need the local network to use rpc and I already have a socks5 proxy available locally. how do I synchronize using proxy. |
|
from the log, the peer count drops to 0, it looks like it was caused by a network issue, a remote peer connected to it and then disconnected in a short time. and during the connection, the peer cannot successfully return the requested blobs in time. |
|
I tried to run the es-node in our office in Beijing without a VPN. The node can join the network and the discovery with UDP and P2P with TCP work well. Then I disconnect my computer, and after that, the es-node P2P peers disconnect and the peer count drops to 0 and the routing table in the discovery also be clear. |
|
I think the top priority is that we can support serving the data to other node when using docker. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On devnet-2, the bootnode was connected with 13 active peers, then we launched a new node, and it can only connect with 7 active peers. We may need to investigate the root cause.
The text was updated successfully, but these errors were encountered: