Bernhard Hahn wrote (2013/04/11 23:22):
Am 11.04.2013 12:05, schrieb Eiichiro Watanabe:
Hi Bernhard,
Which linux kernel version do you use?
it's a 2.6.32
If you use it with 64bit Archtecture and multiple core CPUs, I recommend you would upgrade it to the later one. I encountered similar situation with Debian/Linux(64bit/Squeeze/2.6.32) 2 years ago and upgraded to 2.6.39(Squeeze-backports) at that time, then the issue had been gone. Now I am using Squeeze-backports/3.2.0, it has been fine. The related information is as the following link. http://kerneltrap.org/mailarchive/linux-netdev/2010/5/4/6276345
I'm not sure but I think older linux kernel(<= 2.6.36, maybe) sometimes do that.
If you don't use newer one, please try to set "net.ipv4.tcp_sack = 0" with sysctl.
it's set to 1, so we should be ok, if I got you right?
No. I meant that you should try to set it to 0, if it is hard to upgrade your kernel soon. TCP option field is used not only TCP-MD5 but also TCP SACK. So it sometimes disturbs TCP-MD5 is working when TCP SACK is enabled. Thanks, Eiichiro
Regards Bernhard
-- ################################################### Eiichiro Watanabe Internet Multifeed Co.