Comments on: Websites which can’t handle TCP window scaling http://www.sebruiz.net/255 Sun, 14 Mar 2010 23:15:18 +0000 hourly 1 By: Seb http://www.sebruiz.net/255/comment-page-1#comment-6369 Seb Wed, 27 Jun 2007 12:18:33 +0000 http://www.sebruiz.net/255#comment-6369 Thanks you all so much, you have solved my seemingly unfixable problem. Thanks you all so much, you have solved my seemingly unfixable problem.

]]> By: LukyLuke http://www.sebruiz.net/255/comment-page-1#comment-6368 LukyLuke Wed, 27 Jun 2007 12:08:48 +0000 http://www.sebruiz.net/255#comment-6368 Based on the information/solution from Jonathan I found an other, in my point of view a much better, solution. Instead to scale down the whole net to a 64 KByte buffer for sending and receiving, you can add custom routes for hosts/nets where this occurres: ip route add IP.ADD.RE.SS/32 via YourDefaultGateway window 65535 For your given site for example something like this: ip route add 149.171.95.20 via YourDefaultGateway window 65535 (Just replace "YourDefaultGateway" with it) NB: I found this solution (in german) on http://de.opensuse.org/SDB:Problem_mit_der_Herstellung_einer_TCP/IP_Verbindung_in_openSUSE_10.2 Based on the information/solution from Jonathan I found an other, in my point of view a much better, solution.
Instead to scale down the whole net to a 64 KByte buffer for sending and receiving, you can add custom routes for hosts/nets where this occurres:
ip route add IP.ADD.RE.SS/32 via YourDefaultGateway window 65535

For your given site for example something like this:
ip route add 149.171.95.20 via YourDefaultGateway window 65535
(Just replace “YourDefaultGateway” with it)

NB: I found this solution (in german) on http://de.opensuse.org/SDB:Problem_mit_der_Herstellung_einer_TCP/IP_Verbindung_in_openSUSE_10.2

]]> By: Chris http://www.sebruiz.net/255/comment-page-1#comment-6367 Chris Wed, 27 Jun 2007 11:41:56 +0000 http://www.sebruiz.net/255#comment-6367 Hi. That website wouldn't load here either. Wireshark showed that I could connect and send the http request alright, but the server didn't respond to that. Jonathan's solution made it work for me. Weird kind of problem... Hi. That website wouldn’t load here either. Wireshark showed that I could connect and send the http request alright, but the server didn’t respond to that.

Jonathan’s solution made it work for me. Weird kind of problem…

]]> By: Paul Eggleton http://www.sebruiz.net/255/comment-page-1#comment-6366 Paul Eggleton Wed, 27 Jun 2007 11:37:16 +0000 http://www.sebruiz.net/255#comment-6366 FWIW, I get the same issue here with Konq 3.5.7 on Gentoo here in NZ. Jonothan Brugge's remedy above seems to fix it though, so hopefully it will for you as well :) FWIW, I get the same issue here with Konq 3.5.7 on Gentoo here in NZ. Jonothan Brugge’s remedy above seems to fix it though, so hopefully it will for you as well :)

]]> By: Darkstar http://www.sebruiz.net/255/comment-page-1#comment-6365 Darkstar Wed, 27 Jun 2007 11:34:53 +0000 http://www.sebruiz.net/255#comment-6365 Check the MTU of your network card(s). I had similar problems with PCs behind a router. Try setting the MTU down to 1450 for example. Check the MTU of your network card(s). I had similar problems with PCs behind a router. Try setting the MTU down to 1450 for example.

]]> By: Jonathan Brugge http://www.sebruiz.net/255/comment-page-1#comment-6360 Jonathan Brugge Wed, 27 Jun 2007 11:11:08 +0000 http://www.sebruiz.net/255#comment-6360 I've seen a similar problem which took me quite some time to solve. In that case, there was a faulty router somewhere between me and the website. It didn't work well with TCP scaling and combined with some specific kernel versions which made the situation worse, lead to the problem you describe. Does 'echo 0 > /proc/sys/net/ipv4/tcp_window_scaling' solve it? I’ve seen a similar problem which took me quite some time to solve. In that case, there was a faulty router somewhere between me and the website. It didn’t work well with TCP scaling and combined with some specific kernel versions which made the situation worse, lead to the problem you describe. Does ‘echo 0 > /proc/sys/net/ipv4/tcp_window_scaling’ solve it?

]]> By: Anon Ymous http://www.sebruiz.net/255/comment-page-1#comment-6359 Anon Ymous Wed, 27 Jun 2007 11:01:07 +0000 http://www.sebruiz.net/255#comment-6359 Maybe a bit obvious, but have you tried tcpdump? Maybe a bit obvious, but have you tried tcpdump?

]]> By: Random http://www.sebruiz.net/255/comment-page-1#comment-6357 Random Wed, 27 Jun 2007 10:47:39 +0000 http://www.sebruiz.net/255#comment-6357 Java -- check your java settings . Java — check your java settings .

]]>