← All packs

Routing Pack 2: Ten More OSPF and BGP Incidents to Diagnose

Ten more broken networks, labs 11 to 20, in the same shape as the first pack. Virtual links, authentication, filter lists, reference bandwidth and default origination on the OSPF side; aggregation, communities, conditional advertisement, AS path loop prevention and administrative distance on the BGP side.

Every lab deploys already broken. You diagnose it, fix it, and the verifier checks the behaviour on both the control plane and the data plane before the reveal explains the mechanism.

Vendor-neutral Containerlab + FRR Runs locally No vendor images

What's in Routing Pack 2

Ten challenges, five OSPF and five BGP, numbered on from the first pack. Each one isolates a single behavior, and the difficulty decides how much the scenario tells you before you start.

OSPF
CHALLENGE 114 routers

Virtual Link Across the Transit Area

OSPFVirtual LinksAreasAdvanced30-45 min
INCIDENT

The remote site can still reach head office, but nothing at head office can reach the remote site.

CHALLENGE 123 routers

Authentication Half Applied

OSPFAuthenticationAdjacencyBeginner10-15 min
INCIDENT

One router dropped off the network after a security change, and its interface never went down.

CHALLENGE 133 routers

Filter List Pointing the Wrong Way

OSPFFilter ListsAreasIntermediate15-25 min
INCIDENT

A test subnet everyone thought was hidden is reachable from production, and the test rack has lost its route back.

CHALLENGE 143 routers

Two Links, One Cost

OSPFReference BandwidthCostIntermediate15-25 min
INCIDENT

Half the traffic to the data centre is slow, and it changes which half from one day to the next.

CHALLENGE 154 routers

The Default From the Dead Edge

OSPFDefault OriginationExternal LSAsAdvanced25-40 min
INCIDENT

Nothing at the site can reach the internet, and both internet routers say their configuration is unchanged.

BGP
CHALLENGE 163 routers

The Aggregate That Leaked

BGPRoute AggregationPrefix LimitsAdvanced25-40 min
INCIDENT

The provider session keeps dropping and coming back, and the site is unreachable from outside while it is down.

CHALLENGE 173 routers

The No-Export That Exported

BGPCommunitiesRoute MapsExpert35-55 min
INCIDENT

A partner says they can see a prefix of ours that is supposed to stop at our provider.

CHALLENGE 183 routers

The Backup That Never Stops Advertising

BGPConditional AdvertisementRoute MapsAdvanced25-40 min
INCIDENT

Traffic from outside is arriving over the backup circuit while the primary is up and healthy.

CHALLENGE 193 routers

Two Sites, One AS Number

BGPVPNAS-Path Loop PreventionAdvanced20-35 min
INCIDENT

Two sites of the same customer stopped being able to reach each other, and the provider says it is advertising both.

CHALLENGE 203 routers

The Two Tables Disagree

BGPAdministrative DistanceRIBIntermediate15-25 min
INCIDENT

A neighboring network became unreachable, and BGP says the route to it is fine.

Pricing

One price, everything included. No account, no subscription. The first pack is sold separately and neither needs the other.

$29 one-time

All ten labs, yours to keep.

  • 10 Containerlab scenario labs (5 OSPF, 5 BGP)
  • Topology files and broken starting configs for every router
  • Scenario docs that give away as much as the difficulty allows, and no more
  • A verifier that checks the routing tables and then sends traffic
  • Concept write-ups that explain the mechanism, not just the fix
  • Instant download after checkout
Get Routing Pack 2, $29
what you download
routing-pack-2/
├── README.md
├── LICENSE.txt
├── lab-11-virtual-link-through-stub/
│ ├── topology.yml
│ ├── topology.svg
│ ├── scenario.md
│ ├── reveal.md
│ ├── lab.html
│ ├── labctl
│ ├── configs/
│ └── faults/
├── lab-12-auth-half-applied/
│ └── ...
├── ...
└── lab-20-rib-failure-static-wins/
└── ...

New here

How a lab works, what a scenario looks like from the inside, and the setup, are all on the main page and in the guide. Lab 01 is free, and it is the fastest way to see whether this suits you.

Built by a network engineer, for network engineers.

Adjacency Labs grew out of the way real network problems are solved: start with the symptom, inspect the state, form a theory, make a change, and verify the result. The goal is to build troubleshooting judgment, not teach another sequence of commands.