Bug#407735: closed by maximilian attems <firstname.lastname@example.org> (Re: Bug#407735: 2.6.18-3-686 tcp_window_scaling serious problem)
Sorry, this is not acceptable. This is *not* a bug with "my"
infrastrucuture. It occurs regardless of what network I am on (and I
should know, I have a laptop). It is a bug with the kernel's handing of
tcp window scaling and it is a severe bug because at least 30 percent of
the sites around the world become inaccessible with it.
So wrote Debian Bug Tracking System on Sunday, 21 January 2007:
> Date: Sun, 21 Jan 2007 09:03:23 -0800
> From: Debian Bug Tracking System <email@example.com>
> To: firstname.lastname@example.org
> Subject: Bug#407735 closed by maximilian attems <email@example.com> (Re:
> Bug#407735: 2.6.18-3-686 tcp_window_scaling serious problem)
> X-Mailer: MIME-tools 5.417 (Entity 5.417)
> This is an automatic notification regarding your Bug report
> #407735: 2.6.18-3-686 tcp_window_scaling serious problem,
> which was filed against the linux-image-2.6-686 package.
> It has been closed by maximilian attems <firstname.lastname@example.org>.
> Their explanation is attached below. If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact maximilian attems <email@example.com> by replying
> to this email.
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
> Date: Sun, 21 Jan 2007 18:01:27 +0100
> From: maximilian attems <firstname.lastname@example.org>
> To: email@example.com
> Subject: Re: Bug#407735: 2.6.18-3-686 tcp_window_scaling serious problem
> User-Agent: Mutt/1.5.9i
> On Sun, Jan 21, 2007 at 03:55:40PM +0100, Bastian Blank wrote:
> > tags 407735 wontfix
> > severity 407735 minor
> > thanks
> > On Sat, Jan 20, 2007 at 01:13:43PM -0800, firstname.lastname@example.org wrote:
> > > /proc/sys/net/ipv4/tcp_window_scaling is set to "1" be default in this
> > > kernel. But there is a serious problem with this which causes severe
> > > connection problems for some connections. The user will experience this
> > > as sites that fail to load, or begin to load then abruptly stop and just
> > > hang while loading.
> > There is a broken router or packet filter between the two machines.
> > > I thought that this problem no longer existed as of 2.6.18 kernels, but
> > > I can confirm this is happening again with this fresh debian
> > > linux-image-2.6.18-3-686 kernel in unstable.
> > This is a bug in your infrastructure, not the linux kernel.
> > Bastian
> thus closing