Answer by Ricky for The Reasoning Behind TCP and UDP Multiplexing Tuple
You assume a host has one, and only one, IP address. This is rarely true. If you count loopback, which every machine has, there will always be at least two. In the modern world, it's very likely you'll...
View ArticleAnswer by Zac67 for The Reasoning Behind TCP and UDP Multiplexing Tuple
From a host stack's perspective, different local IP addresses mean different interfaces (mostly), even though they may be bound to the same physical interface.Likewise, the local TCP ports 192.0.2.1:80...
View ArticleThe Reasoning Behind TCP and UDP Multiplexing Tuple
I understand that TCP and UDP are multiplexed protocols, and the multiplexing key in them is the (sender.ip, sender.port, receiver.ip, receiver.port) tuple. I understand the reasoning behind sender.ip,...
View ArticleAnswer by pepoluan for The Reasoning Behind TCP and UDP Multiplexing Tuple
A server can have multiple IP addresses, even if it only has 1 NIC.In fact, every host has at least 2 IP addresses: The host's Layer 3 identifier, and the host's loopback address.A service can choose...
View ArticleAnswer by akostadinov for The Reasoning Behind TCP and UDP Multiplexing Tuple
First of all the address parts are in the IP layer, not the TCP/UDP/Transport layer itself. But answering the question further regardless.I would list all purposes that come to mind:you need the...
View ArticleAnswer by Austin Hemmelgarn for The Reasoning Behind TCP and UDP Multiplexing...
Because the receiver address is required to uniquely identify a given flow.Consider the case where two different clients connect to the same web server, and they happen to pick the same ephemeral port...
View Article
