From: ROUTE 66 - Catalin BOIE <cboie@route66.ro>
To: � <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Strange TCP dump between a Linux and a Samsung phone
Date: Wed, 12 Nov 2008 09:15:13 +0200 [thread overview]
Message-ID: <491A8281.6040804@route66.ro> (raw)
In-Reply-To: <Pine.LNX.4.64.0811111701260.3930@wrl-59.cs.helsinki.fi>
� wrote:
> On Tue, 11 Nov 2008, ROUTE 66 - Catalin BOIE wrote:
Hello!
After upgrading to 2.6.26.?, the problem was fixed!
Thank you very much for your super quick answer!
>> I have captured a strange dump between a Linux kernel
>> 2.6.25.6-55.fc9.x86_64 and a Samsung device.
>
> Please upgrade or prove that the tcp fixes that were in the later kernel
> (.7 iirc or 2.6.26) got applied into that -55 part.
>> I looked at it and it seems that the Linux stack does not send any
>> retransmissions to Samsung device.
>> But, I want a competent look from you.
>>
>> The connection is done over a 3G connection.
>> The capture was done on a router between the two endpoints.
>> c.66.com is the Linux machine, the other IP is the Samsung device.
>
> ...snip...
>
>> As you may see, the Samsung device keeps sending an ACK for 1261841 and
>> after some time closes the connection.
>> Why the Linux stack does no retransmissions?
>
> Looks like a know bug in frto which got fixed.
>
> If upgrade is not an option, you can experiment by playing with tcp_frto
> sysctl (with 0 you should not encounter that bug).
Thanks!
--
Catalin BOIE
ROUTE 66
prev parent reply other threads:[~2008-11-12 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 14:05 Strange TCP dump between a Linux and a Samsung phone ROUTE 66 - Catalin BOIE
2008-11-11 15:05 ` Ilpo Järvinen
2008-11-12 7:15 ` ROUTE 66 - Catalin BOIE [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491A8281.6040804@route66.ro \
--to=cboie@route66.ro \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).