drafted extra network troubleshooting - #779
Merged
rolfyone merged 2 commits intoAug 7, 2026
Merged
Conversation
|
@rolfyone is attempting to deploy a commit to the Consensys Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexandratran
approved these changes
Aug 6, 2026
alexandratran
marked this pull request as ready for review
August 6, 2026 23:34
Contributor
Author
|
Thats a lot better, thankyou for that! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm not sure if this is the best way to represent this information but at least as a placeholder, having the query here to get the ports in use by a node at runtime can be particularly useful when debugging, so I feel like we should add it to this documentation.
I've left as draft because I don't feel like its exactly what we want, and I think someone may have cleaner ideas.
Note
Low Risk
Documentation-only changes with no runtime or security impact.
Overview
Improves P2P port documentation and network troubleshooting for operators debugging connectivity.
In
p2p-networking.md, the port table now includes default ports (9000TCP/discovery,9001QUIC) plus short guidance on listen vs advertised options, how discovery tracks--p2p-port, and IPv6 defaults (9090/9091).In
network.md, peering troubleshooting adds a Check ports flow usingGET /eth/v1/node/identity(curl/jq), samplep2p_addresses/discovery_addresses, and how multiaddr paths map to--p2p-port,--p2p-quic-port, and--p2p-udp-port, including advertised-port vs listen-port behavior. Inbound/outbound peer checks are split into their own section (still via/eth/v1/node/peers), with firewall guidance moved after that and default port numbers called out explicitly.Reviewed by Cursor Bugbot for commit df8c117. Bugbot is set up for automated code reviews on this repo. Configure here.