ACK (reference) in projects: third_party

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:ACK (Results 1 – 25 of 60) sorted by relevance

12 3

/third_party/iptables/iptables/tests/shell/testcases/ipt-save/dumps/
D	wireless.txt	29 -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m multiport --dports 22,80,443,873,1723 -j … 32 -A INPUT -s 10.31.70.8/29 -i bond0.208 -p tcp -m tcp --dport 179 --tcp-flags FIN,SYN,RST,ACK SYN -j… 33 -A INPUT -s 10.44.224.8/29 -i bond0.686 -p tcp -m tcp --dport 179 --tcp-flags FIN,SYN,RST,ACK SYN -… 56 -A CUST_I15_IN -p tcp -m tcp --dport 22 --tcp-flags FIN,SYN,RST,ACK SYN -j L_ACCEPT 57 -A CUST_I15_IN -p tcp -m tcp --dport 80 --tcp-flags FIN,SYN,RST,ACK SYN -j L_ACCEPT 58 -A CUST_I15_IN -p tcp -m tcp --dport 433 --tcp-flags FIN,SYN,RST,ACK SYN -j L_ACCEPT 59 -A CUST_I15_IN -p tcp -m tcp --dport 3306 --tcp-flags FIN,SYN,RST,ACK SYN -j L_ACCEPT 60 -A CUST_I15_IN -p tcp -m tcp --dport 3390 --tcp-flags FIN,SYN,RST,ACK SYN -j L_ACCEPT 62 -A CUST_I15_OUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m multiport --dports 80,443 -j L_ACC… 64 -A CUST_I16_IN -p tcp -m tcp --dport 3390 --tcp-flags FIN,SYN,RST,ACK SYN -j L_ACCEPT [all …]
D	ipt-save-filter.txt	`47 -A accept_log -i ppp0 -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -m limit --limit 1/sec -j LOG --log… 62 -A reject_log -i ppp0 -p tcp -m tcp --dport 22:80 --tcp-flags SYN,RST,ACK SYN -m limit --limit 1/se…`
/third_party/iptables/extensions/
D	libxt_tcp.t	`20 -p tcp -m tcp --syn;-p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN;OK 21 -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN;=;OK 22 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG SYN;=;OK 23 -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,PSH,ACK,URG SYN;=;OK 24 -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG RST;=;OK`
D	libxt_tcp.man	`24 .BR "SYN ACK FIN RST URG PSH ALL NONE" . 27 iptables \-A FORWARD \-p tcp \-\-tcp\-flags SYN,ACK,FIN,RST SYN 29 will only match packets with the SYN flag set, and the ACK, FIN and 33 Only match TCP packets with the SYN bit set and the ACK,RST and FIN bits 38 It is equivalent to \fB\-\-tcp\-flags SYN,RST,ACK,FIN SYN\fP.`
D	libxt_SYNPROXY.man	`53 Catch UNTRACKED (SYN packets) and INVALID (3WHS ACK packets) states 55 SYN+ACK syncookies, create ESTABLISHED for valid client response (3WHS ACK 57 during 3WHS will not match and continue (e.g. SYN+FIN, SYN+ACK).`
D	libxt_TCPMSS.t	`5 -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j TCPMSS --set-mss 42;=;OK 6 -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j TCPMSS --clamp-mss-to-pmtu;=;OK`
D	libxt_dccp.t	`21 -p dccp -m dccp --dccp-types REQUEST,RESPONSE,DATA,ACK,DATAACK,CLOSEREQ,CLOSE,RESET,SYNC,SYNCACK,IN… 22 -p dccp -m dccp ! --dccp-types REQUEST,RESPONSE,DATA,ACK,DATAACK,CLOSEREQ,CLOSE,RESET,SYNC,SYNCACK,…`
D	libxt_tcpmss.man	`1 …nt size) field of the TCP header. You can only use this on TCP SYN or SYN/ACK packets, since the …`
D	libxt_dccp.man	`9 .BR "REQUEST RESPONSE DATA ACK DATAACK CLOSEREQ CLOSE RESET SYNC SYNCACK INVALID" .`
D	libxt_dccp.txlate	`16 iptables-translate -A INPUT -p dccp -m dccp --dport 100 --dccp-types REQUEST,RESPONSE,DATA,ACK,DATA…`
D	libxt_tcp.txlate	`13 iptables -A INPUT -p tcp --tcp-flags ACK,FIN FIN -j DROP`
/third_party/gstreamer/gstreamer/docs/random/wtay/
D	threads_hilevel	`49 wait for ACK (release lock) ! 72 wait for ACK (release lock) ! 92 wait for ACK (release lock) ! 135 wait for ACK (release lock) ! 153 wait for ACK (release lock) !`
/third_party/musl/porting/liteos_m_iccarm/kernel/include/arpa/
D	tftp.h	`7 #define ACK 04 macro`
/third_party/musl/ndk_musl_include/arpa/
D	tftp.h	`7 #define ACK 04 macro`
/third_party/musl/porting/liteos_m/kernel/include/arpa/
D	tftp.h	`7 #define ACK 04 macro`
/third_party/musl/include/arpa/
D	tftp.h	`7 #define ACK 04 macro`
/third_party/musl/porting/uniproton/kernel/include/arpa/
D	tftp.h	`7 #define ACK 04 macro`
/third_party/libcoap/man/
D	coap_async.txt.in	`57 For separate responses, there is an initial empty ACK response (Confirmable 114 * response (empty ACK followed by data response at a later stage). 154 * Not setting response code will cause empty ACK to be sent`
/third_party/grpc/src/proto/grpc/testing/xds/v3/
D	discovery.proto	`48 // response is received until the Envoy instance is ready to ACK/NACK the new 49 // configuration. ACK/NACK takes place by returning the new API config version 71 // nonce corresponding to DiscoveryResponse being ACK/NACKed. See above`
/third_party/openssl/doc/man3/
D	SSL_connect.pod	`40 corresponding ACK has been received yet from the peer. This can have performance 44 typical for many protocols) then this data could be buffered until an ACK has`
/third_party/python/Lib/curses/
D	ascii.py	`9 ACK = 0x06 # ^F variable`
/third_party/iptables/utils/
D	pf.os	36 # performance control (max. amount of data to be sent without ACK). 96 # - Selective ACK permitted - a flag set by systems that implement 97 # selective ACK functionality. 99 # - The sequence of TCP all options (MSS, window scaling, selective ACK 103 # header padding) and sackOK option (selective ACK feature). 144 # S - selective ACK OK 170 # at SYN+ACK - does it look similar? 173 # functionality, enable or disable timestamps or selective ACK, 247 # selective ACK: 553 # Another hardcore MSS, one of the ACK leakers hunted down.
/third_party/jerryscript/targets/curie_bsp/
D	README.md	114 js e print ('Hello World!');js e 1 ACK 120 `js e 1 ACK` and `js e 1 OK` are debug info of Curie BSP uart commands, which mean it receive and e…
/third_party/wpa_supplicant/wpa_supplicant-2.9_standard/wpa_supplicant/
D	eap_testing.txt	`361 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE 367 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE 384 - sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK 389 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE`
/third_party/wpa_supplicant/wpa_supplicant-2.9/wpa_supplicant/
D	eap_testing.txt	`361 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE 367 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE 384 - sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK 389 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE`

12 3