[Xorp-users] XORP RIP enabled. Why are static routes required?

[Mark Handley]

One curiosity shows up.  On router 2:

>Xorp> show route table ipv4 unicast final
>Network 172.20.2.0/24
>    Nexthop := 172.20.2.2
>    Metric :=     0    Protocol := connected    Interface := eth1    Vif := 
>eth1
>Network 172.20.3.0/24
>    Nexthop := 172.20.3.1
>    Metric :=     0    Protocol := connected    Interface := eth2    Vif := 
>eth2

OK, so XORP knows nothing of a route to 172.20.1.0.
But the Linux kernel does:

>Kernel Routing Table
>--------------------
>[eessd@atherton bin]$ netstat -rn
>Kernel IP routing table
>Destination     Gateway         Genmask         Flags   MSS Window  irtt 
>Iface
>137.222.106.0   0.0.0.0         255.255.255.0   U         0 0          0 
>eth0
>172.20.3.0      0.0.0.0         255.255.255.0   U         0 0          0 
>eth2
>172.20.2.0      0.0.0.0         255.255.255.0   U         0 0          0 
>eth1
>172.20.1.0      172.20.2.2      255.255.255.0   UG        0 0          0 
>eth1
>172.20.0.0      0.0.0.0         255.255.255.0   U         0 0          0 
>eth1
>0.0.0.0         137.222.106.1   0.0.0.0         UG        0 0          0 
>eth0
>[eessd@atherton bin]$

So there's a route left behind from some other route configuration or
some other routing daemon.  And it looks to me like that route has the
wrong gateway - shouldn't it be 172.20.2.1?  

I doubt this is the cause of the problem, but XORP might not be really
happy that this route is present.  Probably best to delete it to be
sure this isn't causing a problem.

 - Mark