Insight Vault

Final Mental Model: Host, Route, Link, and Socket

2 min read

Learning Question

What final model should remain after the host reachability details are separated?

A host reaches another host through a chain of decisions and boundaries. The chain is not a direct call from one program into another program. It is a movement from application intent into operating-system communication state, route selection, local link delivery, and forwarding across networks.

The Ordered Model

Use this sequence:

application wants communication
-> process uses a socket
-> OS identifies destination address and port
-> route lookup chooses interface and next hop
-> local link delivery uses a MAC address or equivalent link-layer target
-> network devices forward toward the destination
-> receiving host delivers bytes to the right socket and process
-> application protocol assigns meaning to the bytes

Each step has a different owner.

The Main Distinctions

Keep these distinctions separate:

LAN
local-site network scope
 
IP subnet
address prefix
 
connected route
host's direct reachability rule for a prefix
 
gateway
local next hop for remote destinations
 
ARP
local IPv4 mapping from on-link IP to MAC address
 
socket
OS-managed endpoint used by a process
 
application protocol
rules that define the meaning of exchanged bytes

Confusing any pair can produce wrong diagnoses. For example, a device can be on the same Wi-Fi but isolated by configuration. A destination IP can be remote while the gateway is local. A socket can exist while the remote application is not speaking the expected protocol.

Diagnostic Questions

When a host cannot reach another host, ask in order:

  1. Which destination IP and port is the program trying to use?
  2. Which local interface and source address would the host choose?
  3. Which route matches the destination?
  4. Is the next hop the final destination or a gateway?
  5. Can the host resolve the next hop’s link-layer address?
  6. Can frames leave the local link and be forwarded onward?
  7. Is the receiving host and socket reachable?
  8. Does the application protocol conversation make sense after reachability works?

Final Summary

Host reachability is the path from local intent to a network destination. It is built from interfaces, IP addresses, routes, next hops, local link delivery, and sockets.

The durable correction is:

Reaching a host is lower than speaking an application protocol.
Speaking an application protocol is lower than executing application meaning.

This layered model makes network behavior easier to understand and harder to confuse.

Backlinks

Graph View