Home
last modified time | relevance | path

Searched refs:SYN (Results 1 – 14 of 14) sorted by relevance

/linux-6.3-rc2/Documentation/networking/
A Dsnmp_counter.rst286 It means the TCP layer sends a SYN, and come into the SYN-SENT
296 It means the TCP layer receives a SYN, replies a SYN+ACK, come into
297 the SYN-RCVD state.
329 TCPSynRetrans: number of SYN and SYN/ACK retransmits to break down
800 TCP stack receives a SYN and replies SYN+ACK. Now the TCP stack is
964 SYN cookies
966 SYN cookies are used to mitigate SYN flood, for details, please refer
1110 SYN, sent SYN+ACK, received ACK, so server sent 1 packet, received 2
1115 When the client sent SYN, the client came into the SYN-SENT state, so
1592 re-send the SYN packet if it didn't receive a SYN+ACK, we could find
[all …]
A Dip-sysctl.rst373 TCP SYN and SYNACK messages usually advertise an ADVMSS option,
770 overflows. This is to prevent against the common 'SYN flood attack'
775 against legal connection rate. If you see SYN flood warnings
785 SYN flood warnings in logs not being really flooded, your server
794 the initial SYN packet is received during the three-way handshake.
819 SYN packet.
823 rather than connect() to send data in SYN.
835 a SYN packet to be accepted and passed to the
837 0x4 (client) send data in the opening SYN regardless of cookie
839 0x200 (server) accept data-in-SYN w/o any cookie option present.
[all …]
A Dipvs-sysctl.rst108 the SYN-RECV/SYNACK state, which should be effective against
/linux-6.3-rc2/Documentation/driver-api/surface_aggregator/
A Dssh.rst8 .. |SYN| replace:: ``SYN`` substdef
93 * - |SYN|
97 A message consists of |SYN|, followed by the frame (|TYPE|, |LEN|, |SEQ| and
140 Each exchange begins with |SYN|, followed by a |DATA_SEQ|- or
165 tx: -- SYN FRAME(D) CRC(F) PAYLOAD CRC(P) -----------------------------
166 rx: ------------------------------------- SYN FRAME(A) CRC(F) CRC(P) --
175 tx: -- SYN FRAME(D) CRC(F) PAYLOAD CRC(P) -----------------------------
176 rx: ------------------------------------- SYN FRAME(N) CRC(F) CRC(P) --
184 tx: -- SYN FRAME(DATA_NSQ) CRC(F) PAYLOAD CRC(P) ----------------------
/linux-6.3-rc2/tools/testing/selftests/bpf/prog_tests/
A Dcls_redirect.c182 SYN, enumerator
230 if (test->flags == SYN) in test_str()
240 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, SYN },
339 if (test->flags == SYN) in build_input()
/linux-6.3-rc2/tools/perf/trace/beauty/
A Dmsg_flags.c46 P_MSG_FLAG(SYN); in syscall_arg__scnprintf_msg_flags()
/linux-6.3-rc2/net/ipv4/
A DKconfig271 Normal TCP/IP networking is open to an attack known as "SYN
277 SYN cookies provide protection against this type of attack. If you
279 protocol known as "SYN cookies" to enable legitimate users to
282 SYN cookies work transparently to them. For technical information
283 about SYN cookies, check out <https://cr.yp.to/syncookies.html>.
285 If you are SYN flooded, the source address reported by the kernel is
290 SYN cookies may prevent correct error reporting on clients when the
294 If you say Y here, you can disable SYN cookies at run time by
/linux-6.3-rc2/tools/testing/selftests/bpf/progs/
A Dtest_cls_redirect.c80 SYN, enumerator
827 return SYN; in process_tcp()
1056 case SYN: in cls_redirect()
/linux-6.3-rc2/net/netfilter/
A DKconfig673 during SYN-flood attacks.
1125 MSS value of TCP SYN packets, to control the maximum size for that
1141 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
1468 analyzing incoming TCP SYN packets.
1628 MSS value of TCP SYN packets, which control the maximum packet size
/linux-6.3-rc2/net/ipv6/netfilter/
A DKconfig217 during SYN-flood attacks.
/linux-6.3-rc2/net/ipv4/netfilter/
A DKconfig204 during SYN-flood attacks.
/linux-6.3-rc2/Documentation/networking/devlink/
A Ddevlink-trap.rst460 This could include TCP checksum errors, improper combination of SYN, FIN
/linux-6.3-rc2/drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/
A Dphy_n.c38 write_radio_reg(pi, radio_type##_##SYN##_##reg_name, value)
/linux-6.3-rc2/
A DMAINTAINERS10149 K: \b(ABS|SYN)_MT_

Completed in 65 milliseconds