From: Ion Badulescu <lists@limebrokerage.com>
To: Noritoshi Demizu <demizu@dd.iij4u.or.jp>
Cc: Stephen Hemminger <shemminger@osdl.org>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels
Date: Fri, 2 Sep 2005 08:11:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0509020801380.10545@moisil.badula.org> (raw)
In-Reply-To: <20050902.151132.15273184.Noritoshi@Demizu.ORG>
On Fri, 2 Sep 2005, Noritoshi Demizu wrote:
>> By the way, if tcpdump does not track the window scale option, the right
>> edge (ack + real win) does not change between the following two ACKs.
>>
>>> 11:34:54.337167 10.2.20.246.33060 > 10.2.224.182.8700: . ack 84402527 win 15340 <nop,nop,timestamp 226080473 99717814> (DF)
>> (259 ACKs are omitted here)
>>> 11:34:54.611769 10.2.20.246.33060 > 10.2.224.182.8700: . ack 84454467 win 2355 <nop,nop,timestamp 226080721 99717841> (DF)
>>
>> The first line is the 37th ACK and the second line is the 295th ACK.
>>
>> ACK#37: ack=84402527 win=15340 right_edge=84463887 (= ack + win * 4)
>> ACK#295: ack=84454467 win=2355 right_edge=84463887 (= ack + win * 4)
>>
>> And all ACKs later than ACK#295 has win=2355 (2355*4=9420).
>>
>> This may be a hint. But, sorry, I do not know the internal of Linux TCP.
Oh, it's absolutely possible (even likely) that the application was slow
between 11:34:54.337167 and 11:34:54.611769 and data kept accumulating in
the socket buffer. The real problem is not the shrinking of the window,
but the fact that it never increases back to normal once the socket buffer
is emptied.
> I think there is a possibility that some middle-box does something,
> for example, some middle-box between the two machines does kinda
> traffic-shaping by tweaking the TCP window size field.
Not really: the tcpdump is taken on the very box that generates the acks
with the shrinking window, so it can't possibly be affected by any shaper.
Unless the shaper is the Linux kernel itself...
-Ion
prev parent reply other threads:[~2005-09-02 12:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 22:30 Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels Ion Badulescu
2005-09-01 22:43 ` David S. Miller
2005-09-01 22:49 ` Jesper Juhl
2005-09-01 22:53 ` David S. Miller
2005-09-01 22:53 ` Ion Badulescu
2005-09-01 23:37 ` Jesper Juhl
2005-09-02 2:51 ` John Heffner
2005-09-02 6:28 ` David S. Miller
2005-09-02 14:05 ` lists
2005-09-02 14:10 ` John Heffner
2005-09-02 14:33 ` lists
2005-09-02 14:48 ` John Heffner
2005-09-02 15:43 ` Ion Badulescu
2005-09-02 13:02 ` Guillaume Autran
2005-09-02 13:48 ` Ion Badulescu
2005-09-02 13:52 ` Alexey Kuznetsov
2005-09-02 14:11 ` John Heffner
2005-09-02 13:48 ` Alexey Kuznetsov
2005-09-02 14:16 ` John Heffner
2005-09-02 15:11 ` Alexey Kuznetsov
2005-09-02 18:36 ` Alexey Kuznetsov
2005-09-02 20:57 ` Ion Badulescu
2005-09-02 21:18 ` Alexey Kuznetsov
2005-09-02 23:09 ` Ion Badulescu
2005-09-28 16:31 ` Ion Badulescu
2005-09-29 15:17 ` Alexey Kuznetsov
2005-09-29 15:34 ` Guillaume Autran
2005-09-29 16:04 ` John Heffner
2005-09-29 18:16 ` David S. Miller
2005-09-30 0:29 ` David S. Miller
2005-09-02 4:51 ` Noritoshi Demizu
2005-09-02 5:20 ` Stephen Hemminger
2005-09-02 5:45 ` Noritoshi Demizu
2005-09-02 6:11 ` Noritoshi Demizu
2005-09-02 12:11 ` Ion Badulescu [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=Pine.LNX.4.62.0509020801380.10545@moisil.badula.org \
--to=lists@limebrokerage.com \
--cc=demizu@dd.iij4u.or.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=shemminger@osdl.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).