Differences between version 14 and predecessor to the previous major change of MetaNetBGPNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 14 | Last edited on Friday, October 17, 2008 9:56:41 pm | by DanielLawson | Revert |
| Older page: | version 12 | Last edited on Saturday, June 12, 2004 11:09:39 am | by CraigBox | Revert |
@@ -23,8 +23,9 @@
Then we set up a bgp router process:
+<pre>
! the following sets up a bgp router process with the local AS of 64899
router bgp 64899
! this assigns the bgp router-id of 10.255.255.1 to this router
bgp router-id 10.255.255.1
@@ -41,17 +42,19 @@
! these prefix lists limit which ip ranges we will send out
ip prefix-list as-64899 seq 5 permit 10.255.255.0/24
! and allow in.
ip prefix-list as-64900 seq 5 permit 10.0.0.0/8 le 32
+</pre>
A word on prefix lists. The prefix-list for as-64899 will only permit
10.255.255.0/24 - it wont allow any other networks. If you had two networks
you wished to advertise, you could that with
+<pre>
ip prefix-list as-64899 seq 5 permit 10.255.255.0/24
ip prefix-list as-64899 seq 10 permit 10.255.1.0/24
-
+</pre>
Also, note that the prefix-list for as-64900 has 'le 32' at the end.
This allows a range of prefixes to match - it will match prefixes
from 10.0.0.0/8 down to /32. This effectively matches all metanet routes,
@@ -88,8 +91,9 @@
If you telnet to localhost port bgpd, and enter enable mode, you can inspect
some parts of the bgp router process
+<pre>
show ip bgp
BGP table version is 0, local router ID is 10.66.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
@@ -108,49 +112,55 @@
*> 10.144.3.0/24 192.168.144.3 0 64900 64907 i
*> 10.230.1.0/24 192.168.230.1 0 64900 64915 i
Total number of prefixes 12
+</pre>
+
So this shows all the routes I have received, the next hop ip (gateway ip),
any metrics that have been applied, weights, and the path - which shows which
AS I received the routes through.
Note that there is one entry which has a metric of 20. This is being received via OSPF, which sets the default metric to 20, by deuterium's OSPF
routing process, and is being redistributed via BGP to my node.
+<pre>
# show ip bgp 10.66.10.1
BGP routing table entry for 10.66.10.1/32
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
64900
192.168.66.10 from 192.168.66.10 (10.66.10.1)
Origin IGP, localpref 100, valid, external, best
Last update: Thu Mar 6 14:11:26 2003
+</pre>
This shows the bgp entry for the route to 10.66.10.1/32
It shows the remote AS, and the path it takes, as well as some information
about it
We have one metanet node that is connected via a tunnel to one of the other
nodes. It is participating the BGP peering, and you will receive routes to it.
+<pre>
# show ip bgp 10.25.16.0
BGP routing table entry for 10.25.16.0/24
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
64900 64911
192.168.66.10 from 192.168.66.10 (10.66.10.1)
Origin IGP, localpref 100, valid, external, best
Last update: Thu Mar 6 14:11:26 2003
+</pre>
As you can see, there are two AS's in the AS list. This is because all traffic
to 10.25.16.0 is routed via 192.168.66.10 (deuterium), as 10.25.16.0 connets
to the metanet via a tunnel to deuterium.
To check your route is being seen by other machines on the wand network you might
want to check http://www.feet.net.nz/route.php
-
sample config:
+<pre>
!
hostname bgpd
password metanet
enable password metanet
@@ -165,7 +175,7 @@
neighbor 192.168.66.10 prefix-list as-64900 in
!
ip prefix-list as-<YOUR AS> seq 5 permit <YOUR 10.* NETWORK>/24
ip prefix-list as-64900 seq 5 permit 10.0.0.0/8 le 32
-
+</pre>
See [BGPNotes] for other general notes
