Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have a board running redhat 9, kernel 2.4.20-(?). It has an intel pro1000 (82546eb) ethernet controller that has 2 copper gigabit ports. Both ports initialize fine, but e0 wont transmit at all. When I try to ping e0 from another computer on the network, it just sits...doesnt show the pings timing out. On e0, the Rx packet counter increases, but tx does not.
When I try to ping from e0 to somewhere on the network, a message comes up saying "connect: network is unreachable"
The cable and switch have both been tested and are good.
ethtool shows the port as connected at 1000/full
(ethtool wont let me force the port to anything. when i change any settings through ethtool, the port goes down, then comes back up with the same settings as before)
Whats wierd is how e1 works just fine. And I don't think its a hardware issue because I have an identical board that I have installed in the box that has the same problem.