Loose eth0 after 60 seconds

I've had to rebuild my Suse 10.1 system and I'm seeing the network connection dropout after about 60 seconds. Unplugging and replugging the eithernet cable will change the continuously running ping from "Destination Host Unreachable" to good values to "Destination Host Unreachable". I'm pinging the router. The nat is a Davicom 21x4x DEC-Tulip compatible 10/100 Ethernet.

I'm using the same hardware as before - when things worked. Other computers on the same router are fine. I'm using a static IP address for this Linux machine (auto address DHCP shows 'Network is unreachable' which is odd as I used this successfully before).

ifconfig:

ifconfig - network connection lost
eth0 Link encap:Ethernet HWaddr 00:80:AD:7B:43:06
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::280:adff:fe7b:4306/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
Rx packets:12346 errors:4148 dropped:0 overruns:0 frame:0
Tx packets:7767 errors:9 dropped:0 overruns:0 carrier:9
collisions:0 txqueuelen:1000
Rx byes:15513857 (14.7 Mb) Tx bytes:588924 (575.1 Kb)
Interrupt:169 Base address:0xe800

lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
...

netstat -rn:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

Messages: I left out date, device name,

ifstatus: eth0 is down [pings "unreachable"]
ifprobe: eth0 device: <device name> --> restart interface! [I plugged/replugged eth. cable]
ifup: eth0 device: <device name> [pings okay]
ifup: eth0 configuration: eth-id-00:80:ad:7b
kernel: ADDRCONF (NETDEV_UP): eth0: link is not ready [pings again "unreachable"]

Any suggestions?

Lawrence

There are a ton of errors showing up in the ifconfig output.

Rx packets:12346 errors:4148 dropped:0 overruns:0 frame:0 Tx packets:7767 errors:9 dropped:0 overruns:0 carrier:9

This is normally going to be a hardware issue. First I would check your duplex settings and make sure they are correct. Then try another ethernet cable. Plug into another switch port. If none of those fix I would try another ethernet card.

I've been thinking it might be hardware then I booted up the system in Windows XP and the card worked just fine - surprise. I finally brought up the wireless card in the machine but this limits the updates which I can do. I have to use ndiswrapper for the wireless card and if the kernel gets updated it's possible to have the wrong version of ndiswrapper and hence no connection. I found this out the hard way.

I'll look into the duplex setting within the Linux configuration file. That's a good suggestion, thanks.

Larry

Have YOU tried "Ethtool"? See "man ethtool", in a terminal. It is very customizable. YOU may also need to see, "lspci", "lsusb", "modprobe", "insmod", and "ifconfig -a" or "ifconfig". IMHO setting the Static IP has great benefits. However, DHCP does not use Static IP's for resolution, it uses the request/receive method for IP resolving. See here...www.wiki.com for "Static IP" and "DHCP". They are not the same thing. We do use them for the same networking sometimes. <Two Linux Boxes sharing a router...>. Good luck.