Our tool finds that a client CoreGeth/ETCMCgethNode/v1.12.19-stable-78c91330/windows-amd64/go1.20.7 ends node discovery Ping message whose fromIP is 192.168.x.x. But the actual public IP of it is 94.226.x.x when our tool replys Ping to it. I guess the it is the NAT or the setupPortMapping that trigger the problem.
Our tool finds that a client
CoreGeth/ETCMCgethNode/v1.12.19-stable-78c91330/windows-amd64/go1.20.7
ends node discovery Ping message whose fromIP is192.168.x.x
. But the actual public IP of it is94.226.x.x
when our tool replys Ping to it. I guess the it is the NAT or the setupPortMapping that trigger the problem.See also,
Peer Info: