Differences between version 10 and previous revision of MetaNetBGPNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 10 | Last edited on Wednesday, March 19, 2003 8:16:28 pm | by DanielLawson | Revert |
| Older page: | version 1 | Last edited on Friday, March 7, 2003 12:48:22 am | by DanielLawson | Revert |
@@ -11,12 +11,17 @@
Deuterium has the AS 64900. Its neighbor IP is 192.168.66.10
We'll setup a test network with the AS 64899. Its internal IP range is
10.255.255.0/24, and its routers IP address is 10.255.255.1
+__NOTE__ AS 64899 and the IP range 10.255.255.0/24 are EXAMPLEs only. DO NOT attempt to use these. Please get your own IP range and AS allocated.
Read the section later on the registry to see how to obtain your AS number
In our /etc/zebra/bgpd.conf we have the usual garbage at the top: hostname,
password, enable passwd etc.
+
+__NOTE__ Make sure you EDIT this bgp config before trying to run it. There is a cleaner formatted version at the bottom of
+this page. You *will* need to change your AS number (router bgp ...), your router-id, and the networks you wish to advertise - both in the network line, and in the prefix-list line.
+
Then we set up a bgp router process:
! the following sets up a bgp router process with the local AS of 64899
@@ -71,9 +76,9 @@
AS Allocations. This will automatically allocate you the next available AS.
Don't ask for a specific one - you wont get it. Make sure you add in the
MetaNET IP of your bgp speaker. This is your 192.168 address.
-AS Detail
. In here, you specify which netblocks you will be advertising. You
+IP to
AS Allocation
. In here, you specify which netblocks you will be advertising. You
should only be able to advertise netblocks which are under your control. This
step is important as it gives the route servers information about which routes
to accept from you.
@@ -96,9 +101,8 @@
*> 10.25.16.0/24 192.168.66.10 0 64900 64911 i
*> 10.50.1.0/24 192.168.50.1 0 64900 64905 i
*> 10.66.1.0/24 0.0.0.0 32768 i
*> 10.66.2.0/24 192.168.66.2 20 0 64900 ?
- y
*> 10.66.10.1/32 192.168.66.10 0 64900 i
*> 10.100.1.0/24 192.168.100.1 0 64900 64901 i
*> 10.144.1.0/24 192.168.144.1 0 64900 64906 i
*> 10.144.3.0/24 192.168.144.3 0 64900 64907 i
@@ -108,8 +112,10 @@
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.
# 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)
@@ -137,8 +143,11 @@
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:
!
@@ -146,14 +155,14 @@
password metanet
enable password metanet
log file /var/log/zebra/bgpd.log
!
- router bgp 64899
- bgp router-id 10.255.255.1
- network 10.255.255.
/24
+ router bgp <YOUR AS NUMBER>
+ bgp router-id <IP ADDRESS OF YOUR ROUTER>
+ network <YOUR
10.* NETWORK>
/24
neighbor 192.168.66.10 remote-as 64900
neighbor 192.168.66.10 ebgp-multihop
- neighbor 192.168.66.10 prefix-list as-64899
out
+ neighbor 192.168.66.10 prefix-list as-<YOUR AS>
out
neighbor 192.168.66.10 prefix-list as-64900 in
!
- ip prefix-list as-64899
seq 5 permit 10.255.255.
/24
+ 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
