Skip to content

[codex] Update network troubleshooting peer checks - #763

Closed
rolfyone wants to merge 5 commits into
Consensys:mainfrom
rolfyone:update-troubelshooting-guide
Closed

[codex] Update network troubleshooting peer checks#763
rolfyone wants to merge 5 commits into
Consensys:mainfrom
rolfyone:update-troubelshooting-guide

Conversation

@rolfyone

@rolfyone rolfyone commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

What changed

  • Updated the network troubleshooting guide peer query to report TCP and QUIC counts for inbound and outbound peers.
  • Reworked the firewall guidance to separate TCP and QUIC troubleshooting paths.
  • Clarified that TCP uses --p2p-port by default and QUIC over UDP uses --Xp2p-quic-port, which defaults to 9001.

Why

The previous guidance used a single inbound/outbound peer count and described firewall fixes without clearly separating TCP from QUIC. This made it harder to diagnose cases where outbound QUIC peers exist but inbound QUIC peers are missing.

Validation

  • git diff --check
  • npm run build

The build completed successfully and reported existing broken-anchor warnings unrelated to this change.


Note

Low Risk
Changes are limited to documentation; no runtime or configuration behavior is modified.

Overview
Documentation-only updates so operators can tell TCP and QUIC P2P apart when debugging connectivity.

The network troubleshooting guide replaces a single inbound/outbound peer count with a jq query that reports TCP and QUIC counts per direction, and rewrites firewall guidance so missing inbound TCP vs QUIC peers map to --p2p-port (TCP) vs --p2p-quic-port (UDP, default 9001). Gateway notes now mention --p2p-advertised-quic-port.

IPv6 and CLI reference pages add --p2p-quic-port, --p2p-quic-port-ipv6, and advertised QUIC port options, including dual-stack default ports (9001 / 9091).

Reviewed by Cursor Bugbot for commit e3bad8b. Bugbot is set up for automated code reviews on this repo. Configure here.

@vercel

vercel Bot commented Jun 22, 2026

Copy link
Copy Markdown

@rolfyone is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.

@lucassaldanha

Copy link
Copy Markdown
Member

Just a reminder that we will need to update the docs after we promote quic to stable: Consensys/teku#10866

@vercel

vercel Bot commented Jun 26, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
doc-teku Ready Ready Preview, Comment Jun 26, 2026 5:32pm

Request Review

@rolfyone
rolfyone marked this pull request as ready for review June 28, 2026 22:55
@rolfyone
rolfyone requested a review from a team as a code owner June 28, 2026 22:55
@alexandratran

Copy link
Copy Markdown
Contributor

I've incorporated these changes into #768

@rolfyone rolfyone closed this Jun 29, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 29, 2026
@rolfyone
rolfyone deleted the update-troubelshooting-guide branch June 29, 2026 20:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants