/openbmc/linux/Documentation/networking/ |
H A D | snmp_counter.rst | 286 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 …]
|
H A D | ip-sysctl.rst | 376 TCP SYN and SYNACK messages usually advertise an ADVMSS option, 773 overflows. This is to prevent against the common 'SYN flood attack' 778 against legal connection rate. If you see SYN flood warnings 788 SYN flood warnings in logs not being really flooded, your server 797 the initial SYN packet is received during the three-way handshake. 822 SYN packet. 826 rather than connect() to send data in SYN. 838 a SYN packet to be accepted and passed to the 840 0x4 (client) send data in the opening SYN regardless of cookie 842 0x200 (server) accept data-in-SYN w/o any cookie option present. [all …]
|
H A D | ipvs-sysctl.rst | 108 the SYN-RECV/SYNACK state, which should be effective against
|
/openbmc/linux/Documentation/driver-api/surface_aggregator/ |
H A D | ssh.rst | 8 .. |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) ----------------------
|
/openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
H A D | cls_redirect.c | 183 SYN, enumerator 231 if (test->flags == SYN) in test_str() 241 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, SYN }, 340 if (test->flags == SYN) in build_input()
|
/openbmc/linux/tools/perf/trace/beauty/ |
H A D | msg_flags.c | 52 P_MSG_FLAG(SYN); in syscall_arg__scnprintf_msg_flags()
|
/openbmc/openbmc-test-automation/lib/ |
H A D | bmc_network_security_utils.robot | 44 # flags Type of flag to be set (e.g. SYN, ACK, RST, FIN, ALL).
|
H A D | resource.robot | 109 ${SYN_PACKETS} SYN
|
/openbmc/linux/net/ipv4/ |
H A D | Kconfig | 271 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
|
/openbmc/linux/tools/testing/selftests/bpf/progs/ |
H A D | test_cls_redirect_dynptr.c | 75 SYN, enumerator 721 return SYN; in process_tcp() 955 case SYN: in cls_redirect()
|
H A D | test_cls_redirect.c | 80 SYN, enumerator 827 return SYN; in process_tcp() 1056 case SYN: in cls_redirect()
|
/openbmc/linux/drivers/net/ethernet/sfc/ |
H A D | tc_conntrack.c | 255 tcp_interesting_flags = EFX_NF_TCP_FLAG(SYN) | in efx_tc_ct_parse_match()
|
/openbmc/linux/net/netfilter/ |
H A D | Kconfig | 676 during SYN-flood attacks. 1127 MSS value of TCP SYN packets, to control the maximum size for that 1143 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \ 1470 analyzing incoming TCP SYN packets. 1630 MSS value of TCP SYN packets, which control the maximum packet size
|
/openbmc/linux/net/ipv6/netfilter/ |
H A D | Kconfig | 217 during SYN-flood attacks.
|
/openbmc/linux/net/ipv4/netfilter/ |
H A D | Kconfig | 204 during SYN-flood attacks.
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | devlink-trap.rst | 460 This could include TCP checksum errors, improper combination of SYN, FIN
|
/openbmc/openbmc/meta-security/recipes-ids/suricata/files/ |
H A D | suricata.yaml | 683 # max-synack-queued: 5 # Max different SYN/ACKs to queue
|
/openbmc/linux/drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/ |
H A D | phy_n.c | 38 write_radio_reg(pi, radio_type##_##SYN##_##reg_name, value)
|
/openbmc/linux/ |
H A D | MAINTAINERS | 10419 K: \b(ABS|SYN)_MT_
|