[Xorp-users] iBGP routes not being used/forwarded
Russ Dill
russ.dill at gmail.com
Mon Nov 24 14:13:05 PST 2008
I'd like to use the BGP component of XORP to forward routes along with some
additional per route data across an existing network. The machine has a
wireless card that connects to a mesh network. The wireless card runs its
own layer 2 routing protocol internally. From the wireless card, I'm
collecting reachable hosts and forwarding them via BGP to the local XORP
daemon. I use BGP so that I can also forward additional required information
about the devices as BGP options to remote systems that are running the same
collect/forward daemon. The entire wireless network appears as a flat class
A network to devices on the network.
Ok, so each machine that connects to the wireless network and runs an XORP
daemon to bridge that network across a backhaul would have an XORP boot file
that looks like the following:
interfaces {
interface mea0 {
default-system-config
}
interface eth0 {
default-system-config
}
}
fea {
unicast-forwarding4 {
disable: false
}
}
protocols {
bgp {
bgp-id: 192.168.1.136 /* backhaul IP */
local-as: 65002 /* local AS */
peer 127.0.0.1 {
local-ip: 10.54.12.1 /* wireless IP */
as: 65002 /* local AS */
next-hop: 10.54.12.1 /* wireless IP */
holdtime: 0
}
peer 192.168.1.126 { /* backhaul router */
local-ip: 192.168.1.136 /* backhaul IP */
as: 65000 /* AS of backhaul network */
next-hop: 192.168.1.136 /* wireless IP */
}
}
}
So the XORP daemon comes up, and has the following connected routes:
root at russ-laptop> show route table ipv4 unicast connected
10.0.0.0/8 [connected(0)/0]
> via mea0/mea0
192.168.1.0/24 [connected(0)/0]
> via eth0/eth0
And connects with the following BGP peers:
root at russ-laptop> show bgp peers detail
Peer 1: local 10.0.0.1/179 remote 127.0.0.1/179
Peer ID: 10.0.0.1
Peer State: ESTABLISHED
Admin State: START
Negotiated BGP Version: 4
Peer AS Number: 65002
Updates Received: 1, Updates Sent: 0
Messages Received: 3, Messages Sent: 2
Time since last received update: 51 seconds
Number of transitions to ESTABLISHED: 1
Time since last entering ESTABLISHED state: 51 seconds
Retry Interval: 120 seconds
Hold Time: 0 seconds, Keep Alive Time: 0 seconds
Configured Hold Time: 0 seconds, Configured Keep Alive Time: 0 seconds
Minimum AS Origination Interval: 0 seconds
Minimum Route Advertisement Interval: 0 seconds
Peer 2: local 192.168.1.136/179 remote 192.168.1.126/179
Peer ID: 192.168.1.126
Peer State: ESTABLISHED
Admin State: START
Negotiated BGP Version: 4
Peer AS Number: 65000
Updates Received: 0, Updates Sent: 0
Messages Received: 3, Messages Sent: 3
Time since last received update: n/a
Number of transitions to ESTABLISHED: 1
Time since last entering ESTABLISHED state: 51 seconds
Retry Interval: 120 seconds
Hold Time: 90 seconds, Keep Alive Time: 30 seconds
Configured Hold Time: 90 seconds, Configured Keep Alive Time: 30 seconds
Minimum AS Origination Interval: 0 seconds
Minimum Route Advertisement Interval: 0 seconds
The local collect/forward daemon talks to XORP and the following shows up in
XORP:
root at russ-laptop> show bgp routes
Status Codes: * valid route, > best route
Origin Codes: i IGP, e EGP, ? incomplete
Prefix Nexthop Peer AS Path
------ ------- ---- -------
* 10.170.232.0/24 10.170.232.1 10.0.0.1 65002 i
* 10.172.51.0/24 10.172.51.1 10.0.0.1 65002 i
root at russ-laptop> show bgp routes detail
10.170.232.0/24
From peer: 10.0.0.1
Route: Not Used
Origin: IGP
AS Path: 65002
Nexthop: 10.170.232.1
10.172.51.0/24
From peer: 10.0.0.1
Route: Not Used
Origin: IGP
AS Path: 65002
Nexthop: 10.172.51.1
However, no local routes are added:
ip route
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.136 metric
2
169.254.0.0/16 dev eth0 scope link metric 1000
10.0.0.0/8 dev mea0 scope link
default via 192.168.1.1 dev eth0
And no updates are sent to the backhaul peer.
Both peers are running XORP 1.5-6 from debian.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081124/00310e24/attachment.html
More information about the Xorp-users
mailing list