1.\" Copyright (c) 1986, 1991 The Regents of the University of California. 2.\" 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.\" @(#)ns.3 6.5 (Berkeley) 4/19/91 33.\" 34.Dd April 19, 1991 35.Dt NS 3 36.Os BSD 4.3 37.Sh NAME 38.Nm ns_addr , 39.Nm ns_ntoa 40.Nd Xerox 41.Tn NS Ns (tm) 42address conversion routines 43.Sh SYNOPSIS 44.Fd #include <sys/types.h> 45.Fd #include <netns/ns.h> 46.Ft struct ns_addr 47.Fn ns_addr "char *cp" 48.Ft char * 49.Fn ns_ntoa "struct ns_addr ns" 50.Sh DESCRIPTION 51The routine 52.Fn ns_addr 53interprets character strings representing 54.Tn XNS 55addresses, returning binary information suitable 56for use in system calls. 57The routine 58.Fn ns_ntoa 59takes 60.Tn XNS 61addresses and returns 62.Tn ASCII 63strings representing the address in a 64notation in common use in the Xerox Development Environment: 65.Bd -filled -offset indent 66<network number>.<host number>.<port number> 67.Ed 68.Pp 69Trailing zero fields are suppressed, and each number is printed in hexadecimal, 70in a format suitable for input to 71.Fn ns_addr . 72Any fields lacking super-decimal digits will have a 73trailing 74.Ql H 75appended. 76.Pp 77Unfortunately, no universal standard exists for representing 78.Tn XNS 79addresses. 80An effort has been made to insure that 81.Fn ns_addr 82be compatible with most formats in common use. 83It will first separate an address into 1 to 3 fields using a single delimiter 84chosen from 85period 86.Ql \&. , 87colon 88.Ql \&: 89or pound-sign 90.Ql \&# . 91Each field is then examined for byte separators (colon or period). 92If there are byte separators, each subfield separated is taken to be 93a small hexadecimal number, and the entirety is taken as a network-byte-ordered 94quantity to be zero extended in the high-network-order bytes. 95Next, the field is inspected for hyphens, in which case 96the field is assumed to be a number in decimal notation 97with hyphens separating the millenia. 98Next, the field is assumed to be a number: 99It is interpreted 100as hexadecimal if there is a leading 101.Ql 0x 102(as in C), 103a trailing 104.Ql H 105(as in Mesa), or there are any super-decimal digits present. 106It is interpreted as octal is there is a leading 107.Ql 0 108and there are no super-octal digits. 109Otherwise, it is converted as a decimal number. 110.Sh RETURN VALUES 111None. (See 112.Sx BUGS . ) 113.Sh SEE ALSO 114.Xr hosts 5 , 115.Xr networks 5 , 116.Sh HISTORY 117The 118.Fn ns_addr 119and 120.Fn ns_toa 121functions appeared in 122.Bx 4.3 . 123.Sh BUGS 124The string returned by 125.Fn ns_ntoa 126resides in a static memory area. 127The function 128.Fn ns_addr 129should diagnose improperly formed input, and there should be an unambiguous 130way to recognize this. 131