From Wikipedia, the free encyclopedia

The five layer TCP/IP model

5. Application layer

DHCP • DNS • FTP • HTTP • IMAP4 • IRC • NNTP • XMPP • MIME • POP3 • SIP • SMTP • SNMP • SSH • TELNET • BGP • RPC • RTP • RTCP • TLS/SSL • SDP • SOAP • L2TP • PPTP • …

4. Transport layer

TCP • UDP • DCCP • SCTP • GTP • …

3. Network layer

IP (IPv4 • IPv6) • ICMP • IGMP • RSVP • IPsec • …

2. Data link layer

ATM • DTM • Ethernet • FDDI • Frame Relay • GPRS • PPP • ARP • RARP • …

1. Physical layer

Ethernet physical layer • ISDN • Modems • PLC • SONET/SDH • G.709 • Wi-Fi • …

This box: view • talk • edit

The Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet protocol suite. It is chiefly used by networked computers' operating systems to send error messages—indicating, for instance, that a requested service is not available or that a host or router could not be reached.

ICMP differs in purpose from TCP and UDP in that it is usually not used directly by user network applications. One exception is the ping tool, which sends ICMP Echo Request messages (and receives Echo Response messages) to determine whether a host is reachable and how long packets take to get to and from that host.

Contents 1 Technical Details 1.1 List of permitted control messages (incomplete list) 2 See also 3 External links

Internet control message protocol is part of the Internet protocol suite as defined in RFC 792. ICMP messages are typically generated in response to errors in IP datagrams (as specified in RFC 1122) or for diagnostic or routing purposes.

The version of ICMP for Internet Protocol version 4 is also known as ICMPv4, as it is part of IPv4. IPv6 has an equivalent protocol, ICMPv6.

ICMP messages are constructed at the IP layer, usually from a normal IP datagram that has generated an ICMP response. IP encapsulates the appropriate ICMP message with a new IP header (to get the ICMP message back to the original sending host) and transmits the resulting datagram in the usual manner.

For example, every machine (such as intermediate routers) that forwards an IP datagram has to decrement the time to live (TTL) field of the IP header by one; if the TTL reaches 0, an ICMP Time to live exceeded in transit message is sent to the source of the datagram.

Each ICMP message is encapsulated directly within a single IP datagram, and thus, like UDP, ICMP does not guarantee delivery.

Although ICMP messages are contained within standard IP datagrams, ICMP messages are usually processed as a special case, distinguished from normal IP processing, rather than processed as a normal sub-protocol of IP. In many cases, it is necessary to inspect the contents of the ICMP message and deliver the appropriate error message to the application that generated the original IP packet, the one that prompted the sending of the ICMP message.

Many commonly-used network utilities are based on ICMP messages. The traceroute command is implemented by transmitting UDP datagrams with specially set IP TTL header fields, and looking for ICMP Time to live exceeded in transit (above) and "Destination unreachable" messages generated in response. The related ping utility is implemented using the ICMP "Echo" and "Echo reply" messages.

• 0 - Echo Reply
  
• 1 - Reserved
  
• 2 - Reserved
  
• 3 - Destination Unreachable
  
• 4 - Source Quench
  
• 5 - Redirect Message
  
• 6 - Alternate Host Address
  
• 7 - Reserved
  
• 8 - Echo Request
  
• 9 - Router Advertisement
  
• 10 - Router Solicitation
  
• 11 - Time Exceeded
  
• 12 - Parameter Problem
  
• 13 - Timestamp
  
• 14 - Timestamp Reply
  
• 15 - Information Request
  
• 16 - Information Reply
  
• 17 - Address Mask Request
  
• 18 - Address Mask Reply
  
• 19 - Reserved for security
  
• 20-29 - Reserved for robustness experiment
  
• 30 - Traceroute
  
• 31 - Datagram Conversion Error
  
• 32 - Mobile Host Redirect
  
• 33 - IPv6 Where-Are-You
  
• 34 - IPv6 Here-I-Am
  
• 35 - Mobile Registration Request
  
• 36 - Mobile Registration Reply
  
• 38 - Domain Name Reply
  
• 39 - SKIP Algorithm Discovery Protocol
  
• 40 - Photuris, Security failures
  
• 41 - ICMP for experimental mobility protocols such as Seamoby [RFC4065]
  
• 42-255 - Reserved
  

(Source: IANA ICMP Parameters)

• ICMPv6
• IRDP
• Smurf attack
• TCP
• ping
• traceroute

• RFC 792, Internet Control Message Protocol
• ICMP Sequence Diagram
• RFC 1122, Requirements for Internet Hosts -- Communication Layers
• Filtering ICMP on firewalls
• IANA