Tuesday, October 20, 2009

Chapter 25.  Internet Control Message Protocol (ICMPv4)










Chapter 25. Internet Control Message Protocol (ICMPv4)


The Internet Control Message Protocol (ICMP) is a transport protocol used by Internet hosts to exchange control messages, notably error notifications and information requests. In this chapter, we will look at ICMPv4, the version used by IPv4. IPv6 uses the ICMPv6 protocol, a protocol that includes other functionalities besides the ones in ICMPv4.


Over the years, the ICMP protocol has increasingly been used as the basis for the development of monitoring and measurement applications. Unfortunately, the ICMP protocol is also often used as the basis for security attacks, such as DoS or remote fingerprint collection. For this reason, network administrators often configure routers and firewalls to filter out most ICMP message types. Sometimes they filter too much, going against the RFC recommendations. Regardless of whether messages are filtered, they are often rate limited. It follows that any application built on top of ICMP is not always reliable for measurement or monitoring purposes. However, because measurements were not in its original design goal, ICMP often does not allow monitoring applications to collect all the information they need. Instead, dedicated applications have been written for that purpose, often based on TCP or UDP.


For readers interested in the security aspects of ICMP, I recommend the paper "ICMP Usage in Scanning" from the Israeli security consultant Ofir Arkin (http://www.sys-security.com/archive/papers/ICMP_Scanning_v3.0.zip). It shows how ICMP messages can (and are) used for network scanning purposes and why most of them should be (and are) therefore filtered out by network administrators. The paper includes a detailed summary of the main RFCs on ICMP as well.


In this chapter, we'll see how Linux implements the ICMP protocol. For each ICMP message type, we will briefly see when the kernel generates it and how the kernel processes it when it is received. For more details, refer to the following RFCs:


  • RFC 792, Internet Control Message Protocol

  • RFC 950, Internet Standard Subnetting Procedure, Appendix I

  • RFC 1016, Something a Host Could Do with Source Quench

  • RFC 1191, Path MTU Discovery

  • RFC 1122, Requirements for Internet HostsCommunication Layers

  • RFC 1812, Requirements for IP Version 4 Routers

  • RFC 1256, ICMP Router Discovery Messages

  • RFC 1349, Type of Service in the Internet Protocol Suite


In particular, RFC 792 describes the layout of the headers of most ICMP types, and RFCs 1122 and 1812 tell whether hosts and routers should generate and process each ICMP type. Part of that information is included in this chapter, too.


For a detailed list of RFCs related to ICMP messages, you can also consult this URL: http://www.iana.org/assignments/icmp-parameters.












No comments: