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 just recently installed Centos 7 on my desktop with an Asrock z97 extreme4 motherboard. The LAN port is an Intel I218V. I am using intel's provided driver e1000e for device communication. The issue I am having is when I first start my network the speeds are perfect, but after a minute or two the speed reduces drastically and usually just stops. If I simply issue 'service network restart' then the network comes back up fast then goes back to a crawl. I've used nethogs and the speed gets down to 0.02kb/s or lower. I've tried different versions of the driver, I have set up a static ip and used google's dns and specified the gateway. I am not sure what else to try.
Did you ADD a driver or was it the one you got with the installation? Typically it will configure your network devices based on what it discovers during installation so adding a driver isn't necessary.
If you run 'ethtool <interface>' what does it show you? A lot of NICs default to "auto-negotiate" which could be an issue if the other side is negotiating down. You can actually hard set the speed and duplex with ethtool from command line (and make it do it persistently across reboots by adding settings to the ifcfg-<interface> file in /etc/sysconfig/network-scripts.
I have seen issues with interfaces negotiating down to something like 10MB/half duplex causing issues like the one you describe on servers when the cable between it and the switch was flaky. Usually replacing the cable solved the issue.
Last edited by MensaWater; 10-25-2016 at 09:53 AM.
At first it was using the packaged driver provided by Centos 7 but I added the same driver later on thinking maybe the package was corrupt. I've ran the ethtool -i command to verify the driver and the version but didn't realize I could set the negotiation using that command. I want to bet that is the issue as I am running a gigabyte connection on a max connection speed of 22 mb/s. I will let you know what the output is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.