Commit | Line | Data |
---|---|---|
15637ed4 RG |
1 | .\" Copyright (c) 1985, 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 | .\" @(#)nsip.4 1.4 (Berkeley) 3/28/91 | |
33 | .\" | |
34 | .Dd March 28, 1991 | |
35 | .Dt NSIP 4 | |
36 | .Os BSD 4.3 | |
37 | .Sh NAME | |
38 | .Nm nsip | |
39 | .Nd software network interface encapsulating ns packets in ip packets. | |
40 | .Sh SYNOPSIS | |
41 | .Cd options NSIP | |
42 | .Fd #include <netns/ns_if.h> | |
43 | .Sh DESCRIPTION | |
44 | The | |
45 | .Nm nsip | |
46 | interface is a software mechanism which may be | |
47 | used to transmit Xerox | |
48 | .Tn NS Ns (tm) | |
49 | packets through otherwise uncooperative | |
50 | networks. | |
51 | It functions by prepending an | |
52 | .Tn IP | |
53 | header, and resubmitting the packet | |
54 | through the | |
55 | .Tn UNIX | |
56 | .Tn IP | |
57 | machinery. | |
58 | .Pp | |
59 | The super-user can advise the operating system of a willing partner | |
60 | by naming an | |
61 | .Tn IP | |
62 | address to be associated with an | |
63 | .Tn NS | |
64 | address. | |
65 | Presently, only specific hosts pairs are allowed, and for each host | |
66 | pair, an artificial point-to-point interface is constructed. | |
67 | At some future date, | |
68 | .Tn IP | |
69 | broadcast addresses or hosts may be paired | |
70 | with | |
71 | .Tn NS | |
72 | networks or hosts. | |
73 | .Pp | |
74 | Specifically, a socket option of | |
75 | .Dv SO_NSIP_ROUTE | |
76 | is set on a socket | |
77 | of family | |
78 | .Dv AF_NS , | |
79 | type | |
80 | .Dv SOCK_DGRAM , | |
81 | passing the following structure: | |
82 | .Bd -literal | |
83 | struct nsip_req { | |
84 | struct sockaddr rq_ns; /* must be ns format destination */ | |
85 | struct sockaddr rq_ip; /* must be ip format gateway */ | |
86 | short rq_flags; | |
87 | }; | |
88 | .Ed | |
89 | .Sh DIAGNOSTICS | |
90 | .Bl -diag | |
91 | .It nsip%d: can't handle af%d. | |
92 | The interface was handed | |
93 | a message with addresses formatted in an unsuitable address | |
94 | family; the packet was dropped. | |
95 | .El | |
96 | .Sh SEE ALSO | |
97 | .Xr intro 4 , | |
98 | .Xr ns 4 | |
99 | .Sh HISTORY | |
100 | The | |
101 | .Nm | |
102 | interface appeared in | |
103 | .Bx 4.3 . | |
104 | .Sh BUGS | |
105 | It is absurd to have a separate pseudo-device for each pt-to-pt | |
106 | link. | |
107 | There is no way to change the | |
108 | .Tn IP | |
109 | address for an | |
110 | .Tn NS | |
111 | host once the | |
112 | the encapsulation interface is set up. | |
113 | The request should honor flags of | |
114 | .Dv RTF_GATEWAY | |
115 | to indicate | |
116 | remote networks, and the absence of | |
117 | .Dv RTF_UP | |
118 | should be a clue | |
119 | to remove that partner. | |
120 | This was intended to postpone the necessity of rewriting reverse | |
121 | .Tn ARP | |
122 | for the | |
123 | .Xr en 4 | |
124 | device, and to allow passing | |
125 | .Tn XNS | |
126 | packets through an | |
127 | Arpanet-Milnet gateway, to facilitate testing between some co-operating | |
128 | universities. |