icmp(4) [netbsd man page]

ICMP(4) 						   BSD Kernel Interfaces Manual 						   ICMP(4)

NAME

     icmp -- Internet Control Message Protocol

SYNOPSIS

     #include <sys/socket.h>
     #include <netinet/in.h>

     int
     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 ``raw socket'' for
     network monitoring and diagnostic functions.  The proto parameter to the socket call to create an ICMP socket is obtained from
     getprotobyname(3).  ICMP sockets are connectionless, and are normally used with the sendto(2) and recvfrom(2) 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:

     [EISCONN]	      when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina-
		      tion address specified and the socket is already connected;

     [ENOTCONN]       when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;

     [ENOBUFS]	      when the system runs out of memory for an internal data structure;

     [EADDRNOTAVAIL]  when an attempt is made to create a socket with a network address for which no network interface exists.

SEE ALSO

     recv(2), send(2), inet(4), intro(4), ip(4)

     Internet Control Message Protocol, RFC, 792, September 1981.

     Requirements for Internet Hosts -- Communication Layers, RFC, 1122, October 1989.

HISTORY

     The icmp protocol appeared in 4.3BSD.

BSD
								   June 5, 1993 							       BSD

UDP(4)							   BSD Kernel Interfaces Manual 						    UDP(4)

NAME

     udp -- Internet User Datagram Protocol

SYNOPSIS

     #include <sys/socket.h>
     #include <netinet/in.h>

     int
     socket(AF_INET, SOCK_DGRAM, 0);

DESCRIPTION

     UDP is a simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family.  UDP
     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 recv(2) or read(2) and send(2) or write(2) system calls may be used).

     UDP address formats are identical to those used by TCP.  In particular UDP provides a port identifier in addition to the normal Internet
     address format.  Note that the UDP port space is separate from the TCP port space (i.e. a UDP port may not be ``connected'' to a TCP port).
     In addition broadcast packets may be sent (assuming the underlying network supports this) by using a reserved ``broadcast address''; this
     address is network interface dependent.

     Options at the IP transport level may be used with UDP; see ip(4).

DIAGNOSTICS

     A socket operation may fail with one of the following errors returned:

     [EISCONN]	      when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina-
		      tion address specified and the socket is already connected;

     [ENOTCONN]       when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;

     [ENOBUFS]	      when the system runs out of memory for an internal data structure;

     [EADDRINUSE]     when an attempt is made to create a socket with a port which has already been allocated;

     [EADDRNOTAVAIL]  when an attempt is made to create a socket with a network address for which no network interface exists.

SEE ALSO

     getsockopt(2), recv(2), send(2), socket(2), intro(4), inet(4), ip(4)

HISTORY

     The udp protocol appeared in 4.2BSD.

4.2 Berkeley Distribution					   June 5, 1993 					 4.2 Berkeley Distribution