network unreachable

[Joseph Huber]

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" <madhse at yahoo.com>
To: "Main PLUG discussion list" <plug-discuss at lists.plug.phoenix.az.us>
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.