From 2d12e7cbf9ff7d1e80fa88801e9fb9db844356eb Mon Sep 17 00:00:00 2001 From: Hans van Kranenburg Date: Sat, 20 Jun 2015 18:56:26 +0200 Subject: [PATCH] BGP Intro: remove cruft No idea what I was going to type there. --- bgp-intro/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bgp-intro/README.md b/bgp-intro/README.md index 43250ff..8d8cb84 100644 --- a/bgp-intro/README.md +++ b/bgp-intro/README.md @@ -298,7 +298,7 @@ Table `t_r3` now also contains the routes that are learned from `AS64080`: 10.40.32.0/19 blackhole [originate_to_r3 00:48:27] * (200) 10.40.0.0/22 via 10.40.217.17 on vlan217 [ebgp_r3 00:48:32] * (100) [AS64080i] -The above shows for example that prefix `10.40.216.0/21` was learned via the protocol `ebgp_r3`, 48 minutes ago, and that the range is originating from `AS64080`. The `via 10.40.217.17` is the BGP next-hop, which is the first router _outside_ our own network. On this router +The above shows for example that prefix `10.40.216.0/21` was learned via the protocol `ebgp_r3`, 48 minutes ago, and that the range is originating from `AS64080`. The `via 10.40.217.17` is the BGP next-hop, which is the first router _outside_ our own network. The BIRD master routing table also contains the routes learned over BGP, thanks to the `p_master_to_r3` protocol: