Difference between revisions of "5-Tuple"
Jump to navigation
Jump to search
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | The tuple (source IP address, source port, destination IP address, destination port, transport protocol). A 5-tuple uniquely identifies a UDP/TCP session. When a [[UDP]]/[[TCP]] session flows through a NAT64, each session has two different 5-tuples: | + | The tuple (source [[IP]] address, source port, destination IP address, destination port, transport protocol). A 5-tuple uniquely identifies a UDP/TCP session. When a [[UDP]]/[[TCP]] session flows through a NAT64, each session has two different 5-tuples: |
one with IPv4 addresses and one with [[IPv6]] addresses. | one with IPv4 addresses and one with [[IPv6]] addresses. | ||
+ | |||
+ | == Related terms == | ||
+ | * [[3-Tuple]] | ||
+ | * [[NAT64]] | ||
== See also == | == See also == |
Latest revision as of 10:08, 17 July 2021
The tuple (source IP address, source port, destination IP address, destination port, transport protocol). A 5-tuple uniquely identifies a UDP/TCP session. When a UDP/TCP session flows through a NAT64, each session has two different 5-tuples: one with IPv4 addresses and one with IPv6 addresses.
Related terms[edit]
See also[edit]
- TCP/IP, Transport protocol, UDP, SCTP, QUIC, subnet mask, Routing protocols: BGP, routing table, Policy based routing, multicast, TCP Fast Open, RDP, TTL, RTT, MPTCP, Large send offload (LSO): (TSO, GRO, GSO, TCP checksum),
ethtool
, SCTP, 5-Tuple, Check TCP connectivity, TCP window size,/proc/sys/net/ipv4/tcp_rmem
, ack, List of TCP ports, localhost, broadcast address
Advertising: