
A ping looks like one event. In 3D Live you can stop it on the wire and see that it isn't.
Two PCs and a router on one switch are enough, with the router's port up. Build them in the lab, press 3D Live, and go to the Send real traffic panel:
Everything freezes, and On the wire now lists each frame crossing a cable at that instant. Press . to step forward and , to step back, or use the Timeline's buttons. Click a row to read its addresses.
Here's what to look for:
That last step is the one to notice. Your ping existed the whole time, but PC-A held it until ARP gave it a MAC address to send to.
The engine log already shows the reply while you're paused, because the simulator has finished and the animation is replaying it slowly. Press Live to return to real time.
3D Live is free on every plan and opens without an account. Start in the NetForge-AI lab, then press 3D Live.
I typed ping 10.0.0.2 from PC1 and it worked. But what really happened before the first reply came back — especially the very first time, with empty caches?

Ping across a router with cold caches and you often get one Request timed out., then replies. Ping again and all four come back. The usual explanation is "ARP". That's true, but it skips the interesting part: two devices needed ARP for that ping, and only one of them cost you the echo.
You can prove which one. The network is PC-A (192.168.10.10), the router Edge, and PC-B (192.168.20.10). PC-A needs its gateway's MAC address, and Edge needs PC-B's. So clear one cache at a time and ping from PC-A.
Clear only the PC. Run arp -d * on PC-A. It has to ARP for its gateway all over again, yet all four replies come back.
Clear only the router. Run clear arp-cache on Edge. The timeout is back.
Why the difference? A PC that needs a MAC address holds the packet until the ARP reply arrives, so its ARP costs a moment and nothing more. Many routers don't hold it. They start ARP and drop the packet that triggered it, and the next echo finds the entry ready.
That makes the lost echo useful evidence. One timeout followed by steady replies means the path works and a router along it had to look up its next hop, so there's nothing to fix. A timeout on every echo is a different problem, and that one does need troubleshooting.
Run the experiment yourself: finish the Two LANs, one router guided build, then clear each cache in turn.
Jump into a hands-on lab challenge
NetForge-AI is an independent educational platform and is not affiliated with, endorsed by, or sponsored by any networking vendor or certification body. All product names, protocols, and standards referenced are the property of their respective owners and are used for descriptive, educational purposes only.