Currently yes. Thats tunable
> When the problem occurs we can no longer ping the address mapped to the
> ethernet alias. The route -n command shows all of the expected routes
> plus a new set of 90 routes all going to eth0:94
This sounds like another piece of your equipment advertised a set of routes
or redirects and you are running some kind of routing daemon or picking
them up via ICMP redirect
> Are the any routing related changes in 2.0.33 or pre 34 ?
Not really.
> I'd be keen to talk with anyone else who is running a lot of Apache
> virtual web servers on a linux box to see if this problem occurs
> for anyone else.
I've no other reports but thats never quite the same as saying "must be
you"...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu