From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: Ion Badulescu <ion.badulescu@limegroup.com>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Ion Badulescu <lists@limebrokerage.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels
Date: Sat, 3 Sep 2005 01:18:10 +0400 [thread overview]
Message-ID: <20050902211810.GB18605@yakov.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.61.0509021609430.6083@guppy.limebrokerage.com>
Hello!
> Well, take a look at the double acks for 84439343, 84440447 and 84441059,
> they seem pretty much identical to me.
It is just a little tcpdump glitch.
19:34:54.532271 < 10.2.20.246.33060 > 65.171.224.182.8700: . 44:44(0) ack 84439343 win 24544 <nop,nop,timestamp 226080638 99717832> (DF) (ttl 64, id 60946)
19:34:54.532432 < 10.2.20.246.33060 > 65.171.224.182.8700: . 44:44(0) ack 84439343 win 24544 <nop,nop,timestamp 226080638 99717832> (DF) (ttl 64, id 60946)
It is one ACK (look at IP ID), shown twice. This happens sometimes
with our packet socket.
> >I still do not know how the value of 184 is possible in your case,
> >I would expect 730 as an absolute possible minumum. I see 9420 (2355*4).
>
> The numbers I mentioned are straight from the tcpdump and are not scaled,
I understood. I expect when 184*4, when you said 184. But minimum is
still 730 (unscaled 1460*2). If you really saw values lower than 730
(unscaled 1460*2), there is another more severe problem and the suggested
patch will not solve it.
Alexey
next prev parent reply other threads:[~2005-09-02 21:18 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 [this message]
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
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=20050902211810.GB18605@yakov.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=davem@davemloft.net \
--cc=ion.badulescu@limegroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=lists@limebrokerage.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).