From 11e07d63ecd409a5d3ab4a6c2fae3176d674ed39 Mon Sep 17 00:00:00 2001
From: Shivansh Rai <shivanshrai84@gmail.com>
Date: Fri, 25 Mar 2016 05:17:03 +0600
Subject: [PATCH] Test for behavior when sending a packet with RST bit set but
 no SYN bit set

---
 .../bsd/tcp/listen/listen-incoming-rst.pkt    | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 gtests/net/packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt

diff --git a/gtests/net/packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt b/gtests/net/packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt
new file mode 100644
index 00000000..4923468c
--- /dev/null
+++ b/gtests/net/packetdrill/tests/bsd/tcp/listen/listen-incoming-rst.pkt
@@ -0,0 +1,22 @@
+// Test behavior when a listener gets an incoming packet that has
+// the RST bit set but not the SYN bit 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 < R 0:0(0) win 65535 <mss 1460,sackOK,nop,nop,nop,wscale 7>
+
+// 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 65535 <mss 1460,sackOK,nop,nop,nop,wscale 7>
+0.200 > S. 0:0(0) ack 1 <...>
+
+0.300 < . 1:1(0) ack 1 win 65535
+0.300 accept(3, ..., ...) = 4
-- 
GitLab