About this tool
One packet can cross several local networks before reaching its destination. This walkthrough connects subnet decisions, next-hop delivery and router forwarding into a single story. It is especially useful after DNS, DHCP and ARP because it shows where those earlier concepts fit. The simulation illustrates a path; it does not trace packets from your real computer.
How it works
- Inspect the source, destination and displayed topology.
- Run the walkthrough and follow the current hop.
- Check whether delivery is local or needs a gateway.
- Compare the IP packet with the link-layer frame at each hop.
Worked example
Host 192.168.1.10/24 sends to 192.168.2.20/24 through gateway 192.168.1.1. On the first LAN, its Ethernet frame targets the gateway's MAC. Without NAT, the IP destination remains 192.168.2.20. The router removes that frame and creates a new one for the next link, decrementing IPv4 TTL.
Common mistakes
Do not replace the remote destination IP with the gateway IP when describing ordinary forwarding. Ethernet MAC addresses apply to a local link, not the whole path. Routers choose routes using destination prefixes, not the destination's website name.
FAQ
Does every hop change the source IP?
No. Ordinary routing preserves source and destination IP addresses. NAT is a separate function that can translate addresses, and sometimes ports, at the translating device.