Local link
What must each device learn before this datagram can move, and which received frame proves it? Change one condition to separate the host's decision from the switch's decision.
Three experiments use this same ledger. Separate the tables: keep A's entry for 192.0.2.44 and clear only S1's entry for 02:00:00:00:01:44, then step the next emission. When you select D (198.51.100.44), the router resolves D's MAC address on link 2, then sends the datagram to D. The HTTPS entry examples use different destinations. They stop when the gateway accepts the local frame and do not model link 2 or a remote response. Change the non-target's history: the same request can arrive at C with an empty cache or with a prior entry for A. This note does not state what a host that is not the target keeps after a later unicast reply.
No datagram waiting
A queue empty. R2 queue empty.
Paused before the first commit.
This panel records EtherType, destination, and receipt fields. It does not ask for the transmitter, ARP opcode, target protocol address, egress ports, or cache effects.
Modeled packet fields
Model annotations
Instructor overview. Full model, not one device's knowledge.
Assumptions
These hosts use the static inventory. This preview does not simulate DHCP DISCOVER, OFFER, REQUEST, or ACK.
An ordinary request in this preview has the sender's own protocol address and the next hop as the target.
A later optional chapter can explain where an address and a gateway list come from. This preview does not simulate that configuration exchange.