On Tue, May 15, 2007 at 07:27:26PM +0100, Karl E. Jorgensen wrote: > On Tue, May 15, 2007 at 10:22:50AM +0000, Tim Johnson wrote: > > On Tuesday 15 May 2007 17:33, Antti Talsta wrote: > > > On Tue, 15 May 2007, Tim Johnson wrote: > > > > eth0 Link encap:Ethernet HWaddr 00:80:AD:79:35:E1 > > > > inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 > > > > inet6 addr: fe80::280:adff:fe79:35e1/64 Scope:Link > > > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:28 errors:248 dropped:0 overruns:0 frame:0 > ---------- > > > > > > Hi Antti: > > 1)What do you see that is amiss? > > (I'm neither that hardware-savvy or system-savvy) > > Tim did underline the suspect area (just as I'm doing above)... > > This points towards link-level errors - things like the frame-level > checksum not matching etc. etc. which ... > > > > Faulty netcard or cable ? > > ... could easily be the result of a faulty (or insufficiently > shielded) cable... Or a faulty switch/hub. Or alternatively: a faulty > card (but then I'd only expect to see the error count increasing on > *one* side of the cable). > > > 2)If the card or cable was faulty, what would contribute > > to the behavior of having network connection right away > > after bootup and login, and then the connection is lost > > with minutes or *after* an initial connection? > > I see your logic, and I don't have a proper explanation... Perhaps the > underlying network code "gives up" once the error count reaches a > certain number? Or perhaps the two are getting further and further > "out-of-sync" where things eventually fail? Guesswork on my part... could it be a managed switch with some intrusion detection software that kills the port after x many errors / faults ? > > Hope this helps > -- > Karl E. Jorgensen > karl@jorgensen.org.uk http://www.jorgensen.org.uk/ > karl@jorgensen.com http://karl.jorgensen.com > ==== Today's fortune: > It's OKAY -- I'm an INTELLECTUAL, too.
Attachment:
signature.asc
Description: Digital signature