> I've got a news server that has recently become multi-homed. until now it
> has behaved flawlessly for a few months, however now the interface that
> has the default route slows to a crawl after running for a few hours, the
> second interface is unaffected. no kernel messages accompany this behavior
> however downing the interface and bring it back up again fix the problem.
> generally it takes 8-11 hours for this issue to manifest itself.
>
> sample pinges through each interface follow:
I've also started to see this behavior. Internal (switched 100Bt)
interface (eth1) will return ~4/10 network packets with ping times
of 1000 - 2000ms while the other ~60% are 0.1 - 0.3ms. All ping
times on the external (eth0) interface appear normal (hooked to a
DSL bridge).
Noname P233
64MB
3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c905B Cyclone 100baseTx at 0x6200, 00:10:5a:98:8d:42, IRQ 10
tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov
eth1: Lite-On 82c168 PNIC rev 32 at 0x6100, 00:C0:F0:2E:01:13, IRQ 9.
2.2.10+2.2.11-pre2
ipchains
+--------------------------------------------------------------------------+
| Aaron T Porter | If you can't code it -- support it |
| atporter@primate.net | Help make Linux work for everyone |
| owner-linux-kernel@vger.rutgers.edu | Subscribe to linux-admin today. |
+--------------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/