Networking: ICMP and Ping

Networking · Last updated · About 3 min read

What ICMP Is

ICMP (Internet Control Message Protocol) is IP's built-in signaling channel — not a data transport like TCP/UDP, but the protocol routers and hosts use to report conditions about IP delivery itself: destination unreachable, time exceeded, fragmentation needed, and the echo request/reply pair that ping is built on.

Ping: What It Proves and What It Doesn't

ping sends ICMP echo requests and measures replies — the first tool out of the bag in every network-layer troubleshooting flow (see Troubleshooting RoIP and Gateway Connectivity). Interpreting it correctly matters more than running it:

  • A reply proves the IP path works both directions at that moment — routing, addressing, and basic reachability.
  • Ping success ≠ application success: ICMP passing while the application's TCP/UDP ports are blocked yields "pings fine, still broken" — check the actual ports next (Firewall Types).
  • Round-trip times are a floor, not the whole story: sustained pings reveal loss and the min/max spread (a crude jitter view — see Latency, Jitter, and Packet Loss in Voice Networks), but say nothing about one-way asymmetry or application-layer delay.

Useful variants: sustained ping (ping -t on Windows) to catch intermittents; sized pings with don't-fragment set to probe VPN MTU problems (the "small packets pass, big ones vanish" signature).

Traceroute

Traceroute (tracert on Windows) maps the router path by sending probes with increasing TTL (time-to-live) values; each router that decrements TTL to zero returns an ICMP "time exceeded," revealing itself as a hop. It localizes where along a path delay or loss begins — with the caveat that many routers deprioritize or suppress their ICMP responses, so a "slow" or silent middle hop that still passes traffic normally is common and not itself proof of a problem; judge the end-to-end result and the point where all subsequent hops degrade.

ICMP Beyond Ping

  • Destination unreachable messages are how a sender learns a port/host/network can't be reached — some firewalls send them on blocks (fast, informative failures), others silently drop (slow timeouts). This difference alone explains why some failures are instant and others hang.
  • Fragmentation needed (with don't-fragment set) is the mechanism behind path-MTU discovery; networks that block all ICMP can break PMTU discovery and cause exactly the selective large-packet failures documented for VPN tunnels.
  • Blanket "block all ICMP" firewall policies are therefore heavier-handed than they look; hardened designs typically rate-limit or selectively allow the operationally necessary types.

References

This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.

Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.