1 | .\" Copyright (c) 1993 |
---|
2 | .\" The Regents of the University of California. All rights reserved. |
---|
3 | .\" |
---|
4 | .\" Redistribution and use in source and binary forms, with or without |
---|
5 | .\" modification, are permitted provided that the following conditions |
---|
6 | .\" are met: |
---|
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. |
---|
19 | .\" |
---|
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 |
---|
30 | .\" SUCH DAMAGE. |
---|
31 | .\" |
---|
32 | .\" @(#)iso_addr.3 8.1 (Berkeley) 6/4/93 |
---|
33 | .\" |
---|
34 | .Dd June 4, 1993 |
---|
35 | .Dt ISO_ADDR 3 |
---|
36 | .Os |
---|
37 | .Sh NAME |
---|
38 | .Nm iso_addr , |
---|
39 | .Nm iso_ntoa |
---|
40 | .Nd "elementary network address conversion routines for Open System Interconnection |
---|
41 | .Sh SYNOPSIS |
---|
42 | .Fd #include <sys/types.h> |
---|
43 | .Fd #include <netiso/iso.h> |
---|
44 | .Ft struct iso_addr * |
---|
45 | .Fn iso_addr "char *cp" |
---|
46 | .Ft char * |
---|
47 | .Fn iso_ntoa "struct iso_addr *isoa" |
---|
48 | .Sh DESCRIPTION |
---|
49 | The routine |
---|
50 | .Fn iso_addr |
---|
51 | interprets character strings representing |
---|
52 | .Tn OSI |
---|
53 | addresses, returning binary information suitable |
---|
54 | for use in system calls. |
---|
55 | The routine |
---|
56 | .Fn iso_ntoa |
---|
57 | takes |
---|
58 | .Tn OSI |
---|
59 | addresses and returns |
---|
60 | .Tn ASCII |
---|
61 | strings representing NSAPs (network service |
---|
62 | access points) in a |
---|
63 | notation inverse to that accepted by |
---|
64 | .Fn iso_addr . |
---|
65 | .Pp |
---|
66 | Unfortunately, no universal standard exists for representing |
---|
67 | .Tn OSI |
---|
68 | network addresses. |
---|
69 | .Pp |
---|
70 | The format employed by |
---|
71 | .Fn iso_addr |
---|
72 | is a sequence of hexadecimal |
---|
73 | .Dq digits |
---|
74 | (optionally separated by periods), |
---|
75 | of the form: |
---|
76 | .Bd -filled -offset indent |
---|
77 | <hex digits>.<hex digits>.<hex digits> |
---|
78 | .Ed |
---|
79 | .Pp |
---|
80 | Each pair of hexadecimal digits represents a byte |
---|
81 | with the leading digit indicating the higher-ordered bits. |
---|
82 | A period following an even number of bytes has no |
---|
83 | effect (but may be used to increase legibility). |
---|
84 | A period following an odd number of bytes has the |
---|
85 | effect of causing the byte of address being translated |
---|
86 | to have its higher order bits filled with zeros. |
---|
87 | .Sh RETURN VALUES |
---|
88 | .Fn iso_ntoa |
---|
89 | always returns a null terminated string. |
---|
90 | .Fn iso_addr |
---|
91 | always returns a pointer to a struct iso_addr. |
---|
92 | (See |
---|
93 | .Sx BUGS . ) |
---|
94 | .Sh SEE ALSO |
---|
95 | .Xr iso 4 |
---|
96 | .Sh HISTORY |
---|
97 | The |
---|
98 | .Fn iso_addr |
---|
99 | and |
---|
100 | .Fn iso_ntoa |
---|
101 | functions appeared in |
---|
102 | .Bx 4.3 Reno . |
---|
103 | .Sh BUGS |
---|
104 | The returned values |
---|
105 | reside in a static memory area. |
---|
106 | .Pp |
---|
107 | The function |
---|
108 | .Fn iso_addr |
---|
109 | should diagnose improperly formed input, and there should be an unambiguous |
---|
110 | way to recognize this. |
---|