summaryrefslogtreecommitdiffhomepage
path: root/test/packetimpact/tests/BUILD
diff options
context:
space:
mode:
authorMithun Iyer <iyerm@google.com>2020-09-01 17:40:28 -0700
committergVisor bot <gvisor-bot@google.com>2020-09-01 17:45:04 -0700
commit40faeaa180a30906da4822a105c43fcdb996750d (patch)
tree3f82e1f27216de4504560168a2dfe352ce11815b /test/packetimpact/tests/BUILD
parentc67d8ece09f44900951c5e20d9c551b9759c7aba (diff)
Fix handling of unacceptable ACKs during close.
On receiving an ACK with unacceptable ACK number, in a closing state, TCP, needs to reply back with an ACK with correct seq and ack numbers and remain in same state. This change is as per RFC793 page 37, but with a difference that it does not apply to ESTABLISHED state, just as in Linux. Also add more tests to check for OTW sequence number and unacceptable ack numbers in these states. Fixes #3785 PiperOrigin-RevId: 329616283
Diffstat (limited to 'test/packetimpact/tests/BUILD')
-rw-r--r--test/packetimpact/tests/BUILD4
1 files changed, 2 insertions, 2 deletions
diff --git a/test/packetimpact/tests/BUILD b/test/packetimpact/tests/BUILD
index 74658fea0..e1ed0cc60 100644
--- a/test/packetimpact/tests/BUILD
+++ b/test/packetimpact/tests/BUILD
@@ -166,8 +166,8 @@ packetimpact_go_test(
)
packetimpact_go_test(
- name = "tcp_close_wait_ack",
- srcs = ["tcp_close_wait_ack_test.go"],
+ name = "tcp_unacc_seq_ack",
+ srcs = ["tcp_unacc_seq_ack_test.go"],
deps = [
"//pkg/tcpip/header",
"//pkg/tcpip/seqnum",