Had network, don't anymore

**timmyson** · 12-13-2004

I'm running Debian Woody, 2.4.18. I recently tried to set up a new machine, there were various problems that I was later told should never ever happen, and that I should just reinstall. With this old install, I had partial network connectivity. Since I reinstalled, I've been through every tutorial and howto I can find, and I can't get the network up at all. The fact that the network has been up seems to indicate that it's not a hardware glitch.

Here's everything I've done:
The driver is loaded from modules.conf:

Code:

...
sk98lin ConType 100FD	#the driver for the onboard nic, this argument ought to automatically make if full duplex 100Mbit
&#91;eof&#93;

The interface gets brought up by interfaces

Code:

# /etc/network/interfaces -- configuration file for ifup&#40;8&#41;, ifdown&#40;8&#41;

# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian installation
# &#40;network, broadcast and gateway are optional&#41;
auto eth0
iface eth0 inet static
	address 129.97.4.22
	netmask 255.255.255.0
	network 129.97.4.0
	broadcast 129.97.4.255
	gateway 129.97.4.1

Then I give it a check with ifconfig,

Code:

eth0      Link encap&#58;Ethernet  HWaddr 00&#58;11&#58;2F&#58;89&#58;55&#58;4F  
          inet addr&#58;129.97.4.22  Bcast&#58;129.97.4.255  Mask&#58;255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU&#58;1500  Metric&#58;1
          RX packets&#58;0 errors&#58;0 dropped&#58;0 overruns&#58;0 frame&#58;0
          TX packets&#58;0 errors&#58;0 dropped&#58;0 overruns&#58;0 carrier&#58;0
          collisions&#58;0 txqueuelen&#58;100 
          RX bytes&#58;0 &#40;0.0 b&#41;  TX bytes&#58;0 &#40;0.0 b&#41;
          Interrupt&#58;22 Memory&#58;feafc000-0 

lo        Link encap&#58;Local Loopback  
          inet addr&#58;127.0.0.1  Mask&#58;255.0.0.0
          UP LOOPBACK RUNNING  MTU&#58;16436  Metric&#58;1
          RX packets&#58;164 errors&#58;0 dropped&#58;0 overruns&#58;0 frame&#58;0
          TX packets&#58;164 errors&#58;0 dropped&#58;0 overruns&#58;0 carrier&#58;0
          collisions&#58;0 txqueuelen&#58;0 
          RX bytes&#58;10846 &#40;10.5 KiB&#41;  TX bytes&#58;10846 &#40;10.5 KiB&#41;

resolv.conf has all the right stuff

Code:

domain uwaterloo.ca
nameserver 129.97.128.100
nameserver 129.97.128.10

When I try to run mii-tool, I get

Code:

SIOCGMIIPHY on 'eth0' failed&#58; Bad address
no MII interfaces found

And when I try to ping, it just hangs

Code:

lt-vi&#58;~# ping 129.97.4.1
PING 129.97.4.1 &#40;129.97.4.1&#41;&#58; 56 data bytes
&#91;CTRL-C&#93;
--- 129.97.4.1 ping statistics ---
16 packets transmitted, 0 packets received, 100% packet loss

Am I missing a step? Could it be another crappy install? I'm tempted to just give up and let Windows handle the problem. Seems to me like Windows would be able to sort it out, or at least do a better job of telling me what's wrong. The longer I spend on this, the more respect I have for Microsoft.

**lakerdonald** · 12-13-2004

is the machine you are trying to ping set up to accept ICMP echo requests or is there any firewall or something?
-lakerdonald

**timmyson** · 12-13-2004

It's a University network, I can ping any computer on campus, except this new one, from another machine.

**lakerdonald** · 12-13-2004

can you access the internet?

**timmyson** · 12-14-2004

Nope, no internet either, so I'm getting a lot of excercize going back and forth between it, and this computer, with internet.

Thread Tools

Display

Had network, don't anymore

Posting Permissions