1994-05-24 09:57:34 +00:00
|
|
|
/*
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* ++Copyright++ 1983, 1993
|
|
|
|
* -
|
1994-05-24 09:57:34 +00:00
|
|
|
* Copyright (c) 1983, 1993
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* The Regents of the University of California. All rights reserved.
|
|
|
|
*
|
1994-05-24 09:57:34 +00:00
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
2010-02-16 19:46:46 +00:00
|
|
|
* 3. Neither the name of the University nor the names of its contributors
|
1994-05-24 09:57:34 +00:00
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
* without specific prior written permission.
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
*
|
1994-05-24 09:57:34 +00:00
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
1996-12-30 13:10:35 +00:00
|
|
|
* -
|
|
|
|
* Portions Copyright (c) 1993 by Digital Equipment Corporation.
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
*
|
1996-12-30 13:10:35 +00:00
|
|
|
* Permission to use, copy, modify, and distribute this software for any
|
|
|
|
* purpose with or without fee is hereby granted, provided that the above
|
|
|
|
* copyright notice and this permission notice appear in all copies, and that
|
|
|
|
* the name of Digital Equipment Corporation not be used in advertising or
|
|
|
|
* publicity pertaining to distribution of the document or software without
|
|
|
|
* specific, written prior permission.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS" AND DIGITAL EQUIPMENT CORP. DISCLAIMS ALL
|
|
|
|
* WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES
|
|
|
|
* OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL DIGITAL EQUIPMENT
|
|
|
|
* CORPORATION BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
|
|
|
|
* PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
|
|
|
|
* ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
|
|
|
|
* SOFTWARE.
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* -
|
|
|
|
* --Copyright--
|
|
|
|
*/
|
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
1994-05-24 09:57:34 +00:00
|
|
|
* @(#)inet.h 8.1 (Berkeley) 6/2/93
|
2014-08-05 23:16:31 +00:00
|
|
|
* $Id: inet.h,v 1.3 2005/04/27 04:56:16 sra Exp $
|
1999-08-27 23:45:13 +00:00
|
|
|
* $FreeBSD$
|
1994-05-24 09:57:34 +00:00
|
|
|
*/
|
|
|
|
|
1994-08-21 04:05:05 +00:00
|
|
|
#ifndef _ARPA_INET_H_
|
|
|
|
#define _ARPA_INET_H_
|
1994-05-24 09:57:34 +00:00
|
|
|
|
2010-07-06 03:48:46 +00:00
|
|
|
/* External definitions for functions in inet(3). */
|
1994-05-24 09:57:34 +00:00
|
|
|
|
|
|
|
#include <sys/cdefs.h>
|
2002-08-21 16:20:02 +00:00
|
|
|
#include <sys/_types.h>
|
1994-05-24 09:57:34 +00:00
|
|
|
|
2002-02-18 20:35:27 +00:00
|
|
|
/* Required for byteorder(3) functions. */
|
|
|
|
#include <machine/endian.h>
|
|
|
|
|
2002-03-10 06:42:27 +00:00
|
|
|
#define INET_ADDRSTRLEN 16
|
|
|
|
#define INET6_ADDRSTRLEN 46
|
|
|
|
|
2002-04-01 08:12:25 +00:00
|
|
|
#ifndef _UINT16_T_DECLARED
|
|
|
|
typedef __uint16_t uint16_t;
|
|
|
|
#define _UINT16_T_DECLARED
|
2001-12-01 03:43:01 +00:00
|
|
|
#endif
|
|
|
|
|
2002-04-01 08:12:25 +00:00
|
|
|
#ifndef _UINT32_T_DECLARED
|
|
|
|
typedef __uint32_t uint32_t;
|
|
|
|
#define _UINT32_T_DECLARED
|
|
|
|
#endif
|
|
|
|
|
2002-08-16 16:34:26 +00:00
|
|
|
#ifndef _IN_ADDR_T_DECLARED
|
2002-04-01 08:12:25 +00:00
|
|
|
typedef uint32_t in_addr_t;
|
|
|
|
#define _IN_ADDR_T_DECLARED
|
|
|
|
#endif
|
|
|
|
|
2002-08-16 16:34:26 +00:00
|
|
|
#ifndef _IN_PORT_T_DECLARED
|
2002-04-01 08:12:25 +00:00
|
|
|
typedef uint16_t in_port_t;
|
|
|
|
#define _IN_PORT_T_DECLARED
|
2001-12-01 03:43:01 +00:00
|
|
|
#endif
|
|
|
|
|
2002-08-16 16:34:26 +00:00
|
|
|
#if __BSD_VISIBLE
|
2002-08-21 16:20:02 +00:00
|
|
|
#ifndef _SIZE_T_DECLARED
|
|
|
|
typedef __size_t size_t;
|
|
|
|
#define _SIZE_T_DECLARED
|
2002-08-16 16:34:26 +00:00
|
|
|
#endif
|
2001-12-01 03:43:01 +00:00
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
2002-03-10 06:42:27 +00:00
|
|
|
* XXX socklen_t is used by a POSIX.1-2001 interface, but not required by
|
|
|
|
* POSIX.1-2001.
|
2001-12-01 03:43:01 +00:00
|
|
|
*/
|
2002-08-21 16:20:02 +00:00
|
|
|
#ifndef _SOCKLEN_T_DECLARED
|
|
|
|
typedef __socklen_t socklen_t;
|
|
|
|
#define _SOCKLEN_T_DECLARED
|
2001-12-01 03:43:01 +00:00
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifndef _STRUCT_IN_ADDR_DECLARED
|
|
|
|
struct in_addr {
|
|
|
|
in_addr_t s_addr;
|
|
|
|
};
|
|
|
|
#define _STRUCT_IN_ADDR_DECLARED
|
|
|
|
#endif
|
1996-06-13 20:45:05 +00:00
|
|
|
|
1998-06-11 08:55:17 +00:00
|
|
|
/* XXX all new diversions!! argh!! */
|
2002-04-10 10:51:53 +00:00
|
|
|
#if __BSD_VISIBLE
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define inet_addr __inet_addr
|
|
|
|
#define inet_aton __inet_aton
|
|
|
|
#define inet_lnaof __inet_lnaof
|
|
|
|
#define inet_makeaddr __inet_makeaddr
|
|
|
|
#define inet_neta __inet_neta
|
|
|
|
#define inet_netof __inet_netof
|
|
|
|
#define inet_network __inet_network
|
|
|
|
#define inet_net_ntop __inet_net_ntop
|
|
|
|
#define inet_net_pton __inet_net_pton
|
|
|
|
#define inet_cidr_ntop __inet_cidr_ntop
|
|
|
|
#define inet_cidr_pton __inet_cidr_pton
|
|
|
|
#define inet_ntoa __inet_ntoa
|
2007-06-11 07:21:21 +00:00
|
|
|
#define inet_ntoa_r __inet_ntoa_r
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define inet_pton __inet_pton
|
|
|
|
#define inet_ntop __inet_ntop
|
|
|
|
#define inet_nsap_addr __inet_nsap_addr
|
|
|
|
#define inet_nsap_ntoa __inet_nsap_ntoa
|
2002-04-10 10:51:53 +00:00
|
|
|
#endif /* __BSD_VISIBLE */
|
1998-06-11 08:55:17 +00:00
|
|
|
|
2002-03-09 21:02:16 +00:00
|
|
|
__BEGIN_DECLS
|
|
|
|
#ifndef _BYTEORDER_PROTOTYPED
|
|
|
|
#define _BYTEORDER_PROTOTYPED
|
2002-04-01 08:12:25 +00:00
|
|
|
uint32_t htonl(uint32_t);
|
|
|
|
uint16_t htons(uint16_t);
|
|
|
|
uint32_t ntohl(uint32_t);
|
|
|
|
uint16_t ntohs(uint16_t);
|
2002-02-18 20:35:27 +00:00
|
|
|
#endif
|
|
|
|
|
2002-03-23 17:24:55 +00:00
|
|
|
in_addr_t inet_addr(const char *);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
/*const*/ char *inet_ntoa(struct in_addr);
|
2002-08-16 16:34:26 +00:00
|
|
|
const char *inet_ntop(int, const void * __restrict, char * __restrict,
|
|
|
|
socklen_t);
|
|
|
|
int inet_pton(int, const char * __restrict, void * __restrict);
|
2001-12-01 03:43:01 +00:00
|
|
|
|
2002-04-10 10:51:53 +00:00
|
|
|
#if __BSD_VISIBLE
|
2002-03-23 17:24:55 +00:00
|
|
|
int inet_aton(const char *, struct in_addr *);
|
|
|
|
in_addr_t inet_lnaof(struct in_addr);
|
|
|
|
struct in_addr inet_makeaddr(in_addr_t, in_addr_t);
|
|
|
|
char * inet_neta(in_addr_t, char *, size_t);
|
|
|
|
in_addr_t inet_netof(struct in_addr);
|
|
|
|
in_addr_t inet_network(const char *);
|
|
|
|
char *inet_net_ntop(int, const void *, int, char *, size_t);
|
|
|
|
int inet_net_pton(int, const char *, void *, size_t);
|
2009-03-14 19:00:16 +00:00
|
|
|
char *inet_ntoa_r(struct in_addr, char *buf, socklen_t size);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
char *inet_cidr_ntop(int, const void *, int, char *, size_t);
|
|
|
|
int inet_cidr_pton(int, const char *, void *, int *);
|
2002-03-23 17:24:55 +00:00
|
|
|
unsigned inet_nsap_addr(const char *, unsigned char *, int);
|
|
|
|
char *inet_nsap_ntoa(int, const unsigned char *, char *);
|
2002-04-10 10:51:53 +00:00
|
|
|
#endif /* __BSD_VISIBLE */
|
1994-05-24 09:57:34 +00:00
|
|
|
__END_DECLS
|
|
|
|
|
2002-03-09 21:02:16 +00:00
|
|
|
#ifndef _BYTEORDER_FUNC_DEFINED
|
|
|
|
#define _BYTEORDER_FUNC_DEFINED
|
|
|
|
#define htonl(x) __htonl(x)
|
|
|
|
#define htons(x) __htons(x)
|
|
|
|
#define ntohl(x) __ntohl(x)
|
|
|
|
#define ntohs(x) __ntohs(x)
|
|
|
|
#endif
|
|
|
|
|
2001-12-01 03:43:01 +00:00
|
|
|
#endif /* !_ARPA_INET_H_ */
|
2007-06-03 17:20:27 +00:00
|
|
|
|
|
|
|
/*! \file */
|