From: David Miller <davem@davemloft.net>
To: rmk@arm.linux.org.uk
Cc: ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org,
bhutchings@solarflare.com
Subject: Re: 2.6.27.8 (+the idr fix) TCP Ack issue
Date: Fri, 02 Jan 2009 13:34:35 -0800 (PST) [thread overview]
Message-ID: <20090102.133435.105577950.davem@davemloft.net> (raw)
In-Reply-To: <20090102142608.GC26093@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Fri, 2 Jan 2009 14:26:09 +0000
> Remote end sequence number is still at 1190.
>
> 19:47:32.285397 IP (tos 0x0, ttl 64, id 30055, offset 0, flags [DF], proto: TCP (6), length: 40) dyn-67.arm.linux.org.uk.38803 > 193.108.74.209.http: ., cksum 0x41e5 (correct), 3216:3216(0) ack 2215 win 10701
> 19:47:32.320287 IP (tos 0x0, ttl 238, id 10, offset 0, flags [none], proto: TCP (6), length: 40) 193.108.74.209.http > dyn-67.arm.linux.org.uk.38803: ., cksum 0x45e6 (correct), 1190:1190(0) ack 3216 win 10701
> 19:47:32.320300 IP (tos 0x0, ttl 64, id 30056, offset 0, flags [DF], proto: TCP (6), length: 40) dyn-67.arm.linux.org.uk.38803 > 193.108.74.209.http: ., cksum 0x41e5 (correct), 3216:3216(0) ack 2215 win 10701
> 19:47:32.353016 IP (tos 0x0, ttl 238, id 12, offset 0, flags [none], proto: TCP (6), length: 40) 193.108.74.209.http > dyn-67.arm.linux.org.uk.38803: ., cksum 0x45e6 (correct), 1190:1190(0) ack 3216 win 10701
> ...
>
> So it looks to me like the remote end doesn't like our ack of 2215 for
> some reason.
Let's make sure the checksum is OK. That's a reason the ACK might
get dropped at the remote end.
next prev parent reply other threads:[~2009-01-02 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 19:58 2.6.27.8 (+the idr fix) TCP Ack issue Russell King
2008-12-31 10:38 ` Ilpo Järvinen
2008-12-31 17:10 ` Russell King
2008-12-31 20:20 ` Ilpo Järvinen
2009-01-02 14:26 ` Russell King
2009-01-02 21:34 ` David Miller [this message]
2009-01-02 22:02 ` Russell King
2009-01-02 8:43 ` Herbert Xu
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=20090102.133435.105577950.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).