1 .\" Copyright (c) 1986, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
40 .Nd IPX address conversion routines
44 .Fd #include <sys/types.h>
45 .Fd #include <netipx/ipx.h>
47 .Fn ipx_addr "const char *cp"
49 .Fn ipx_ntoa "struct ipx_addr ipx"
53 interprets character strings representing
55 addresses, returning binary information suitable
56 for use in system calls.
63 strings representing the address in a
64 notation in common use:
65 .Bd -ragged -offset indent
66 <network number>.<host number>.<port number>
69 Trailing zero fields are suppressed, and each number is printed in hexadecimal,
70 in a format suitable for input to
72 Any fields lacking super-decimal digits will have a
77 An effort has been made to insure that
79 be compatible with most formats in common use.
80 It will first separate an address into 1 to 3 fields using a single delimiter
88 Each field is then examined for byte separators (colon or period).
89 If there are byte separators, each subfield separated is taken to be
90 a small hexadecimal number, and the entirety is taken as a network-byte-ordered
91 quantity to be zero extended in the high-network-order bytes.
92 Next, the field is inspected for hyphens, in which case
93 the field is assumed to be a number in decimal notation
94 with hyphens separating the millenia.
95 Next, the field is assumed to be a number:
97 as hexadecimal if there is a leading
102 (as in Mesa), or there are any super-decimal digits present.
103 It is interpreted as octal is there is a leading
105 and there are no super-octal digits.
106 Otherwise, it is converted as a decimal number.
119 functions appeared in
122 The string returned by
124 resides in a static memory area.
127 should diagnose improperly formed input, and there should be an unambiguous
128 way to recognize this.