10.0.0.1 however is far from dead, if we add yet another nexthop:
# ip ro add dev eth0 default nexthop via 10.10.10.10 dev eth0 nexthop via
10.0.0.1 dev eth0 nexthop via 10.0.0.202 dev eth0
# ip ro ls
10.0.0.0/8 dev eth0 proto kernel scope link src 10.0.0.11
default
nexthop via 10.10.10.10 dev eth0 weight 1 dead
nexthop via 10.0.0.1 dev eth0 weight 1
nexthop via 10.0.0.202 dev eth0 weight 1
This first nexthop is *always* declared dead. Linux 2.4.x, iproute 20010824.
If anybody can point me in the direction of this problem, it must be known
as it has been there for a *long* time, it would be appreciated. I'll try to
fix it.
Thanks!
Regards,
bert
-- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk Netherlabs BV / Rent-a-Nerd.nl - Nerd Available - Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/