Hello misc@,
I'd like to set up bgpd with multiple routing tables, a la vrf-lite
(ie without mpls and mp-bgp).
What works:
- peering within a rtable/rdomain
- receiving the routes
What doesn't work:
- nexthop is never "validated"
-> routes are never installed in fib
Configuration is pretty straitforward:
# cat bgpd.conf
AS 64751
router-id 172.22.151.130
listen on 172.22.151.130 # loopback
listen on 172.22.151.251 # interface towards peer
rtable 10
group "ibgp peering AS64751" {
remote-as 64751
neighbor 172.22.151.245 {
descr "beta"
announce self
}
}
bgpd is started as such:
route -n -T10 exec bgpd -d -v -f /etc/bgpd/bgpd.conf
Peering gets up, and routes received:
# bgpctl -n show sum
Neighbor AS MsgRcvd MsgSent OutQ Up/Down State/PrfRcvd
172.22.151.245 64751 10851 6373 0 2d05h05m 338
Routes are received in rtable 0:
# bgpctl show rib in | head
flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale
origin: i = IGP, e = EGP, ? = Incomplete
flags destination gateway lpref med aspath origin
I 10.0.0.0/16 172.22.151.245 100 0 64734.14918
64734.12596 65112 65530 i
I 10.1.0.0/16 172.22.151.245 100 0 64734.14918
64734.12596 65112 65530 i
I 10.8.0.0/16 172.22.151.245 100 0 64734.12699
1.10582 65053 i
I 10.11.0.0/18 172.22.151.245 100 0 64828 64609 i
I 10.11.64.0/18 172.22.151.245 100 0 64828 1.10567 1.10594 i
I 10.15.0.0/16 172.22.151.245 100 0 64828 1.10604 65079 i
And indeed, 172.22.151.245 is not reachable in rtable0.
If I use "rde rib foo no evaluate", routes are put in the 'foo' rib,
but still not installed.
If I use the "rde rib foo table 10", I get the following error:
'/etc/bgpd/bgpd.conf:20: rtable 10 does not belong to rdomain 0'
I tried to use 'rdomain 10' in the config file, but that looks very
mpls-oriented (mp-bgp peering in GRT, which works fine btw).
Have I missed something, or am I asking for something currently unsupported?
Thanks, and sorry for the long post,
--
petrus
