-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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.
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
Change p2p default port to 8084 #21162
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
@@ -40,7 +40,7 @@ pub struct P2pConfig { | |||
} | |||
|
|||
fn default_listen_address() -> SocketAddr { | |||
"0.0.0.0:8080".parse().unwrap() | |||
"0.0.0.0:8084".parse().unwrap() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great context. Do you have opinions on how this should be updated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't think of any issues this would cause for an operator who isn't explicitly setting this value
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And Sui node RPC port uses the 8080 port as well.
sui node rpc uses 9000, right? or is 8080 used for something else
Updated the description. I meant the sui/crates/sui-config/src/node.rs Line 517 in 01257bd
|
Description
8084 is mentioned to be the default p2p port in docs: https://docs.sui.io/guides/operator/validator-tasks#connectivity
And validator / transaction RPC port defaults to 8080 already.
So changing the default p2p port from 8080 to 8084 in
P2pConfig
.I believe the change is backward compatible but lmk otherwise.
Test plan
CI
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.