Hi,
I've set up a simple test multipath route out eth1 and eth2 which go to
the same switch. I'm pinging from the multipath box to another box
plugged in to the switch, and it seems to work nicely. However,
something seems a bit strange with the timeout when I unplug the link
that is currently being used -- the base_reachable_time and delay_time
works properly (watching "ip neigh"), but then the entry in the routing
table gets a negative timeout, like this:
192.168.253.1 from 192.168.253.254 dev eth2
cache expires -94sec mtu 1500 advmss 1460
I have to wait a while longer before this route expires from route cache
and it then uses the neighbor table again and finds the correct route.
Is this expected? If so, why is the timeout negative and decreasing?
(If I run "ip route flush cache" at this point, it immediately finds the
correct route.)
Thanks,
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
-
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/
This archive was generated by hypermail 2b29 : Tue Apr 30 2002 - 22:00:19 EST