Eugene Kabanov
Eugene Kabanov
Everything what falls into ``` error "Exception in accept loop, exiting", exc = exc.msg ``` looks like serious error, and `nimbus` consumers actually asking what the error is. But this...
Could you please provide more information? There is no reason for VC to request `genesis` state from BN. But anyway i do not see from your issue that something requests...
`identify` protocol is not enabled in `nimbus` and not enabled in `lighthouse`. And identity is actually match what both libp2p and discv5 using. `AnyAddress` just got expanded explicitly.
Also all the corresponding information is obtained via libp2p and discovery5 interfaces. So previously we had ``` { "p2p_addresses": [ "/ip4/0.0.0.0/tcp/9011/p2p/16Uiu2HAmQEmCoEfKQ7ZdPyw1vkMYPLfosfksRUJwssvyDzAosGgm" ], "discovery_addresses": [ "/ip4/185.181.230.77/udp/9011/p2p/16Uiu2HAmQEmCoEfKQ7ZdPyw1vkMYPLfosfksRUJwssvyDzAosGgm" ] } ``` Now we...
So what is doing current PR. For `p2p_addresses`. 1. Expands all the addresses which are `0.0.0.0` or `::` to corresponding interface addresses. 2. Obtains observed addresses (which should be received...
This PR does not replacing any old logic, it add more sources of information and eliminates `0.0.0.0` reports.
Yep, it supposed to fix the issue, but i have not checked it yet.
This PR was superseded by #6422
This is `libp2p` known issue and probably limitation.
Usually developers prefer to use `0.0.0.0` which forces OS to bound server to all available interfaces. But this comes with limitation that when you will request local address of bound...