Figured I would pass this along... this going back a few months from the dates. Basic story was - have dual boot Debian/XP, suddenly when the Debian side is up ethernet is dead. Realtek RTL8139/810x by the way... At the time what I ended up with was a static address on the Debian side. That made the problem go away and like most times where I think, "when I get the time I'll have to figure out what the problem is..." I never did. Couple days ago problem returned (even with the static IP). The additional symptom this time was a "NETDEV WATCHDOG: eth0: transmit timed out." Google turned up a truck load of hits including http://bozziesfw.wordpress.com/2007/08/14/netdev-watchdog-timed-out-realtek-8139/ The only variation in my case was Windows restore didn't want to restore which made things a tad more complicated but once I had the driver rolled back (and Windows updates turned the h*ll off) - bingo... the Debian side works DHCP and all. ----- Original Message ----- From: "Joseph Huber" To: "Main PLUG discussion list" Sent: Tuesday, June 05, 2007 7:10 PM Subject: Re: network unreachable > Thanks for all the replies (on list and off). > > It doesn't seem to be hardware (everything is okay if I boot it Windows). > It > shouldn't be upgrade related... I haven't run any updates for some time (I > don't think Debian will decide to update anything for me unless I tell it > to - unlike a certain other OS)... > > Can we focus on the "I'm guessing your DHCP server has crapped out" from > Jeremy Miller? I tried the "ifconfig eth0" and got a bunch of output but > the > BROADCAST MULTICAST line wasn't prefixed with "UP" and I didn't have an > "inet addr x.x.x.x" line. I tried > > iface eth0 inet static > address 192.168.2.51 > gateway 192.168.2.1 > netmask 255.255.255.0 > > in /etc/network/interfaces however - no joy following > > ifconfig eth0 down > ifconfig eth0 up > > I brought the box back up to see what "ifconfig -a" had to say and it > showed > a "UP" prefixing the BROADCAST line and showed gave the "inet addr" line > with the 192.168.2.51 address... > > What's going on and what exactly is involved in the DHCP server crapping > out > (and I guess needing at least a warm boot in order to get it to bring up > the > static IP address)???? > > Joe > > > ----- Original Message ----- > From: "Kenneth" > To: "Main PLUG discussion list" > Sent: Tuesday, June 05, 2007 5:33 PM > Subject: Re: network unreachable > > >> >>> ifconfig tells me the following (I don't have any way to get it off the >>> box >>> >>> so there may be some typos): >>> >>> lo Link encap : Local Loopback >>> inet addr: 127.0.0.1 mask:255.0.0.0 >>> inet6 addr: ::1/28 Scopt:Host >>> UP LOOKBACK RUNNING MTU:16438 Metric:1 >>> RX Packets:6130 errors:0 dropped:0 overruns:0 frame:0 >>> TX Packets:6130 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 carrier:0 >>> RX bytes:979892 (948.0 KiB) >>> TX bytes:970802 (948.0 KiB) >> >> Try ifconfig -a >> This should show interfaces that are down, as well as those that are up. >> "lo" is the loopback interface and has nothing to do with your NIC. >> >> Use lsmod to check to see if a module is loaded for your NIC also. >> >> You might also find and post the relevant section of the output lf lspci, >> especially if you don't know what your NIC is, or which module should be >> loaded. > > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change you mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss