Home
last modified time | relevance | path

Searched refs:TCP (Results 1 – 25 of 197) sorted by relevance

12345678

/linux/Documentation/networking/
H A Dtcp_ao.rst4 TCP Authentication Option Linux implementation (RFC5925)
7 TCP Authentication Option (TCP-AO) provides a TCP extension aimed at verifying
8 segments between trusted peers. It adds a new TCP header option with
10 of a TCP segment using a hashing function with a password known to both peers.
11 The intent of TCP-AO is to deprecate TCP-MD5 providing better security,
17 .. table:: Short and Limited Comparison of TCP-AO and TCP-MD5
20 | | TCP-MD5 | TCP-AO |
31 | | |TCP header permitted. |
34 |TCP connection | | |
45 |traffic-crossing | |includes TCP ports. |
[all …]
H A Dkcm.rst8 interface over TCP for generic application protocols. With KCM an application
9 can efficiently send and receive application protocol messages over TCP using
31 | TCP sock | | TCP sock | | TCP sock | | TCP sock | | TCP sock |
46 written on a KCM socket are sent atomically on an appropriate TCP socket.
47 Similarly, in the receive path, messages are constructed on each TCP socket
50 TCP sockets & Psocks
53 TCP sockets may be bound to a KCM multiplexor. A Psock structure is allocated
54 for each bound TCP socket, this structure holds the state for constructing
60 Each multiplexor assumes that all attached TCP connections are to the same
73 Messages are sent over a TCP stream with some application protocol message
[all …]
H A Dsnmp_counter.rst32 The number of packets delivers to the upper layer protocols. E.g. TCP, UDP,
249 General TCP counters
257 The number of packets received by the TCP layer. As mentioned in
259 error, invalid TCP header and so on. Only one error won't be included:
263 packets would be delivered to the TCP layer, but the TCP layer will discard
274 The number of packets sent by the TCP layer. As mentioned in RFC1213,
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
301 When packets are received by the TCP layer and are not be read by the
302 application, the TCP layer will try to merge them. This counter
[all …]
H A Dmptcp.rst4 Multipath TCP (MPTCP)
10 Multipath TCP or MPTCP is an extension to the standard TCP and is described in
12 device to make use of multiple interfaces at once to send and receive TCP
18 For more details about Multipath TCP in the Linux kernel, please see the
26 brings new use-cases, compared to TCP:
42 a regular TCP connection that is used to transmit data through one interface.
44 host to be able to detect the use of MPTCP, a new field is added to the TCP
45 *option* field of the underlying TCP *subflow*. This field contains, amongst
48 it, the returned ``SYN+ACK`` packet will not contain MPTCP options in the TCP
49 *option* field. In that case, the connection will be "downgraded" to plain TCP,
[all …]
H A Dproc_net_tcp.rst10 These /proc interfaces provide information about currently active TCP
14 It will first list all listening TCP sockets, and next list all established
15 TCP connections. A typical entry of /proc/net/tcp would look like this (split
20 | | | | |------> remote TCP port number
22 | | |--------------------> local TCP port number
H A Dpsp.rst75 PSP encryption is currently only supported for TCP connections.
77 Netlink command needs to be issued, specifying a target TCP socket.
80 and plain text TCP packets.
88 returns and before the TCP socket encounters it's first PSP
89 authenticated packet, where the TCP stack will allow certain nondata
90 packets, i.e. ACKs, FINs, and RSTs, to enter TCP receive processing
91 even if not PSP authenticated. During the ``tx-assoc`` call, the TCP
94 accepted at the latched value of ``rcv_nxt``. Once the TCP stack
95 encounters the first TCP packet containing PSP authenticated data, the
97 command, so any TCP packet, including those without data, will be
[all …]
H A Dtls-offload.rst10 Linux kernel provides TLS connection offload infrastructure. Once a TCP
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
31 with its own TCP handling, it is not usable in production environments
43 mode) and then hands the modified scatter list to the TCP layer. From this
44 point on the TCP stack proceeds as normal.
56 :c:type:`struct sk_buff <sk_buff>`. The packets reach the TCP stack and
101 which TCP sequence number corresponds to the beginning of the record with
112 number, simplifying TCP sequence number matching.
124 segmentation, so the initial records' TCP sequence number may be anywhere
136 * expected TCP sequence number
[all …]
H A Ddevmem.rst4 Device Memory TCP
11 Device memory TCP (devmem TCP) enables receiving data directly into device
12 memory (dmabuf). The feature is currently implemented for TCP sockets.
36 Devmem TCP optimizes this use case by implementing socket APIs that enable
41 Packet headers go to host memory and are processed by the TCP/IP stack
61 [PATCH net-next v24 00/13] Device Memory TCP
79 Header split, flow steering, & RSS are required features for devmem TCP.
134 devmem TCP, even if the dmabuf is not actually backed by devmem. An example of
211 regular TCP data that landed on an RX queue not bound to a dmabuf.
277 devmem TCP, even if the dmabuf is not actually backed by devmem. An example of
[all …]
H A Dstrparser.rst21 callback of a TCP socket. Messages are parsed and delivered as they are
47 strparser that is allocated by the upper layer. sk is the TCP
140 is unrecoverable (application expected to close TCP socket)
145 the error on TCP socket and wake it up. If parse_msg returned
197 the TCP socket in receive callback mode. The stream parser may
229 associated TCP socket. In general mode, the timeout is passed as an
231 the stream parser is aborted and the ETIMEDOUT error is set on the TCP
235 buffer size of the associated TCP socket. If the length returned by
237 is aborted with EMSGSIZE error set on the TCP socket. Note that this
239 parser to be 2*sk_rcvbuf of the TCP socket.
H A Dsegmentation-offloads.rst15 * TCP Segmentation Offload - TSO
24 TCP Segmentation Offload
27 TCP segmentation allows a device to segment a single frame into multiple
29 When TCP segmentation requested the bit for either SKB_GSO_TCPV4 or
33 TCP segmentation is dependent on support for the use of partial checksum
37 In order to support TCP segmentation offload it is necessary to populate
40 TCP header. In addition as CHECKSUM_PARTIAL is required csum_start should
41 also point to the TCP header of the packet.
143 it effectively does is take advantage of certain traits of TCP and tunnels
H A Dip-sysctl.rst44 protocols for which pmtu events will be honored are TCP and
48 TCP path mtu must still work but path MTU information of other
78 associated with a socket for example, TCP RSTs or ICMP echo replies).
330 TCP variables
336 See also tcp_max_syn_backlog for additional tuning for TCP sockets.
372 Enable TCP auto corking :
404 TCP SYN and SYNACK messages usually advertise an ADVMSS option,
423 Allows TCP to send "duplicate" SACKs.
445 Control use of Explicit Congestion Notification (ECN) by TCP.
446 ECN is used only when both ends of the TCP connection indicate support
[all …]
/linux/net/ipv4/
H A DKconfig269 bool "IP: TCP syncookie support"
271 Normal TCP/IP networking is open to an attack known as "SYN
278 say Y here, the TCP/IP stack will use a cryptographic challenge
281 is no need for the legitimate users to change their TCP/IP software;
384 bool "IP: ESP in TCP encapsulation (RFC 8229)"
391 TCP/IPv4 sockets.
428 Support for INET (TCP, UDP, etc) socket monitoring interface used by
470 bool "TCP: advanced congestion control"
472 Support for selection of various TCP congestion control
486 BIC-TCP is a sender-side only change that ensures a linear RTT
[all …]
/linux/net/mptcp/
H A DKconfig3 bool "MPTCP: Multipath TCP"
9 Multipath TCP (MPTCP) connections send and receive data over multiple
11 uses the TCP protocol, and TCP options carry header information for
21 bool "MPTCP: IPv6 support for Multipath TCP"
/linux/tools/testing/selftests/bpf/prog_tests/
H A Dcls_redirect.c97 TCP, enumerator
166 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, SYN },
167 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK },
168 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK },
169 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK },
269 case TCP: in build_input()
324 &servers[TCP][i], &conns[TCP][i], in test_cls_redirect_common()
325 &srcs[TCP][i], &dsts[TCP][i]))) in test_cls_redirect_common()
/linux/drivers/infiniband/sw/siw/
H A DKconfig2 tristate "Software RDMA over TCP/IP (iWARP) driver"
9 the Linux TCP/IP network stack. It enables a system with a
19 TCP/IP, the driver further interfaces with the Linux
20 in-kernel TCP socket layer.
/linux/tools/testing/selftests/net/netfilter/
H A Dnf_nat_edemux.sh61 ip netns exec "$ns1" socat -u TCP-LISTEN:5201,fork OPEN:/dev/null,wronly=1 &
78 sleep 10 | ip netns exec "$ns2" socat -t 10 - TCP:192.168.1.1:5201 > /dev/null &
85 echo test | ip netns exec "$ns2" socat -t 3 -u STDIN TCP:10.96.0.1:443,connect-timeout=3 >/dev/null
99 sleep 5 | ip netns exec "$ns2" socat -T 5 -u STDIN TCP:192.168.1.1:5202,connect-timeout=5 >/dev/nul…
102 sleep 5 | ip netns exec "$ns2" socat -T 5 -u STDIN TCP:192.168.1.1:5203,connect-timeout=5 >/dev/nul…
H A Dnft_conntrack_helper.sh117 ip netns exec "$ns2" socat -t 3 -u -4 TCP-LISTEN:"$port",reuseaddr STDOUT > /dev/null &
120 ip netns exec "$ns1" socat -u -4 STDIN TCP:10.0.1.2:"$port" < /dev/null > /dev/null
132 ip netns exec "$ns2" socat -t 3 -u -6 TCP-LISTEN:"$port",reuseaddr STDOUT > /dev/null &
135 ip netns exec "$ns1" socat -t 3 -u -6 STDIN TCP:"[dead:1::2]":"$port" < /dev/null > /dev/null
/linux/Documentation/translations/zh_CN/networking/
H A Dmsg_zerocopy.rst23 MSG_ZEROCOPY 标志用于启用套接字发送调用的免拷贝功能。该功能目前适用于 TCP、UDP 和 VSOCK
144 对于按顺序确认数据的协议(如 TCP),每个通知都可以合并到前一个通知中,因此在任何时候在等待
155 控制数据中的级别和类型字段是协议族特定的,对于 TCP 或 UDP 套接字,分别为 IP_RECVERR 或
205 对于 TCP 和 UDP:
H A Dnetmem.rst16 支持设备内存 TCP 等功能。通过支持netmem,驱动可以灵活适配不同底层内
17 存类型(如设备内存TCP),且无需或仅需少量修改。
22 使驱动程序能够支持设备内存 TCP 等各种用例。
/linux/tools/testing/selftests/net/netfilter/packetdrill/
H A Dconntrack_inexact_rst.pkt9 // 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…
15 // 5.788581 server_ip > client_ip TCP 54 8443 > 45020 [RST] Seq=781811892 Win=0 Len=0
/linux/net/rds/
H A DKconfig8 sequenced delivery of datagrams over Infiniband or TCP.
18 tristate "RDS over TCP"
22 Allow RDS to use TCP as a transport.
/linux/drivers/nvme/target/
H A DKconfig88 tristate "NVMe over Fabrics TCP target support"
92 This enables the NVMe TCP target support, which allows exporting NVMe
93 devices over TCP.
98 bool "NVMe over Fabrics TCP target TLS encryption support"
103 Enables TLS encryption for the NVMe TCP target using the netlink handshake API.
/linux/Documentation/networking/device_drivers/ethernet/microsoft/
H A Dnetvsc.rst20 support checksum offload for TCP and UDP for both IPv4 and
21 IPv6. Windows Server 2012 only supports checksum offload for TCP.
25 Hyper-V supports receive side scaling. For TCP & UDP, packets can
29 For TCP & UDP, we can switch hash level between L3 and L4 by ethtool
30 command. TCP/UDP over IPv4 and v6 can be set differently. The default
60 processing overhead by coalescing multiple TCP segments when possible. The
/linux/Documentation/networking/device_drivers/ethernet/freescale/
H A Dgianfar.rst15 the 8548) has the ability to perform TCP, UDP, and IP checksums
16 in hardware. The Linux kernel only offloads the TCP and UDP
18 the driver only supports checksumming for TCP/IP and UDP/IP
/linux/drivers/net/ethernet/wiznet/
H A DKconfig27 PHY and hardware TCP/IP stack, but this driver is limited to
28 the MAC and PHY functions only, onchip TCP/IP is unused.
40 PHY and hardware TCP/IP stack, but this driver is limited to
41 the MAC and PHY functions only, onchip TCP/IP is unused.

12345678