Skip to content
sp home

The network is down.
Your shift starts now.

SadPackets drops you into a live outage on real routers — FRR, GoBGP and Linux — with a terminal in your browser. Find the fault, fix it, and the checks prove it.

Create accountSign in

Free plan: 600 Lab Credits a month (≈ 10 h on a standard lab), no card needed.

leaf-1 — eBGP session won't establish. Replay of a lab: the neighbor is stuck in Active because of a wrong remote AS; after correcting it the session establishes and every check passes.outage live
leaf-1# show bgp summaryNeighbor     V    AS   Up/Down  State/PfxRcd10.0.12.2    4 65003  never    Activeleaf-1# show running-config | include remote-as neighbor 10.0.12.2 remote-as 65003leaf-1# configure terminalleaf-1(config)# router bgp 65001leaf-1(config-router)# neighbor 10.0.12.2 remote-as 65002leaf-1(config-router)# endleaf-1# show bgp summary10.0.12.2    4 65002  00:00:07 3checks  bgp-up pass   routes pass   dataplane passresolved in 6:41    +100 points

How a lab goes

Every lab runs the same loop, from the first guided outage to multi-router BGP.

  1. Read the brief

    What users are reporting, what should work, and the topology you inherited.

  2. Investigate

    Click any node to open its terminal. vtysh, ip, ping, tcpdump — the real tools.

  3. Fix it live

    Change the configuration on the running network, exactly like on the job.

  4. Run the checks

    Every requirement shows what was observed and what was expected. Pass them all to score.

From first steps to BGP

Fundamentals
Where everyone starts: a typo'd address, a missing gateway, a wrong netmask, an interface left down, a route that never comes back.
BGP
Sessions that won't establish, MD5 mismatches, filters that drop the wrong prefix, next-hops, path selection, route servers.
OSPF
Adjacencies stuck on an MTU mismatch, summary routes that blackhole traffic.
Start with your first outageThe first lab is guided and takes about ten minutes.