I have a problem with my NIC losing 'connetivity' on my boxen.
The nic uses the 'tlan' module, and eth0 comes up fine at boot. After a period of time that I haven't been able to determine, the networks goes kaplop and I can't connect to or from this boxen anylonger. I tried taking eth0 down and then eth0 back up again, but that didn't help. So I take eth0 down, rmmod tlan, and then eth0 back up again and that would restore things... temporarily. It'd go kaplop again eventually. So I built tlan into my kernel. This seemed to work, but now after about a day it acts the same way again. I can boot my system and the network connection goes bellyup anywhere between 30 minutes to a few hours later. And it doesn't matter if there is network activity or not. This has happened at times of ftp and web access, and then everything just stops. It has happened when nothing is happening and the next connection times out. I get messages in /var/log and on the console about 'eth0: link forced'. It seems that as soon as one of these messages appears, my network goes bellyup. It still does this even though the module is compiled into the kernel, which I thought was odd. (!?) I asked this before but got no replies, anyone have any ideas? Anyone see anything like this happening? I just found an old 3com 3c59x card, I will try that I guess. I'm just sick and silly from trying to figure this out on the lack of any time I can spend doing it. _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
