[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131120122211.386c9680@nehalam.linuxnetplumber.net>
Date: Wed, 20 Nov 2013 12:22:11 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Fw: [Bug 65271] New: Acceptable RST packets (with seq number in
window) are ignored in LAST_ACK state (and previously sent data pending
acknowledgement)
Begin forwarded message:
Date: Wed, 20 Nov 2013 07:03:59 -0800
From: "bugzilla-daemon@...zilla.kernel.org" <bugzilla-daemon@...zilla.kernel.org>
To: "stephen@...workplumber.org" <stephen@...workplumber.org>
Subject: [Bug 65271] New: Acceptable RST packets (with seq number in window) are ignored in LAST_ACK state (and previously sent data pending acknowledgement)
https://bugzilla.kernel.org/show_bug.cgi?id=65271
Bug ID: 65271
Summary: Acceptable RST packets (with seq number in window) are
ignored in LAST_ACK state (and previously sent data
pending acknowledgement)
Product: Networking
Version: 2.5
Kernel Version: 2.6.32.59-0.7-default
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@...ux-foundation.org
Reporter: julien.delacroix@...il.com
Regression: No
Created attachment 115271
--> https://bugzilla.kernel.org/attachment.cgi?id=115271&action=edit
TCP dump showing described scenario
PCAP file of traffic capture is attached.
Note that capture was taken directly on server host, so RST packets definitely
reached the server host.
Here is the flow:
1: Client ---- SYN ----> Server
2: Client <- SYN, ACK -- Server
3: Client ---- ACK ----> Server
4: Client ---- FIN ----> Server ( server in CLOSE_WAIT state)
5: Client <- PSH, ACK -- Server
6: Client <- FIN, ACK -- Server ( server in LAST_ACK state)
7: Client ---- RST ----> Server
Then repeat N times:
8: Client <- PSH, ACK -- Server
9: Client ---RST, ACK -> Server
Notes:
5: packet contains 3 bytes of data
7: no ACK flag, and sequence number is correct, but RST packet is ignored
8: retransmission of step 5
9: the sequence number is correct as well as the acknowledgment number
(acknowledging data in 5, but not yet FIN in 6), but this RST is again ignored.
>From this point client keeps retransmitting 5, while server keeps answering
with acceptable RST packets.
You can observe this scenario (with 5 retransmissions and 5 RST) in the
attached PCAP file.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists