Re: possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage)

2006-07-10 Thread CaT
On Wed, Jul 05, 2006 at 07:54:01AM -0400, linux-os (Dick Johnson) wrote: running since 8:42pm yesterday. It's 8:37am now. It hasn't progressed in any way. It hasn't quit. It hasn't timed out. It just sits there, hung. This leads me to consider the possibility of a DOS, either intentional

Re: possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage)

2006-07-05 Thread linux-os \(Dick Johnson\)
On Tue, 4 Jul 2006, CaT wrote: On Fri, Jun 30, 2006 at 08:50:39AM +1000, CaT wrote: Another datapoint to this is that I've had this my netcat web test running since 8:42pm yesterday. It's 8:37am now. It hasn't progressed in any way. It hasn't quit. It hasn't timed out. It just sits there,

possible dos / wsize affected frozen connection length (was: Re: 2.6.17.1: fails to fully get webpage)

2006-07-04 Thread CaT
On Fri, Jun 30, 2006 at 08:50:39AM +1000, CaT wrote: Another datapoint to this is that I've had this my netcat web test running since 8:42pm yesterday. It's 8:37am now. It hasn't progressed in any way. It hasn't quit. It hasn't timed out. It just sits there, hung. This leads me to consider the

Re: 2.6.17.1: fails to fully get webpage

2006-06-29 Thread Bill Davidsen
CaT wrote: On Wed, Jun 28, 2006 at 08:47:09PM -0700, David Miller wrote: You can save yourself that hassle by informing the site admin of the affected site that they have a firewall that misinterprets the RFC standard window scaling field of the TCP headers. These devices assume it is zero

Re: 2.6.17.1: fails to fully get webpage

2006-06-29 Thread CaT
On Thu, Jun 29, 2006 at 10:50:00AM -0400, Bill Davidsen wrote: Basically the mostlikely end-result is I don't know what there is a problem and my customer doesn't know that there is a problem but they're just not getting as many hits to their site that they otherwise would. Ofcourse, this

2.6.17.1: fails to fully get webpage

2006-06-28 Thread CaT
I had recently upgraded to 2.6.17.1 and tried to go to http://submit.spam.acma.gov.au/acma_submit.cgi?lang=EN to report an australian spammer. Unfortunately the loading of the webpage cuts out at 5472 bytes. I can repeat this each and every time under 2.6.17.1 with ( echo 'get

Re: 2.6.17.1: fails to fully get webpage

2006-06-28 Thread David Miller
From: CaT [EMAIL PROTECTED] Date: Thu, 29 Jun 2006 11:59:15 +1000 Now I found a thread about tcp window scaling affecting the loading of some sites but I fail to load the above site with /proc/sys/net/ipv4/tcp_adv_win_scale set to 6 and 2 under 2.6.17.1 whilst it works just fine with the

Re: 2.6.17.1: fails to fully get webpage

2006-06-28 Thread CaT
On Wed, Jun 28, 2006 at 07:46:27PM -0700, David Miller wrote: From: CaT [EMAIL PROTECTED] Date: Thu, 29 Jun 2006 11:59:15 +1000 Now I found a thread about tcp window scaling affecting the loading of some sites but I fail to load the above site with /proc/sys/net/ipv4/tcp_adv_win_scale

Re: 2.6.17.1: fails to fully get webpage

2006-06-28 Thread David Miller
From: CaT [EMAIL PROTECTED] Date: Thu, 29 Jun 2006 13:09:23 +1000 Yup. Must've. Just tried it now and setting tcp_window_scaling to 0 makes the site load. Sorry about that. Looks like I'll have to remember to make sure that gets set to zero on any servers I wind up having to upgrade to 2.6.17

Re: 2.6.17.1: fails to fully get webpage

2006-06-28 Thread CaT
On Wed, Jun 28, 2006 at 08:47:09PM -0700, David Miller wrote: You can save yourself that hassle by informing the site admin of the affected site that they have a firewall that misinterprets the RFC standard window scaling field of the TCP headers. These devices assume it is zero because they