Lab R5: BGP peering

Most BGP trouble is not about paths. It is a session that will not come up, or one that is up and carries routes nobody can use. The reasons are few and each has a cure with a name: the two ends aim at addresses the other does not send from, a password is missing, the neighbor is more than one hop away, the next hop of a route is an address the inside of your network has never heard of, a private number shows in a path sent to the world. Here your company is a small provider. Build each session, meet each of those once, and fix it.

In Daveth Pro (Network)Build it from the brief · Five routers · 7 tasks

What you will do

  1. Inside: every router to every other
  2. Above: a session with a password
  3. Below: a neighbor two hops away
  4. A route with nowhere to send it
  5. A number that is not for the world
  6. A second family, a session of its own
  7. Keep it

New in this lab: iBGP, eBGP, multihop, next-hop, peer group, 4-byte AS, private AS, authentication, IPv6.

How it is checked

Each of the 7 tasks is checked on the devices themselves as you finish it: the bench reads how the network is configured and what it does, not what you typed. The lab is done when all 7 pass.

The lessons it follows

It opens after these, and uses what they teach:

Open the lab benchIt needs a computer: phones and tablets are not supported.