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 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
@(#)inet.3 6.7 (Berkeley) 02/14/89
"#include <sys/socket.h> "#include <netinet/in.h> "#include <arpa/inet.h>"unsigned long inet_addr(cp) "char *cp;
"unsigned long inet_network(cp) "char *cp;
"char *inet_ntoa(in) "struct in_addr in;
"struct in_addr inet_makeaddr(net, lna) "int net, lna;
"unsigned long inet_lnaof(in) "struct in_addr in;
"unsigned long inet_netof(in) "struct in_addr in;
All Internet address are returned in network order (bytes ordered from left to right). All network numbers and local address parts are returned as machine format integer values.
When a three part address is specified, the last part is interpreted as a 16-bit quantity and placed in the right most two bytes of the network address. This makes the three part address format convenient for specifying Class B network addresses as \*(lq128.net.host\*(rq.
When a two part address is supplied, the last part is interpreted as a 24-bit quantity and placed in the right most three bytes of the network address. This makes the two part address format convenient for specifying Class A network addresses as \*(lqnet.host\*(rq.
When only one part is given, the value is stored directly in the network address without any byte rearrangement.
All numbers supplied as \*(lqparts\*(rq in a \*(lq.\*(rq notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal).
Inet_addr should return a struct in_addr.