Searched refs:ACK (Results 1 – 20 of 20) sorted by relevance
| /tools/testing/selftests/net/packetdrill/ |
| A D | tcp_md5_md5-only-on-client-ack.pkt | 3 // but then does on the ACK that completes the three-way handshake.
15 // Ooh, weird: client provides MD5 option on the ACK:
22 // Now here comes the legit ACK:
|
| A D | tcp_fast_recovery_prr-ss-ack-below-snd_una-cubic.pkt | 3 // In this variant we verify that the sender uses SACK info on an ACK
36 // The following ACK was reordered - delayed so that it arrives with
37 // an ACK field below snd_una. Here we check that the newly-SACKed
|
| A D | tcp_sack_sack-shift-sacked-2-6-8-3-9-nofack.pkt | 45 // ACK for 1:1001 as packets from t=0.303 arrive.
49 // ACK for 1:4001 as packets from t=0.310 arrive.
53 // ACK for 1:7001 as packets from t=0.320 arrive.
56 // ACK for all data as packets from t=0.403 arrive.
|
| A D | tcp_close_close-local-close-then-remote-fin.pkt | 3 // the local process calls close() first, so we send a FIN, and receive an ACK.
4 // Then we receive a FIN and ACK it.
|
| A D | tcp_validate_validate-established-no-flags.pkt | 2 // Verify that established connections drop a segment without the ACK flag set.
22 // Receive a segment with ACK flag set, verify that it is enqueued.
|
| A D | tcp_blocking_blocking-write.pkt | 31 // This ACK should wakeup the write(). An ACK of 35001 does not.
|
| A D | tcp_ts_recent_invalid_ack.pkt | 2 // Test that we reject TS val updates on a packet with invalid ACK sequence
20 // bad packet with high tsval (its ACK sequence is above our sndnxt)
|
| A D | tcp_ecn_ecn-uses-ect0.pkt | 11 // ECN handshake: send EW flags in SYN packet, E flag in SYN-ACK response
|
| A D | tcp_slow_start_slow-start-ack-per-4pkt.pkt | 4 // In this variant, the receiver sends one ACK per 4 packets.
|
| A D | tcp_nagle_https_client.pkt | 34 // Without disabling Nagle, this packet will not happen until the remote ACK.
|
| A D | tcp_limited_transmit_limited-transmit-no-sack.pkt | 33 // We have one packet newly acked (1001:3001 were DUP-ACK'd)
|
| A D | tcp_nagle_sendmsg_msg_more.pkt | 45 // Err... we relase the remaining right after the ACK? note that PUSH is reset
|
| A D | tcp_sack_sack-shift-sacked-7-5-6-8-9-fack.pkt | 54 // To simplify clean-up, say we get an ACK for all data.
|
| A D | tcp_sack_sack-shift-sacked-7-3-4-8-9-fack.pkt | 58 // To simplify clean-up, say we get an ACK for all data.
|
| /tools/testing/selftests/net/netfilter/packetdrill/ |
| A D | conntrack_synack_reuse.pkt | 2 // Challenge ACK is supposed to pass through, RST reply should clear conntrack
8 +0 `iptables -A INPUT -m conntrack --ctstate INVALID -p tcp --tcp-flags SYN,ACK SYN,ACK`
|
| A D | conntrack_inexact_rst.pkt | 9 // 5.772212 client_ip > server_ip TCP 66 45020 > 443 [ACK] Seq=1905874048 Ack=781810658 Win=36352 …
12 // 5.788207 server_ip > client_ip TCP 66 443 > 45020 [FIN, ACK] Seq=781811916 Ack=1905874048 Win=3…
14 // 5.788479 client_ip > server_ip TCP 66 45020 > 443 [RST, ACK] Seq=1905874072 Ack=781811917 Win=3…
|
| A D | conntrack_syn_challenge_ack.pkt | 2 // a challenge-ACK.
24 // Challenge ACK, old incarnation.
|
| A D | conntrack_ack_loss_stall.pkt | 112 …REC=0x00 TTL=255 ID=0 PROTO=TCP SPT=34375 DPT=8080 SEQ=1 ACK=4162510439 WINDOW=257 RES=0x00 ACK PS…
|
| A D | conntrack_synack_old.pkt | 12 …LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=0 PROTO=TCP SPT=8080 DPT=34500 SEQ=162602411 ACK=2124350315 ..
|
| /tools/testing/selftests/bpf/prog_tests/ |
| A D | cls_redirect.c | 152 ACK, enumerator
201 else if (test->flags == ACK) in test_str()
210 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK },
211 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK },
212 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK },
310 if (test->flags == ACK) in build_input()
|
Completed in 17 milliseconds