summaryrefslogtreecommitdiffhomepage
path: root/test/packetimpact/tests/BUILD
diff options
context:
space:
mode:
authorTony Gong <gongt@google.com>2020-07-07 16:13:21 -0700
committergVisor bot <gvisor-bot@google.com>2020-07-07 16:14:49 -0700
commit76c7bc51b7b02c4ba83c0a064c3629bb5ee91340 (patch)
tree48c1525ebbb54fc47a3cbd46c4e3efee957300aa /test/packetimpact/tests/BUILD
parent7e4d2d63eef3f643222181b3a227bfc7ebe44db2 (diff)
Set IPv4 ID on all non-atomic datagrams
RFC 6864 imposes various restrictions on the uniqueness of the IPv4 Identification field for non-atomic datagrams, defined as an IP datagram that either can be fragmented (DF=0) or is already a fragment (MF=1 or positive fragment offset). In order to be compliant, the ID field is assigned for all non-atomic datagrams. Add a TCP unit test that induces retransmissions and checks that the IPv4 ID field is unique every time. Add basic handling of the IP_MTU_DISCOVER socket option so that the option can be used to disable PMTU discovery, effectively setting DF=0. Attempting to set the sockopt to anything other than disabled will fail because PMTU discovery is currently not implemented, and the default behavior matches that of disabled. PiperOrigin-RevId: 320081842
Diffstat (limited to 'test/packetimpact/tests/BUILD')
-rw-r--r--test/packetimpact/tests/BUILD2
1 files changed, 0 insertions, 2 deletions
diff --git a/test/packetimpact/tests/BUILD b/test/packetimpact/tests/BUILD
index 85749c559..3ecbe83eb 100644
--- a/test/packetimpact/tests/BUILD
+++ b/test/packetimpact/tests/BUILD
@@ -18,8 +18,6 @@ packetimpact_go_test(
packetimpact_go_test(
name = "ipv4_id_uniqueness",
srcs = ["ipv4_id_uniqueness_test.go"],
- # TODO(b/157506701) Fix netstack then remove the line below.
- expect_netstack_failure = True,
deps = [
"//pkg/abi/linux",
"//pkg/tcpip/header",