BGP peering and route advertisement labs
Practice BGP peering and route advertisement in simulated networks with editable router configurations.
Trace the prefix from its origin
Begin at the router that owns the service. Check the local route, the BGP origination configuration, and the prefixes learned by the next peer.
Compare reciprocal configuration
A peer relationship depends on both routers agreeing about the session. A single remote-AS typo can disconnect a service while the interface addresses remain reachable.
Apply and verify
Fix the peer or origination statement, then inspect the resulting BGP paths and verify the service. Network tests determine whether the repair works; the AI tutor cannot decide that a lab passes.
Protocol reference: BGP-4 protocol specification — RFC 4271.
A prefix without a voice
Miami edge. Parallel three-site metro paths have cross-links at each stage, between independent client and service handoffs. BGP carries the primary service prefix, but the connected secondary service subnet is absent from remote BGP tables. Investigate the two service networks from R1: 10.202.64.0/24 to 10.202.78.0/24 (TCP/443), and 10.202.65.0/24 to 10.202.79.0/24 (TCP/8443).
Link addressing (9)
- R1 R2
10.202.80.0/30 - R2 R3
10.202.81.0/30 - R3 R4
10.202.82.0/30 - R5 R6
10.202.83.0/30 - R6 R7
10.202.84.0/30 - R2 R5
10.202.85.0/30 - R3 R6
10.202.86.0/30 - R4 R7
10.202.87.0/30 - R7 R8
10.202.88.0/30
Free to practice. No account required.
Create an account to save your results and build your skill graph.