authentication header
IP option pseudo header for BEET
Compression Header Protocol
Datagram Congestion Control Protocol
IPv6 destination options
Exterior Gateway Protocol
Encapsulation Header
encapsulating security payload
IPv6 fragmentation header
General Routing Encapsulation
IPv6 Hop-by-Hop options
Internet Control Message Protocol
ICMPv6
XNS IDP protocol
Internet Group Management Protocol
Dummy protocol for TCP
IPIP tunnels (older KA9Q tunnels use 94)
IPv6 header
IPv6 mobility header
MPLS in IP
Multicast Transport Protocol
IPv6 no next header
Protocol Independent Multicast
PUP protocol
Raw IP packets
IPv6 routing header
Reservation Protocol
Stream Control Transmission Protocol
Transmission Control Protocol
SO Transport Protocol Class 4
User Datagram Protocol
UDP-Lite protocol
Shutdown state of a socket. A socket shut down with SHUT_RD
can
no longer receive data. See also man 2 shutdown
.
Shutdown state of a socket. A socket shut down with SHUT_RDWR
can no longer receive nor send data. See also man 2 shutdown
.
Shutdown state of a socket. A socket shut down with SHUT_WR
can
no longer send data. See also man 2 shutdown
.
Supports datagrams (connectionless, unreliable messages of a fixed
maximum length).
Obsolete and should not be used in new programs; see packet(7)
.
Provides raw network protocol access.
Provides a reliable datagram layer that does not guarantee
ordering.
Provides a sequenced, reliable, two-way connection-based data
transmission path for datagrams of fixed maximum length; a
consumer is required to read an entire packet with each input
system call.
Provides sequenced, reliable, two-way, connection-based byte
streams. An out-of-band data transmission mechanism may be
supported.
ECN was negociated at TCP session init
We received at least one packet with ECT
SYN-ACK acked data in SYN sent or rcvd
The sender enters Congestion Window Reduction (CWR) state when it
has received ACKs with ECN-ECE marks, or has experienced
congestion or packet discard on the sender host (e.g. qdisc).
The sender enters disordered state when it has received DUPACKs or
SACKs in the last round of packets sent. This could be due to
packet loss or reordering but needs further information to confirm
packets have been lost.
The sender is in loss recovery triggered by retransmission timeout.
Nothing bad has been observed recently. No apparent reordering, packet loss,
or ECN marks.
The sender is in fast recovery and retransmitting lost packets, typically
triggered by ACK events.
(both server and client) represents no connection state at all.
(both server and client) represents waiting for a connection
termination request from the local user.
(both server and client) represents waiting for a connection termination
request acknowledgment from the remote TCP.
(both server and client) represents an open connection, data
received can be delivered to the user. The normal state for the
data transfer phase of the connection.
(both server and client) represents waiting for a connection
termination request from the remote TCP, or an acknowledgment of
the connection termination request previously sent.
(both server and client) represents waiting for a connection
termination request from the remote TCP.
(both server and client) represents waiting for an acknowledgment
of the connection termination request previously sent to the
remote TCP (which includes an acknowledgment of its connection
termination request).
(server) represents waiting for a connection request from any
remote TCP and port.
(server) represents waiting for a confirming connection request
acknowledgment after having both received and sent a connection
request.
(client) represents waiting for a matching connection request
after having sent a connection request.
(either server or client) represents waiting for enough time to
pass to be sure the remote TCP received the acknowledgment of its
connection termination request.
The attribute reported in answer to this request is
UNIX_DIAG_ICONS
, which information about pending
connections. Specifically, it contains the inode numbers of the
sockets that have passed the connect(2)
call, but hasn’t been
processed with accept(2) yet
. This attribute is reported for
listening sockets only.
The attribute reported in answer to this request is
UNIX_DIAG_MEMINFO
which shows memory information about the
socket
The attribute reported in answer to this request is
UNIX_DIAG_NAME
. The payload associated with this attribute is
the pathname to which the socket was bound (a se quence of bytes
up to UNIX_PATH_MAX
length).
The attribute reported in answer to this request is
UNIX_DIAG_PEER
, which carries the peer’s inode number. This
attribute is reported for connected sockets only.
The attribute reported in answer to this request is
UNIX_DIAG_RQLEN
, which reports:
The attribute reported in answer to this request is
UNIX_DIAG_VFS
, which returns VFS information associated to the
inode.