I'm experiencing by far the strangest problem I've ever encountered in
Linux.. I'm kind of left with no where to turn for ideas on what might be
happening, I thought maybe there is a slight change it is an actual bug.
First, the system.. A single process PIII-450 (katmai).
Linux 2.2.19 i686
The machine has 4 Network interfaces. a Dual intel etherexpress pro.. an
onboard 3c905, and a pci netgear card. (all 10/100)
The onboard, and dual intel work fine.. using the correct
eth0: 3Com 3c905B Cyclone 100baseTx at 0xcc00
eth1: Intel PCI EtherExpress Pro100 82557
eth2: Intel PCI EtherExpress Pro100 82557
eth3: Lite-On 82c168 PNIC rev 32 at 0xc800,
The netgear is using the tulip driver.. (eth3)
Here is the strange part.. The machine has two default routes set..
0.0.0.0 184.108.40.206 0.0.0.0 UG 0 0 0 eth3
0.0.0.0 220.127.116.11 0.0.0.0 UG 0 0 0 eth1
This problem is random.. Usually every 30 minutes to 4 hours.. The route
on eth3 just stops working.. You can still ping 18.104.22.168.. but you can't
get to this machine via that interface, and it can't route through it.
if you issue a:
route delete default gw 22.214.171.124 ; route add default gw 126.96.36.199
It all of a sudden works again.. The route table is identical to how it
was prior. Arp tables are the same before and after.. No errors in any
logs, or on screen.. Just random.
I'm at a loss.. Any thoughts?
--- Erik Parker---
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/