← PROTOCOL LIBRARY

ICMP

NETWORK

Network control and error messages

LESSON PROGRESS1/2
READ FIRST · 60-SECOND BRIEF

THE PROBLEM

IP itself does not explain why a packet failed to reach its destination.

THE NAIVE APPROACH

Silently dropping every failed packet leaves the sender unable to distinguish routing, size and reachability problems.

THE KEY INSIGHT

ICMP carries structured control messages such as echo replies, time-exceeded and destination-unreachable.

WHERE YOU MEET IT

  • • Ping checking basic reachability
  • • Traceroute discovering hop responses
  • • Path MTU Discovery diagnosing packet-size limits

ANALOGY / HISTORY

Like a postal service returning a note that says the address is unknown or the parcel is too large.

Context: It complements IP rather than replacing a transport protocol.

3D NETWORK TOPOLOGY
SIMULATION
3D topologypacket animationlocal simulation
SELECTED NODE · CLIENT
Drag to orbit · packet movement is illustrative
CURRENT EXCHANGE
Echo request

client → server · ECHO REQUEST SENT

CONTROLLED LAB SIM

Echo request

An echo request asks the destination to return the identifier, sequence number and payload. The checksum covers the ICMP message.

BREAK IT · LOCAL ONLY
WHY THIS MATTERS

ICMP is carried directly inside IP; it does not use TCP or UDP ports.

BYTE INSPECTOR
0000 08 00 9a 88 1a 2b 00 01 61 62 63 64 65 66 67 68 |.....+..abcdefgh| 0010 69 6a 6b 6c 6d 6e 6f 70 |ijklmnop|
FIELD EXPLANATION

The ICMP Echo header is 8 bytes before the payload: type, code, checksum, identifier and sequence number.

Educational simulator · Byte examples are labelled by their level of fidelity in the lesson notes.
← Back to protocol library