Sinon, on peut désactiver le tcp_window_scaling globalement en mettant un
net.ipv4.tcp_window_scaling=0 dans votre sysctl.conf
et vérifier la valeur globale par un
cat /proc/sys/net/ipv4/tcp_window_scaling
Le patch est visible dans le changelog du 2.6.17.12 après je ne sais pas trop quand la modif de base est apparue.
Extrait Changelog 2.6.17.12:
commit 31e8b3a3708f75d9e012e2c2ed2b9d6d69ad0491
Author: Stephen Hemminger <shemminger@osdl.org>
Date: Tue Aug 22 00:10:07 2006 -0700
Allow per-route window scale limiting
There are black box devices out there, routers and firewalls and
whatnot, that simply cannot grok the TCP window scaling option
correctly.
People should and do bark at the site running the device causing
the problems, but in the mean time folks do want a way to deal
with the problem. We don't want them to turn off window scaling
completely as that hurts performance of connections that would run
just fine with window scaling enabled.
So give a way to do this on a per-route basis by limiting the
window scaling by the per-connection window clamp. Stephen's
changelog message explains how to do this using a route metric.
[TCP]: Limit window scaling if window is clamped.
This small change allows for easy per-route workarounds for broken hosts or
middleboxes that are not compliant with TCP standards for window scaling.
Rather than having to turn off window scaling globally. This patch allows
reducing or disabling window scaling if window clamp is present.
Example: Mark Lord reported a problem with 2.6.17 kernel being unable to
access http://www.everymac.com
# ip route add 216.145.246.23/32 via 10.8.0.1 window 65535
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
[^] # Re: Etrange
Posté par aboo . En réponse au message Résolution du problème lcl.fr et linux. Évalué à 4.
Pour voir si vous avez le problème il suffit de faire un simple wget
wget --no-check-certificate "https://e.secure.lcl.fr/v_1.0/css/styleAp.css"
Si ça passe c'est cool
Sinon, on peut désactiver le tcp_window_scaling globalement en mettant un
net.ipv4.tcp_window_scaling=0 dans votre sysctl.conf
et vérifier la valeur globale par un
cat /proc/sys/net/ipv4/tcp_window_scaling
Le patch est visible dans le changelog du 2.6.17.12 après je ne sais pas trop quand la modif de base est apparue.
Extrait Changelog 2.6.17.12:
commit 31e8b3a3708f75d9e012e2c2ed2b9d6d69ad0491
Author: Stephen Hemminger <shemminger@osdl.org>
Date: Tue Aug 22 00:10:07 2006 -0700
Allow per-route window scale limiting
There are black box devices out there, routers and firewalls and
whatnot, that simply cannot grok the TCP window scaling option
correctly.
People should and do bark at the site running the device causing
the problems, but in the mean time folks do want a way to deal
with the problem. We don't want them to turn off window scaling
completely as that hurts performance of connections that would run
just fine with window scaling enabled.
So give a way to do this on a per-route basis by limiting the
window scaling by the per-connection window clamp. Stephen's
changelog message explains how to do this using a route metric.
[TCP]: Limit window scaling if window is clamped.
This small change allows for easy per-route workarounds for broken hosts or
middleboxes that are not compliant with TCP standards for window scaling.
Rather than having to turn off window scaling globally. This patch allows
reducing or disabling window scaling if window clamp is present.
Example: Mark Lord reported a problem with 2.6.17 kernel being unable to
access http://www.everymac.com
# ip route add 216.145.246.23/32 via 10.8.0.1 window 65535
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>