|
|
1.1 root 1: .\" Copyright (c) 1985 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)ns.4 1.5 (Berkeley) 6/23/90
19: .\"
20: .TH NS 4 "June 23, 1990"
21: .UC 6
22: .SH NAME
23: ns \- Xerox Network Systems(tm) protocol family
24: .SH SYNOPSIS
25: \fBoptions NS\fP
26: .br
27: \fBoptions NSIP\fP
28: .br
29: \fBpseudo-device ns\fP
30: .SH DESCRIPTION
31: .IX "ns device" "" "\fLns\fP \(em Xerox NS protocol family"
32: The NS protocol family is a collection of protocols
33: layered atop the
34: .I Internet Datagram Protocol
35: (IDP) transport layer, and using the Xerox NS address formats.
36: The NS family provides protocol support for the
37: SOCK_STREAM, SOCK_DGRAM, SOCK_SEQPACKET, and SOCK_RAW socket types; the
38: SOCK_RAW interface is a debugging tool, allowing you to trace all packets
39: entering, (or with toggling kernel variable, additionally leaving) the local
40: host.
41: .SH ADDRESSING
42: NS addresses are 12 byte quantities, consisting of a
43: 4 byte Network number, a 6 byte Host number and a 2 byte port number,
44: all stored in network standard format.
45: (on the VAX these are word and byte reversed; on the Sun they are not
46: reversed). The include file
47: .RI < netns/ns.h >
48: defines the NS address as a structure containing unions (for quicker
49: comparisons).
50: .PP
51: Sockets in the Internet protocol family use the following
52: addressing structure:
53: .nf
54:
55: struct sockaddr_ns {
56: short sns_family;
57: struct ns_addr sns_addr;
58: char sns_zero[2];
59: };
60:
61: where an ns_addr is composed as follows:
62:
63: union ns_host {
64: u_char c_host[6];
65: u_short s_host[3];
66: };
67:
68: union ns_net {
69: u_char c_net[4];
70: u_short s_net[2];
71: };
72:
73: struct ns_addr {
74: union ns_net x_net;
75: union ns_host x_host;
76: u_short x_port;
77: };
78:
79: .fi
80: Sockets may be created with an address of all zeroes to effect
81: ``wildcard'' matching on incoming messages.
82: The local port address specified in a
83: .IR bind (2)
84: call is restricted to be greater than NSPORT_RESERVED
85: (=3000, in <netns/ns.h>) unless the creating process is running
86: as the super-user, providing a space of protected port numbers.
87: .SH PROTOCOLS
88: The NS protocol family supported by the operating system
89: is comprised of
90: the Internet Datagram Protocol (IDP)
91: .IR idp (4),
92: Error Protocol (available through IDP),
93: and
94: Sequenced Packet Protocol (SPP)
95: .IR spp (4).
96: .LP
97: SPP is used to support the SOCK_STREAM and SOCK_SEQPACKET abstraction,
98: while IDP is used to support the SOCK_DGRAM abstraction.
99: The Error protocol is responded to by the kernel
100: to handle and report errors in protocol processing;
101: it is, however,
102: only accessible to user programs through heroic actions.
103: .SH SEE ALSO
104: intro(3), byteorder(3), gethostbyname(3), getnetent(3),
105: getprotoent(3), getservent(3), ns(3),
106: intro(4), spp(4), idp(4), nsip(4)
107: .br
108: Internet Transport Protocols, Xerox Corporation document XSIS-028112
109: .br
110: An Advanced 4.3BSD Interprocess Communication Tutorial
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.