1.\" $NetBSD: icmp.4,v 1.3 1994/11/30 16:22:14 jtc Exp $ 2.\" 3.\" Copyright (c) 1986, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" @(#)icmp.4 8.1 (Berkeley) 6/5/93 35.\" 36.Dd June 5, 1993 37.Dt ICMP 4 38.Os BSD 4.3 39.Sh NAME 40.Nm icmp 41.Nd Internet Control Message Protocol 42.Sh SYNOPSIS 43.Fd #include <sys/socket.h> 44.Fd #include <netinet/in.h> 45.Ft int 46.Fn socket AF_INET SOCK_RAW proto 47.Sh DESCRIPTION 48.Tn ICMP 49is the error and control message protocol used 50by 51.Tn IP 52and the Internet protocol family. It may be accessed 53through a 54.Dq raw socket 55for network monitoring 56and diagnostic functions. 57The 58.Fa proto 59parameter to the socket call to create an 60.Tn ICMP 61socket 62is obtained from 63.Xr getprotobyname 3 . 64.Tn ICMP 65sockets are connectionless, 66and are normally used with the 67.Xr sendto 68and 69.Xr recvfrom 70calls, though the 71.Xr connect 2 72call may also be used to fix the destination for future 73packets (in which case the 74.Xr read 2 75or 76.Xr recv 2 77and 78.Xr write 2 79or 80.Xr send 2 81system calls may be used). 82.Pp 83Outgoing packets automatically have an 84.Tn IP 85header prepended to 86them (based on the destination address). 87Incoming packets are received with the 88.Tn IP 89header and options intact. 90.Sh DIAGNOSTICS 91A socket operation may fail with one of the following errors returned: 92.Bl -tag -width [EADDRNOTAVAIL] 93.It Bq Er EISCONN 94when trying to establish a connection on a socket which 95already has one, or when trying to send a datagram with the destination 96address specified and the socket is already connected; 97.It Bq Er ENOTCONN 98when trying to send a datagram, but 99no destination address is specified, and the socket hasn't been 100connected; 101.It Bq Er ENOBUFS 102when the system runs out of memory for 103an internal data structure; 104.It Bq Er EADDRNOTAVAIL 105when an attempt is made to create a 106socket with a network address for which no network interface 107exists. 108.El 109.Sh SEE ALSO 110.Xr send 2 , 111.Xr recv 2 , 112.Xr intro 4 , 113.Xr inet 4 , 114.Xr ip 4 115.Sh HISTORY 116The 117.Nm 118protocol appeared in 119.Bx 4.3 . 120