Separate Listening and Discovery Ports in Node Configuration

Open bgravenorst opened this issue 4 years ago • 1 comments

The p2p-port configuration file option can be used to configure the listening port for the node, which is used for both the TCP listening port and the UDP discovery port.

For enterprise setups using Kubernetes, users can use K8s services mapping as explained in https://besu.hyperledger.org/en/latest/HowTo/Find-and-Connect/Specifying-NAT/#kubernetes -> K8s services mapping + NAT = different ports possible.

This PR is to seperate the TCP listening port and UDP discovery port into separate CLI options.

See: https://github.com/hyperledger/besu/issues/2308

May 24 '21 04:05 bgravenorst

Completely slipped my mind regarding private Slack links. I've deleted it.

May 26 '21 03:05 bgravenorst