Bug#478062: This has a work around
I received an email from Ilpo Järvinen asking me to set F-RTO to off in
sysctl. I could not get the syntax right in that file to boot with that
option off so I ran
echo 0 >/proc/sys/net/ipv4/tcp_frto and I then ran a test page through
the cups web front end. It printed.
I don't know who Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> is, but a
quick google shows he appears to be a kernel developer. Below is a copy
of his request to me:
Hi,
I've been trying to track reports about TCP problem that is possibly F-RTO
related (there aren't that many), which was enabled for 2.6.24. Noticed
that http://mwh.geek.nz/ links to your mail as similar problem (wasn't
working for me except from google archives), that problem was solved by
turning F-RTO off (tcp_frto) sysctl. Could you possible check if that
applies to your CUPS case as well, if so I'd be interested to see some
tcpdumps about the problem to see what's wrong with it.
Ilpo,
What exactly do you want me to do to assist you pinning this down? I know the words "tcpdump" but I never ran it, it looks like you want me to run
tcpdump -some switches. After perusing the man file, I thought it best to just ask you what options would be best to be run. Keep in mind I have one box on my net that is running a vpn to a business that I do NOT want sniffed, so I would think that host printerIP would be best?
--
Damon L. Chesser
damon@damtek.com
http://www.linkedin.com/in/dchesser
Reply to: