ICMP: Echo, Errors and Network Diagnostics
ICMP carries control and error messages used by IP hosts and routers. It supports diagnostics, but it is not a reliable application transport and not every network forwards every message.
Updated · Editorial approach and simulation limits
Echo messages test a path, not an application
An ICMP Echo Request asks a destination to return an Echo Reply with matching identifier and sequence information. Ping tools use this exchange to test reachability and estimate round-trip time when policy permits it.
A missing reply does not prove that the host is down. Firewalls may filter echo traffic, return paths may differ, and the endpoint may be reachable for TCP while declining ICMP. Conversely, an echo reply does not prove that a web service or application port is working.
ICMP errors explain IP forwarding problems
Routers and hosts can send ICMP messages such as Destination Unreachable or Time Exceeded to report a network-layer condition. Traceroute techniques use changes in the IP hop limit and resulting time-exceeded responses to infer intermediate hops, subject to router policy and load balancing.
An ICMP error often includes part of the packet that caused it, allowing a sender to associate the report with a flow. Read the outer ICMP type and code with the quoted original IP header; the error is feedback about that packet, not a new application request.
IPv4 ICMP and ICMPv6 are related but distinct
RFC 792 specifies ICMP for IPv4. ICMPv6, specified separately, also supports core IPv6 functions such as Neighbor Discovery and Path MTU Discovery. Blocking all ICMPv6 can therefore break essential IPv6 behavior even if an IPv4 firewall policy appears to work.
Use the address family and ICMP type when interpreting a trace. Protocol Explorer’s ICMP lesson is a simplified IPv4 example; it does not imply that every ICMP message has the same role or filtering requirements.
Explore ICMP interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 792: Internet Control Message Protocol. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all network protocols · Use packet order to diagnose a network path