Repository navigation
docs: troubleshoot missing peer routes - #226
Merged
Merged
Conversation
Add a troubleshooting section for active route liveness: reading `doublezero routes status`, the inbound and outbound UDP 44880 fixes, what each per-peer state means, and how to opt out. The daemon log and the CLI link to its anchor.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
`down (remote_down)` means the same as `init`: the peer does not hear this host. A manual rp_filter value lasts until doublezerod recreates the tunnel.
The routes status warning now asks the user to check that UDP 44880 is allowed, and the page notes that with few peers the fault may be on their side.
doublezero routes status now names the route count Peers, and with no action but missing routes it says that this host appears healthy and needs no action.
doublezero routes status now reads starting for the first 2 minutes with no session up and no route installed, and says the host appears healthy only with a session up. The opt-out keeps passive liveness on, so this host keeps answering probes.
doublezerod now warns when no session has been up for 2 minutes and at least one desired route is missing from the kernel, rather than when no route is installed.
ben-dz
marked this pull request as ready for review
November 5, 2026 21:53
nikw9944
self-requested a review
November 6, 2026 01:07
nikw9944
approved these changes
Nov 6, 2026
nikw9944
left a comment
nikw9944
left a comment
Contributor
There was a problem hiding this comment.
Compared the four routes status examples and the status warning with the routes.rs and status.rs tests in merged malbeclabs/doublezero#4490, and the flags, hold-down cap and rp_filter value with main.go and netlink.go on upstream main; they match.
Docs & comments (non-blocking)
docs/support/troubleshooting.md:386— This overstates withdrawal: routes to peers running passive liveness, and all routes on IBRL with an allocated IP, stay installed when the peer stops answering, so that traffic does not move to the public internet. Most peers stay passive until they upgrade, and line 450 makes the same claim.docs/support/troubleshooting.md:452— An older client does not by itself causeno reply: clients since v0.8.3 default to passive liveness and answer probes. Readers will write off a peer's blocked port as the rollout.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
### Issue: routes to some or all peers are missingtodocs/support/troubleshooting.md, for the active route liveness thatdoublezerodturns on by default in the next client release. Keep the anchor#issue-missing-peer-routesas is: thedoublezerodWARN,doublezero routes status, and thedocsfield of the session logs link to it.Fixes malbeclabs/infra#3603. This documents malbeclabs/doublezero#4490, which has merged. Merge this when client v0.47.0 ships, because the page goes live on merge.
Pre-merge TODO
mainbefore v0.47.0 ships, update the quotes here.Notes for review
outboundreads "this host hears peers, but peers do not hear it", not "a session is ininit". The daemon also reportsoutboundwhen sessions sit indownafter this host heard a peer.solana/ibrl/publish.mdinline. The IBRL runbook is excluded from the site, so a link to it would break.setup.mddoes, and warns that this page's environment switch rewrites that file, which would drop the flag.translations.jsonare untouched.Verification
mkdocs buildwith the pinned requirements passes with only the allowed i18n warning, and the built page has exactly oneid="issue-missing-peer-routes". Vercel redirects/support/troubleshootingto the trailing-slash URL with a 308, so the daemon's link resolves. Not verified: the page against a running daemon or real CLI output, since no release carries this behavior yet.