Discovery port changed after starting geth about go-ethereum HOT 3 OPEN

There is an internal prediction process that attempts to figure out the node's own address based on statements from other nodes. We have this process in order to guess the NATed endpoint of the node. Looks like either the prediction isn't working in your case.

from go-ethereum.

This issue does look like a potential bug in Geth. In the situation you describe, Geth is showing the wrong discovery port in admin.nodeInfo, which may cause peers to not recognize your node correctly.

To fix this issue, first make sure you are using the latest version of Geth. Sometimes problems are fixed in older versions. Also, check Geth's logs for any error messages or warnings about discovered port changes. This may help determine the root cause of the problem.

Then when starting Geth, try to use the --discovery.port parameter to manually set the discovery port to see if you can keep the port unchanged stably.

from go-ethereum.

--discovery.port can help. good example

from go-ethereum.