On 6/17/07, James G. Sack (jim) <[EMAIL PROTECTED]> wrote:
Bob La Quey wrote:
> Earlier today I had a power outage on my network. Usually
> I can reboot everything and I am good to go. Today, however,
> one of the boxes will not reestablish connection. I am left
> suspecting a hardware failure.
>
> The main power lines are a good example of how _not_ to
> do things. Basically long runs of extension cords and power
> strips with no consideration for grounding or ground loops.
>
> My guess is that a voltage spike took out the network interface
> on this box. I have swapped the cable to the router and gone
> through several ifdown/ifup attempts to no avail.
>
> The network interface on the downed PC is one that is built into
> the MB.
>
> Before I get a NIC and install it does anyone know a good way
> to determine if indeed the network interface hardware is broken?
>
> The good news is my daughter and her boyfriend brought me
> a nice bottle of Merlot for Father's Day, so I can drink my
> troubles away :)
>
We're talking about an ethernet interface, right.
Things I can think of:
1. lspci | grep [Ee]thernet
2. dmesg | grep [Ee]th (then visual around found lines)
3. cat /proc/net/dev
4. is there a link light when connected to the switch
5. ethtool eth0
5a. ethtool -i eth0
6. ifconfig eth0 up (ifconfig eth0 .. any Tx/Tx counts?)
7. tcpdump -i eth0 (or wireshark) .. anything (ping from other term)
Hope that gives some ideas.
Regards,
..jim
Hmm ... none of that led me to anywhere. But then
I bumped into the main outlet where the extension
cords all start (I am cleaning my garage) and on reboot
everything came back. I guess it is some kind of sequence
thing. Boot of cable modem, router, PC, etc.
Oh well it works, though damned if I know why it quit
before.
BobLQ "some things remain a mystery"
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
