From: Stephen Hemminger <shemminger@osdl.org>
To: Noritoshi Demizu <demizu@dd.iij4u.or.jp>
Cc: Ion Badulescu <lists@limebrokerage.com>,
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: Thu, 1 Sep 2005 22:20:32 -0700 [thread overview]
Message-ID: <20050901222032.5cc649c0@localhost.localdomain> (raw)
In-Reply-To: <20050902.135138.38716488.Noritoshi@Demizu.ORG>
On Fri, 02 Sep 2005 13:51:38 +0900 (JST)
Noritoshi Demizu <demizu@dd.iij4u.or.jp> wrote:
> Below may not be directly related to the cause of the problem.
> But I think some window sizes in your mail need to be re-evaluated.
>
> > 11:29:54.961998 10.2.20.246.33060 > 10.2.224.182.8700: S 1972343059:1972343059(0) win 5840 <mss 1460,sackOK,timestamp 225781001 0,nop,wscale 2> (DF)
> > 11:29:54.983334 10.2.224.182.8700 > 10.2.20.246.33060: S 2770690746:2770690746(0) ack 1972343060 win 33304 <nop,nop,timestamp 99687881 225781001,mss 1460,nop,wscale 1,nop,nop,sackOK> (DF)
>
> Since the TCP Window Scale options are exchanged,
> the window size field contains shifted value except SYNs.
Be careful, tcpdump may be tracking the window scale and reporting
scaled values. Seems unlikely since with a window scale of 2, and odd
window size would be impossible. Also, is there by any chance a busted
firewall in the way (like OpenBSD) that corrupts window scaling.
next prev parent reply other threads:[~2005-09-02 5:19 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 [this message]
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=20050901222032.5cc649c0@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=demizu@dd.iij4u.or.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=lists@limebrokerage.com \
/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