Re: [Hampshire] constantly flickering LEDs on router, second try.
Lisi wrote: > So - thank you all very much. And I am an idiot. In the literal sense, of > course - but also in the modern derived sense. :-( don't be hard on yourself. Often situations like this are an excellent opportunity for learning. You are only an idiot if you keep making the same mistakes :-) regds -- Jon Wilks PGP key 0xFA593C1A from hkp://wwwkeys.uk.pgp.net -- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --
Re: [Hampshire] constantly flickering LEDs on router, second try.
Thanks, Hugo - I have read marked learnt and filed this. And yes, I was heading off base very fast. On Sunday 17 May 2009 20:12:27 Hugo Mills wrote: > On Sun, May 17, 2009 at 07:59:23PM +0100, hants...@googlemail.com wrote: > > I have had this problem since yesterday evening. > >Why is it a problem? :) Good question. I won't embarrass myself further by answering it. I thought I sent an email to Paul thanking him and saying that I was an idiot - but it doesn't seem to have got through. So - thank you all very much. And I am an idiot. In the literal sense, of course - but also in the modern derived sense. :-( Lisi I have left your excellent advice at the bottom in case someone looking to trouble shoot a non-existent network problem somehow finds my reply, but for some reason not your email. [snip] >You're heading way off base very fast, here... > >The first thing to do is to find out whether there actually is any > network traffic going past. Then you need to find out whether it's > network traffic that you want to be going through. > >Simple first test: if you bring down the main network interface on > the machine, does the flickering stop? > > # ifdown eth0 > > (Use ifup eth0 to bring it back up) > >If so, then it's probably not a hardware fault, and something > really is sending network packets. Also try: > > # watch -n 1 ifconfig > > and watch the RX bytes and TX bytes counters. > >To investigate what might be doing this communication, netstat may > help: > > # netstat -ap --inet --inet6 > >Look at the tcp and tcp6 sockets that are "ESTABLISHED", and see > what connections you've got. The last column will give you the pid of > the process, in each case, which you can then look up in "ps axfww". > >If you still can't see what might be causing the communications > you're worried about, then we can get all medieval on it with tcpdump > and/or wireshark, but the above should be a good start. > >Hugo. -- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --
Re: [Hampshire] constantly flickering LEDs on router, second try.
On Sun, May 17, 2009 at 07:59:23PM +0100, hants...@googlemail.com wrote: > I have had this problem since yesterday evening. Why is it a problem? :) > When my main desktop is connected to the router the light on the > port to which it is connected flickers constantly. I have tried it > on 3 of the 4 ports. I do not have this problem with any of the > other computers that are attached. > > Simultaneously the Internet connected led flashes. Initially the > IDE HDD light flashed as well, but that appears to have stopped. > > I have tried: > Three of the ports on the router. > two different network cards (the computer has two) > run rkhunter > a live CD > As to the problem, other possible causes I found were PSU and RAM. I have a > PC/SPS Tester, but am a bit scared to use it after all the warnings on the > net! I shall probably run Memtest overnight. You're heading way off base very fast, here... The first thing to do is to find out whether there actually is any network traffic going past. Then you need to find out whether it's network traffic that you want to be going through. Simple first test: if you bring down the main network interface on the machine, does the flickering stop? # ifdown eth0 (Use ifup eth0 to bring it back up) If so, then it's probably not a hardware fault, and something really is sending network packets. Also try: # watch -n 1 ifconfig and watch the RX bytes and TX bytes counters. To investigate what might be doing this communication, netstat may help: # netstat -ap --inet --inet6 Look at the tcp and tcp6 sockets that are "ESTABLISHED", and see what connections you've got. The last column will give you the pid of the process, in each case, which you can then look up in "ps axfww". If you still can't see what might be causing the communications you're worried about, then we can get all medieval on it with tcpdump and/or wireshark, but the above should be a good start. Hugo. -- === Hugo Mills: h...@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- What do you give the man who has everything? -- Penicillin is --- a good start... signature.asc Description: Digital signature -- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --
[Hampshire] constantly flickering LEDs on router, second try.
Sorry, everybody. Shouldn't have explored while I had an email on the go. :-( I have had this problem since yesterday evening. When my main desktop is connected to the router the light on the port to which it is connected flickers constantly. I have tried it on 3 of the 4 ports. I do not have this problem with any of the other computers that are attached. Simultaneously the Internet connected led flashes. Initially the IDE HDD light flashed as well, but that appears to have stopped. I have tried: Three of the ports on the router. two different network cards (the computer has two) run rkhunter a live CD The first two of those made no difference. Rkhunter found, so it said, a Trojan in inetd. So far I have done nothing with that information other than worry. The last, when I finally found a live CD that was prepared to talk to my hardware (Puppy 4.1.2 - Knoppix 6 was sadly a no go :-( ) was rock solid. I tried to use it a fair bit, then just left it, and it stayed rock solid for about two hours. I have googled both about the problem and about the rkhunter result. I do not know how much credence I should give the result, and if Puppy has rkhunter in its toolkit I may run it on the system from there. As to the problem, other possible causes I found were PSU and RAM. I have a PC/SPS Tester, but am a bit scared to use it after all the warnings on the net! I shall probably run Memtest overnight. TIA Lisi -- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --
