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.
Last updated kernel to 3.2.0-4-686-pae on my Debian firewall via apt-get. Previous kernel package was linux-image-3.2.0-4-686-pae_3.2.57-3+deb7u2_i386 and the last is linux-image-3.2.0-4-686-pae_3.2.60-1+deb7u1_i386.
After that, most of the sites was opened after long delays or not open at all.
No errors on the console. I do not know where to look for the problem.
Put the old kernel back in and see if that corrects it. I rather doubt it can be the kernel but you will have to test something. Use other route tests also. May need to try wireshark even.
I noticed the same issues when I updated to the security fixed (ptrace issue) kernel 3.2.60-1+deb7u1 (I was using the amd64 one though), when I returned to the 3.2.57-3+deb7u2 kernel my networking went fine. While I have not posted the bug myself on debian, it looks like it has been posted Bug#754173 (bugs.debian.org). Not much action yet. The problem with a kernel bug is it requires a reboot, and a lot of people need to schedule those for their servers, so you may not see a lot of people reporting the issue yet.
I noticed the same issues when I updated to the security fixed (ptrace issue) kernel 3.2.60-1+deb7u1 (I was using the amd64 one though), when I returned to the 3.2.57-3+deb7u2 kernel my networking went fine. While I have not posted the bug myself on debian, it looks like it has been posted Bug#754173 (bugs.debian.org). Not much action yet. The problem with a kernel bug is it requires a reboot, and a lot of people need to schedule those for their servers, so you may not see a lot of people reporting the issue yet.
For those interested there is now some additional information under the debian bug report. It now links 2 bugs together. The current work around is to use ethtool to turn off the gro feature on your nic.
To make this survive booting, edit /etc/network/interfaces
Add a line:
pre-up /sbin/ethtool -K eth0 gro off
you will need 1 line per interface, and change eth0 to your correct nic.
It seems the bug is related to routing/nat.
I can confirm for my network configuration the work around seems to be working so far.
For those interested there is now some additional information under the debian bug report. It now links 2 bugs together. The current work around is to use ethtool to turn off the gro feature on your nic.
To make this survive booting, edit /etc/network/interfaces
Add a line:
pre-up /sbin/ethtool -K eth0 gro off
Thanks again. I already read about solution, upgrade the kernel and made changes in /etc/network/interfaces.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
