From: "Zack Weinberg" <zackw@stanford.edu>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@redhat.com>
Subject: 2.2.19 pre13 doesn't like retransmitted SYN ACK packets
Date: Thu, 15 Mar 2001 09:31:16 -0800 [thread overview]
Message-ID: <20010315093116.B2523@stanford.edu> (raw)
2.2.19 pre13 sends an RST in response to a retransmitted SYN ACK which
arrives after we've sent out the final ACK of the handshake. For
example:
tcpdump: listening on eth0
15:15:15.075670 wolery.Stanford.EDU.1341 > plan9.bell-labs.com.www:
S 1057306555:1057306555(0) win 32120
<mss 1460,sackOK,timestamp 49252305 0,nop,wscale 0> (DF) [tos 0x10]
15:15:15.156320 plan9.bell-labs.com.www > wolery.Stanford.EDU.1341:
S 1042976132:1042976132(0) ack 1057306556 win 1460 <mss 1460>
15:15:15.156364 wolery.Stanford.EDU.1341 > plan9.bell-labs.com.www:
. ack 1 win 32120 (DF) [tos 0x10]
15:15:15.204186 plan9.bell-labs.com.www > wolery.Stanford.EDU.1341:
S 1042976132:1042976132(0) ack 1057306556 win 1460 <mss 1460>
15:15:15.204232 wolery.Stanford.EDU.1341 > plan9.bell-labs.com.www:
R 1057306556:1057306556(0) win 0
I do not know if this behavior is correct or not from the TCP spec.
It seems unlikely to me, given that duplicate packets are expected
and ignored just about everywhere else. As a practical matter, this
behavior makes it close to impossible to communicate with a host that
commonly sends duplicate SYN ACKs. plan9.bell-labs.com is just such;
I estimate I get past the initial handshake one connection in twenty.
This kernel does not have SYN cookies compiled in. rp_filter is 1,
all other TCP and IP tunables are at their defaults.
zw
next reply other threads:[~2001-03-15 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 17:31 Zack Weinberg [this message]
2001-03-15 20:09 ` 2.2.19 pre13 doesn't like retransmitted SYN ACK packets Henrique de Moraes Holschuh
2001-03-15 23:41 ` Zack Weinberg
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=20010315093116.B2523@stanford.edu \
--to=zackw@stanford.edu \
--cc=alan@redhat.com \
--cc=linux-kernel@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