Observed arrival · 2026-10-28
Netdryrun puts routing changes through a lab before CI says yes
Netdryrun runs network changes in a containerlab topology, checks routing behavior, and can fail a CI job when an expected condition is violated.
○Open
⊠Login
$Paid
†Ads
✦Pretty
●Pro
◎Niche
◉Human
⚑Risk
ƒJS
- For
- Network engineers testing routing changes in CI
- Worth noticing
- Its bundled three-node FRR example catches an unselected leaked default route even though BGP and ping checks pass.
Field notes
The bundled FRR scenario reports five passing checks and one failure: r1 receives a default route via BGP, but does not select it. That distinction matters because the example's ping and session checks still pass. The documented workflow keeps topology and changed configs in Git, describes expectations in netdryrun.yml, and produces a JSON evidence file with commands and raw output. The page also links to examples for FRR and SONiC changes.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
○OpenPublic substance visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use
One card from the complete issue