Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
03-06-2005, 03:59 PM
|
#1
|
|
Member
Registered: Jul 2004
Location: Glasgow, UK
Distribution: Ubuntu 6.10, FC5
Posts: 40
Rep:
|
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
|
|
|
|
03-07-2005, 03:10 AM
|
#2
|
|
Member
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 987
Rep:
|
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'
|
|
|
|
03-08-2005, 06:29 PM
|
#3
|
|
Member
Registered: Jul 2004
Location: Glasgow, UK
Distribution: Ubuntu 6.10, FC5
Posts: 40
Original Poster
Rep:
|
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)
|
|
|
|
03-08-2005, 07:04 PM
|
#4
|
|
Member
Registered: Jul 2004
Location: Glasgow, UK
Distribution: Ubuntu 6.10, FC5
Posts: 40
Original Poster
Rep:
|
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.
|
|
|
|
03-09-2005, 01:20 AM
|
#5
|
|
Member
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 987
Rep:
|
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.)
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:48 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|