You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our tool has identified a client that utilizes the zero IP address as the sender IP in the Ping message of the node discovery protocol. This indicates a potential issue with the NAT port mapping code, suggesting that it may not update the client IP correctly. However, the actual IP (34.38.x.x) obtained from the UDP socket is a valid public IP address. It's worth noting that this situation is uncommon, as only 5 out of thousands of Nethermind peers exhibit this issue.
Additionally, I have observed that Geth experiences a similar issue, although it only affects the first ping message in rare circumstances. see ethereum/go-ethereum#29713
Our tool has identified a client that utilizes the zero IP address as the sender IP in the Ping message of the node discovery protocol. This indicates a potential issue with the NAT port mapping code, suggesting that it may not update the client IP correctly. However, the actual IP (34.38.x.x) obtained from the UDP socket is a valid public IP address. It's worth noting that this situation is uncommon, as only 5 out of thousands of Nethermind peers exhibit this issue.
Additionally, I have observed that Geth experiences a similar issue, although it only affects the first ping message in rare circumstances. see ethereum/go-ethereum#29713
Reth and Besu have been aware of this issue. paradigmxyz/reth#8122 hyperledger/besu#6439 hyperledger/besu#6225
peer Info:
The text was updated successfully, but these errors were encountered: