Linux - NetworkingThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have faced big trouble setting up my network card, but at least now I can bring up eth0. However, it seems I can't ping any computer on my LAN. I have looked at some similar posts, but I can't get their solutions really solve my problem..
The icmp 'Destination Host Unreachable' reply comes from your local interface, so the icmp echo request never enters your cable. Are you sure your cable is properly connected, and that you are using the right cable?
In plain English, means that your system found what it thinks is the right network but could not find the other system on that network.
-A subtle slip up could be that the computer you want to reach has a different netmask and/or broadcast address, although the ones you have set, from your ifconfig, are the defaults for that IP range so it's not likely.
-The most common problem here would be no connection between you and the other system, as qazzaq eluded to. Check to make sure all the cables are pluged in and the linklights on the ports are lit up. You could also see if there is a faulty cable by replacing one, sometimes a miswired or iffy cable will give you link lights but won't transmit data.
-It's also possible that a misconfiguration was made. If the other system has that IP address, make sure there is not a router between the two systems (plugging them both into ports on an Internet sharing router does not usually mean that the router is between them unless one is on the input, or "Internet" port)
-If there are other systems on your network, can you ping those? What is at the 192.168.0.1 address i.e. a router or another computer and if there are other systems on your network, can they ping that device?
-What type of network card are you using (if unsure then post the relevant output from, as root, lspci and lsmod)? It's rare, but it can happen that some network cards will load their drivers without obvious errors and still not reach other computers on the network.
-Usually, but not always, a firewall preventing pings will give you a different error such as, "Connection Refused By Host."
qazzaq:
I think you're absolutely right that the signal never enters the cable, the problem is why. It is connected correctly. The cable and the network card work perfectly under Windows, and previous versions of Linux. My latest working distribution was Fedora Core 1. In both FC2 and FC3, eth0 can not even be activated. Now, I use Mandrake 10.1, and there eth0 can be activated. But, now I have this problem.
Darin:
- The netmask and broadcast addresses are correct.
- Cables are plugged, as described above.
- I am trying to ping a router directly connected to my computer. The router is pingable when booted in Windows, and also from other computers.
- I can't ping anyone (but myself), nor can anyone ping me.
- Below is the listing of lspci and lsmod. Previous distributions have always autodetected the module "tulip", but Mandrake detects "de2104x". It doesn't matter, though. No matter the module the behaviour is the same.
luis_m_c:
- Those files do have the specified values.
- Adding that route does unfortunately not help.
Thank you for taking your time. I'm still quite confused. I'm getting to think there is a driver problem. Perhaps I should buy a new network card better supported by Linux (although it has been (still is?) quite well supported). It is quite old, but does work..
Look on the Mandrake site to be sure the ethernet card you are using is compatible.
If it is, try the wizard to setup your internet once again. The wizard should work great when you have a simple network configuration.
If it is still not working, try another card like a 3com / smc / etc. (anyways they are cheap).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.