Copyright (c) 1986 Regents of the University of California.
All rights reserved.
Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
@(#)icmp.4 6.3 (Berkeley) 07/09/88
All rights reserved.
Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
@(#)icmp.4 6.3 (Berkeley) 07/09/88
ICMP 4P ""
C 6 NAME
icmp - Internet Control Message Protocol
SYNOPSIS
#include <sys/socket.h> s = socket(AF_INET, SOCK_RAW, proto);
DESCRIPTION
ICMP is the error and control message protocol used
by IP and the Internet protocol family. It may be accessed
through a \*(lqraw socket\*(rq for network monitoring
and diagnostic functions.
The
proto parameter to the socket call to create an ICMP socket
is obtained from
getprotobyname (3N). ICMP sockets are connectionless,
and are normally used with the
sendto and
recvfrom calls, though the
connect (2) call may also be used to fix the destination for future
packets (in which case the
read (2) or
recv (2) and
write (2) or
send (2) system calls may be used).
Outgoing packets automatically have an IP header prepended to them (based on the destination address). Incoming packets are received with the IP header and options intact.
DIAGNOSTICS
A socket operation may fail with one of the following errors returned:
15 [EISCONN] when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destination address specified and the socket is already connected;
15 [ENOTCONN] when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;
15 [ENOBUFS] when the system runs out of memory for an internal data structure;
15 [EADDRNOTAVAIL] when an attempt is made to create a socket with a network address for which no network interface exists.
SEE ALSO
send(2), recv(2), intro(4N), inet(4F), ip(4P)