On Wed, Jul 30, 2008 at 4:26 AM, Stephen Hemminger <shemminger@xxxxxxxxxx> wrote: > You may be suffering with a site that has a window scaling problem. > This is due to some firewall or other middlebox that can't keep track > of window scaling properly. More information is in: > http://lwn.net/Articles/92727/ Stephen, thanks for the pointer. On my current Lenny box, /proc/sys/net/ipv4/ does not contain a file called tcp_default_win_scale (which the original article refers to), but I found a web-page suggesting tcp_window_scaling instead, so after: # echo 0 > /proc/sys/net/ipv4/tcp_window_scaling (followed by a "cat /proc/sys/net/ipv4/tcp_window_scaling" to make sure that the change had stuck), I've tried again: $ wget http://ocp.com.com/ad.js --2008-07-30 11:00:08-- http://ocp.com.com/ad.js Resolving ocp.com.com... 216.239.122.193 Connecting to ocp.com.com|216.239.122.193|:80... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. --2008-07-30 11:15:10-- (try: 2) http://ocp.com.com/ad.js Connecting to ocp.com.com|216.239.122.193|:80... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. --2008-07-30 11:30:12-- (try: 3) http://ocp.com.com/ad.js Connecting to ocp.com.com|216.239.122.193|:80... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. ... ... etc... Does anyone know whether this means that "window-scaling" is _not_ related to my problem? I do have a list of the ip addresses / dns names for the routers between myself and the destination box (which I managed to find using lft - tracert returned too many asterisks). Is there anything I can run against each of the routers in turn to try to fathom out where the problem is? In the meantime, that article has given me plenty of possible avenues of research (such as ECN) to look at... Thanks again, Jaime -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
