Your message dated Mon, 6 Sep 2010 06:41:10 +0200 with message-id <20100906044110.GD10168@mykerinos.kheops.frmug.org> and subject line Re: Bug#401435: already added to the errata has caused the Debian Bug report #401435, regarding debian-installer: sometimes net install does not work because of networking change in Linux 2.6.17 or later to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 401435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401435 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: debian-installer: sometimes net install does not work because of networking change in Linux 2.6.17 or later
- From: Santiago Vila <sanvila@unex.es>
- Date: Sun, 3 Dec 2006 15:14:02 +0100 (CET)
- Message-id: <None.LNX.4.64.0612031447290.8795@cantor.unex.es>
Package: debian-installer Version: 20061102 Severity: important This is really a feature more than a bug, but the adverse effects are so devastating that it would be nice to have a workaround in debian-installer, or have it properly documented in the install manual. It seems there is a buggy router between me and the Internet. As a result, apt-get does not work at all (it hangs, waiting for who knows what). Needless to say, this is very bad if one wants to install Debian via the Internet. I found a thread in the linux kernel mailing list which explains *exactly* my problem: http://www.gatago.com/linux/kernel/9440712.html Short summary: A change introduced in Linux 2.6.17 makes the network not to work properly in some cases, due to buggy routers. There is a trivial workaround: echo 0 > /proc/sys/net/ipv4/tcp_window_scaling However, I had to spend several afternoons to *diagnose* this problem and realize what exactly the nature of the problem was. Considering that the number of systems potentially affected is very big, it would be nice if this were at least documented somewhere. Thanks.
--- End Message ---
--- Begin Message ---
- To: Miguel Figueiredo <elmig@debianpt.org>, 401435-done@bugs.debian.org
- Subject: Re: Bug#401435: already added to the errata
- From: Christian PERRIER <bubulle@debian.org>
- Date: Mon, 6 Sep 2010 06:41:10 +0200
- Message-id: <20100906044110.GD10168@mykerinos.kheops.frmug.org>
- In-reply-to: <[🔎] 4C840699.4010808@debianpt.org>
- References: <[🔎] 4C840699.4010808@debianpt.org>
Quoting Miguel Figueiredo (elmig@debianpt.org): > According message #25 in 2007 info was added to the errata with a fix to > improve behaviour with broken routers. > > Can this bug be closed? Just Do It, IMHO. I very much doubt anybody triple checks: you went on this bug, you analyzed it, you found it could be closed...then just close it..:-) And to show you that I have an entire confidence in your judgement, I close it now.Attachment: signature.asc
Description: Digital signature
--- End Message ---