[quagga-users 13321] Re: Q: deleting routes from the zebra_rib

Christian Franke nobody at nowhere.ws
Wed Jul 10 14:39:09 BST 2013


On 07/10/2013 02:32 AM, Charlet, Ricky wrote:
> Then I add a new connected interface/route on rtr2
> rtr2: lo=42.0.0.2/24
> 
> I epxpect that the `show ip route` will reveal only the new connected route, but it still retains the RIP route also:
> helios-cave# show ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
>        I - ISIS, B - BGP, > - selected route, * - FIB route
> 
> K>* 0.0.0.0/0 via 15.255.120.1, eth0
> C>* 15.255.120.0/21 is directly connected, eth0
> C>* 42.0.0.0/24 is directly connected, lo
> R   42.0.0.0/24 [120/2] via 172.16.30.220, eth1, 00:00:23
> C>* 127.0.0.0/8 is directly connected, lo
> C>* 172.16.30.0/24 is directly connected, eth1
> 
> 
> Is that bad? It seems so to me.

I tried to reproduce that here but to me it seems to be working correctly.

If I have "network lo" in the RIP router configuration on rtr2, the RIP
process will withdraw the route for 42.0.0.0/24 via rtr1 from zebra as
soon as I add 42.0.0.2/24 on rtr2's lo device. This is because ripd sees
that it has a better local route for 42.0.0.0/24 now. In that case, no
RIP route shows up anymore in "show ip route".

If I don't have "network lo" in the rip router configuration on rtr2
when adding 42.0.0.2/24, the rip process won't consider 42.0.0.0/24
locally connected and will keep the route via rtr1. In that case the RIB
looks like the one you showed above. RIPD sends the route via rtr1 to
zebra, but zebra will not install it as connected routes have a lower
administrative distance.

-Christian



More information about the Quagga-users mailing list