Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separate Listening and Discovery Ports in Node Configuration #712

Open
bgravenorst opened this issue May 24, 2021 · 1 comment
Open

Separate Listening and Discovery Ports in Node Configuration #712

bgravenorst opened this issue May 24, 2021 · 1 comment
Assignees
@bgravenorst

Comments

@bgravenorst
Copy link
Contributor

bgravenorst commented May 24, 2021 •
edited
Loading

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: hyperledger/besu#2308
@bgravenorst
Copy link
Contributor Author

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

@bgravenorst bgravenorst self-assigned this Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bgravenorst bgravenorst

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexandratran @bgravenorst