From 78c896b3b3127515478090c19447e27dc406427e Mon Sep 17 00:00:00 2001 From: Jianfeng Tan Date: Mon, 18 Nov 2019 06:59:50 +0000 Subject: TLDKv2 Signed-off-by: Jianfeng Tan Signed-off-by: Jielong Zhou Signed-off-by: Jian Zhang Signed-off-by: Chen Zhao Change-Id: I55c39de4c6cd30f991f35631eb507f770230f08e --- .../tests/linux/listen/listen-incoming-syn-rst.pkt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 test/packetdrill/tests/linux/listen/listen-incoming-syn-rst.pkt (limited to 'test/packetdrill/tests/linux/listen/listen-incoming-syn-rst.pkt') diff --git a/test/packetdrill/tests/linux/listen/listen-incoming-syn-rst.pkt b/test/packetdrill/tests/linux/listen/listen-incoming-syn-rst.pkt new file mode 100644 index 0000000..f3c0607 --- /dev/null +++ b/test/packetdrill/tests/linux/listen/listen-incoming-syn-rst.pkt @@ -0,0 +1,22 @@ +// Test behavior when a listener gets an incoming packet that has +// the SYN and RST bits set. + +0.000 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3 +0.000 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 +0.000 bind(3, ..., ...) = 0 +0.000 listen(3, 1) = 0 + +0.100 < SR 0:0(0) win 32792 + +// The TCP stack should not respond to incoming RSTs, or else +// we could get infinite RST ping-pong storms. + +// Now make sure that when a valid SYN arrives shortly thereafter +// (with the same address 4-tuple) we can still successfully establish +// a connection. + +0.200 < S 0:0(0) win 32792 +0.200 > S. 0:0(0) ack 1 + +0.300 < . 1:1(0) ack 1 win 320 +0.300 accept(3, ..., ...) = 4 -- cgit 1.2.3-korg