LinuxQuestions.org - eth0 status idle

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - eth0 status idle - aMule to blame? (https://www.linuxquestions.org/questions/linux-networking-3/eth0-status-idle-amule-to-blame-298436/)

eth0 status idle - aMule to blame?

Hi,

I am running FC3 and recently aMule just died on me. One day I ran out of disk space while it was running and it crashed (as you would probably expect). After this the client would load up and then shut down almost instantly.

Around the same time my internet connection died. I am reluctant to say "At the same time my internet connection died" but I am pretty sure it died after the next reboot. It is a LAN/broadband connection and works fine on my win2k box. I have disabled DNS server on the router - both PCs have fixed IP.

The Network Properties tool shows both "eth0" and "lo" interfaces as idle with eth0 having sent and received no packets, lo having received and sent 4.7MB of packets (immediately after startup).

#rehat-config-network

does not list any devices to activate/deactivate.

#ifconfig

output looks normal except that for eth0 TX sent = 0 and RX sent = 0. Entry for lo has something like inet6address ::1/128 and RX/TX bytes 4.7MiB again.

#ping 192.168.1.1 (router)

output is "Destination Host Unreachable"

Can anybody help me with where I should look next to find the problem?

Thanks

I would start with your eth0 - does it actually have an IP?
Try setting it manually:
#ifconfig eth0 192.168.1.3 (or whatever IP you have)
Then check routing-table ('route' or 'netstat -r')
Post the output, as well as output of 'ifconfig'

Pingu,

Here is the output. Netstat takes quite a while to finish printing out. Fedora appears to recognise the device and offers configuration options today(?!), through redhat-config-network.

Code:

#ifconfig eth0 192.168.1.137

#netstat -r



Destination  Gateway      Genmask        Flags      Metric    Ref    Use  Iface

192.168.1.0      *        255.255.255.0      U          0      0      0  eth0

169.254.0.0      *        255.255.0.0        U          0      0      0  eth0

default      192.168.1.1    0.0.0.0            UG        0      0      0  eth0



#ifconfig



eth0

Link encap:Ethernet  HWaddress: 00:E0:4C:E7:98:6E

inet addr: 192.168.1.137 Bcast: 192.168.1.255 Mask: 255.255.255.0

inet6 addr: fe80:2e0:4eff:fee7:986e/64 Scope:Link

UP BROADCAST RUNNING MULITCAST MTU:1500 Metric:1

RX Packets:0 errors:0 dropped:0 overruns:0 frame:0

TX Packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000

RX bytes: 0 (0.0b) TX bytes: 0 (0.0b)

Interrupt:11 Base address:0xc000



lo

Link encap:Local Loopback inet addr:127.0.0.1 Mask: 255.255.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX Packets:4026 errors:0 dropped:0 overruns:0 frame:0

TX Packets:4026 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

RX bytes: 4981352 (4.7MiB) TX bytes: 4981352 (4.7MiB)

Immediately after reporting the output to this forum, I tried again:

Code:

#netstat -r



Destination  Gateway      Genmask      Flags  MSS  Window  irtt  Iface

192.168.1.0    *        255.255.255.0    U    0    0        0    eth0

Different table, less entries in it.

So for some reason the defaul gateway is lost in routing-table.
Without a defalt gateway you'll get nowhere outside internal network (192.168.1.0).
One solution might be to add default gateway with a script, but then there is a risk it just hides the real problem - there must be a reason for dropping default gateway?
My guess is: reinstall first aMule, if it doesn't help reinstall routed too. (I know reinstalling seldom is the very best solution, but I have no other ideas.)