Bug#478062: Fix FRTO+NewReno problem

2008-07-07 Thread Brian Burch
I reported a problem upgrading from ubuntu dapper to hardy where printing to an ethernet-connected HP Laserjet 2200 using a PrintSir using LPR/LPD protocol always fails. See https://bugs.launchpad.net/bugs/225603 I didn't get a response, so finally decided to run a sniffer trace when

Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around)

2008-05-12 Thread Ilpo Järvinen
On Thu, 8 May 2008, Ilpo Järvinen wrote: On Thu, 8 May 2008, Damon L. Chesser wrote: reran the print job with the correct kernel (for control reasons) and received the same results: tcp_frto=1 no print. tcp_frto=0 I can print. Attached is the output of tcpdump uname -r =

Bug#478062: Fix FRTO+NewReno problem

2008-05-08 Thread David Miller
From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Thu, 8 May 2008 01:26:59 +0300 (EEST) [PATCH] [TCP] FRTO: SACK variant is errorneously used with NewReno I applied this with a minor coding style fixup. From: Ilpo_Järvinen [EMAIL PROTECTED] Date: Thu, 8 May 2008 01:26:59 +0300 (EEST) +static int

Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around)

2008-05-08 Thread Damon L. Chesser
Ilpo Järvinen wrote: Snip Could you next try with tcp_frto set to 1, if my theory proves to be correct, it too should be enough to fix the problem (in this particular case). Of course you can verify the patch below too if you want to, the patch should allow cups-printer to work with

Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around)

2008-05-08 Thread Damon L. Chesser
Ilpo Järvinen wrote: Snip Could you next try with tcp_frto set to 1, if my theory proves to be correct, it too should be enough to fix the problem (in this particular case). Of course you can verify the patch below too if you want to, the patch should allow cups-printer to work with

Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around)

2008-05-08 Thread Damon L. Chesser
Ilpo Järvinen wrote: SNIP Could you next try with tcp_frto set to 1, if my theory proves to be correct, it too should be enough to fix the problem (in this particular case). Of course you can verify the patch below too if you want to, the patch should allow cups-printer to work with

Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around)

2008-05-08 Thread Ilpo Järvinen
On Thu, 8 May 2008, Damon L. Chesser wrote: Ilpo Järvinen wrote: SNIP Could you next try with tcp_frto set to 1, if my theory proves to be correct, it too should be enough to fix the problem (in this particular case). Of course you can verify the patch below too if you want to, the patch

Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around)

2008-05-07 Thread Ilpo Järvinen
Added Cc netdev (=linux network developers list). On Wed, 7 May 2008, Damon L. Chesser wrote: Ilpo Järvinen wrote: So the problem was 100% reproducable for you with FRTO (I'm still catching up the details here :-))? Yes, 100% reproducible if you turn FRTO = 2. Printing works as it is