netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristian Evensen <kristian.evensen@gmail.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Strange TCP behavior over HSDPA
Date: Tue, 29 Dec 2009 10:59:43 +0100	[thread overview]
Message-ID: <4B39D30F.8090006@gmail.com> (raw)
In-Reply-To: <20091229083050.GA7209@ff.dom.local>

Den 29.12.2009 09:30, skrev Jarek Poplawski:
> The most obvious difference seems to be the SACK option used in [2],
> so maybe something on the route breaks it (without tunnels).
>
> Jarek P.
>    
Thank you for your reply. I have tried disabling SACK and then the 
performance when packet loss occured got even worse, and the rest of the 
time it was pretty similar.

After finally getting hold of someone I know at my ISP, I was told that 
they use TCP accelerators in their mobile network. Also, when looking at 
the packet captures from the server side I see that the sequene numbers 
are changed, so there is a machine doing something to the packets along 
the route. What I suspect is that this or these machines somehow breaks 
when a retransmission occurs. I am not quire sure what could cause it 
though, for example all dupAcks generated by the client are recieved by 
the server, but hopefully my ISP will be able to figure it out.

-Kristian

  reply	other threads:[~2009-12-29 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 12:56 Strange TCP behavior over HSDPA Kristian Evensen
2009-12-29  8:30 ` Jarek Poplawski
2009-12-29  9:59   ` Kristian Evensen [this message]
2009-12-29 10:57     ` Jarek Poplawski
2009-12-29 12:16       ` Jarek Poplawski
2009-12-29 13:36         ` Jarek Poplawski
2009-12-29 14:30           ` Kristian Evensen
2009-12-29 18:31             ` Jarek Poplawski

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=4B39D30F.8090006@gmail.com \
    --to=kristian.evensen@gmail.com \
    --cc=jarkao2@gmail.com \
    --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).