Addressing scopes differ
An IP address identifies a source or destination for IP forwarding across networks. An Ethernet MAC address is used for delivery of a link-layer frame on a particular link. Both appear in communication, but they do not identify destinations over the same scope. A laptop contacting a distant web server does not ordinarily discover that remote server’s MAC address directly. It first uses routing information to decide whether to deliver locally or send to a next-hop router. Separating the IP route decision from link-layer delivery explains how a packet can cross networks without every host knowing every remote interface’s hardware address.
Delivering to a peer on the same link
Suppose routing selects direct delivery from host A to host B on one Ethernet link. For IPv4, A can use ARP to obtain the link-layer address corresponding to B’s IP address, then place it in the Ethernet destination field. A cached mapping can avoid another query. IPv6 uses ICMPv6 Neighbor Discovery rather than simply reusing IPv4 ARP. Neighbor mappings and DNS resolution solve different problems. A hostname resolving successfully does not prove that link-layer delivery has the information it needs. Inspect both the route and the neighbor state when packets fail locally despite apparently correct destination addresses.
Delivering through a router
When A sends to remote server C through next-hop router R, the first Ethernet destination is ordinarily R’s relevant interface, while the IP destination remains C. A does not put the distant server’s MAC into every frame along the path. R removes the incoming link-layer framing, makes an IP forwarding decision, and sends an appropriate frame on the next link. The MAC pair can change at each hop. This is the ordinary routing model; NAT, tunnels, and bridges require additional attention to the layer being observed. A packet capture at one location should not be generalized into an identical frame at every location on the path.
Place the two destination fields side by side
For an illustrative example, give A address192.0.2.10, a default gateway192.0.2.1, and a remote destination203.0.113.20. If routing selects the gateway, the immediately needed MAC mapping is for192.0.2.1. Write the remote IP destination beside the gateway’s link-layer destination to make the roles visible. An ARP table lacking the distant server is not, by itself, an error. Prefixes, route preferences, and virtual interfaces affect real configurations, so do not infer same-link reachability merely from the appearance of decimal addresses. Read the actual route selection before deciding which neighbor mapping should exist.
Do not treat an address as an unforgeable identity
A MAC address is not a permanent, unforgeable identity document for a person or device. Configuration changes, virtualization, and privacy randomization can alter observations. IP addresses likewise need not map one-to-one to people because of dynamic assignment, NAT, and proxies. Matching an address does not necessarily replace the authentication needed for sensitive access. For monitoring, define the scope and lifetime of the identifier and correlate it with application principals or connection records when appropriate. The networking function of an address and the security claim that a particular human is authorized are different questions, even when a product displays both in one log entry.
Locate the failing link and layer
A useful diagnosis separates local IP configuration, route selection, next-hop neighbor information, and the actual required application exchange. Missing neighbor information suggests a local-link investigation, but it does not by itself explain the complete remote-service incident. When capturing packets, record the interface and distinguish Ethernet header fields from IP header fields. Not every network uses Ethernet MAC framing, and a virtual interface or tunnel can expose a different representation. Preserve the assumptions of the worked example rather than applying its exact frame layout everywhere. The goal is to identify which delivery stage lacks evidence, then choose a measurement suited to that stage.