Add a cgsix man page; From: Craig Leres <leres@ee.lbl.gov>
[unix-history] / usr / src / share / man / man4 / nsip.4
CommitLineData
5ebe7d4b
KB
1.\" Copyright (c) 1985, 1991, 1993
2.\" The Regents of the University of California. All rights reserved.
ef8cc9a4 3.\"
91cff1e1 4.\" %sccs.include.redist.man%
ef8cc9a4 5.\"
9323e918 6.\" @(#)nsip.4 8.2 (Berkeley) %G%
1324d254 7.\"
9903e566
CL
8.Dd
9.Dt NSIP 4
10.Os BSD 4.3
11.Sh NAME
12.Nm nsip
13.Nd software network interface encapsulating NS packets in IP packets
14.Sh SYNOPSIS
15.Cd options NSIP
16.Fd #include <netns/ns_if.h>
17.Sh DESCRIPTION
ef8cc9a4 18The
9903e566 19.Nm nsip
ef8cc9a4 20interface is a software mechanism which may be
9903e566
CL
21used to transmit Xerox
22.Tn NS Ns (tm)
23packets through otherwise uncooperative
ef8cc9a4 24networks.
9903e566
CL
25It functions by prepending an
26.Tn IP
27header, and resubmitting the packet
28through the
29.Tn UNIX
30.Tn IP
31machinery.
32.Pp
ef8cc9a4 33The super-user can advise the operating system of a willing partner
9903e566
CL
34by naming an
35.Tn IP
36address to be associated with an
37.Tn NS
38address.
ef8cc9a4
KS
39Presently, only specific hosts pairs are allowed, and for each host
40pair, an artificial point-to-point interface is constructed.
9903e566
CL
41At some future date,
42.Tn IP
43broadcast addresses or hosts may be paired
44with
45.Tn NS
46networks or hosts.
47.Pp
48Specifically, a socket option of
49.Dv SO_NSIP_ROUTE
50is set on a socket
51of family
52.Dv AF_NS ,
53type
54.Dv SOCK_DGRAM ,
55passing the following structure:
56.Bd -literal
ef8cc9a4
KS
57struct nsip_req {
58 struct sockaddr rq_ns; /* must be ns format destination */
59 struct sockaddr rq_ip; /* must be ip format gateway */
60 short rq_flags;
61};
9903e566
CL
62.Ed
63.Sh DIAGNOSTICS
64.Bl -diag
65.It nsip%d: can't handle af%d.
66The interface was handed
ef8cc9a4
KS
67a message with addresses formatted in an unsuitable address
68family; the packet was dropped.
9903e566
CL
69.El
70.Sh SEE ALSO
71.Xr intro 4 ,
72.Xr ns 4
73.Sh HISTORY
74The
75.Nm
76interface appeared in
77.Bx 4.3 .
78.Sh BUGS
ef8cc9a4
KS
79It is absurd to have a separate pseudo-device for each pt-to-pt
80link.
9903e566
CL
81There is no way to change the
82.Tn IP
83address for an
84.Tn NS
85host once the
9323e918 86encapsulation interface is set up.
9903e566
CL
87The request should honor flags of
88.Dv RTF_GATEWAY
89to indicate
90remote networks, and the absence of
91.Dv RTF_UP
92should be a clue
ef8cc9a4 93to remove that partner.
9903e566
CL
94This was intended to postpone the necessity of rewriting reverse
95.Tn ARP
ef8cc9a4 96for the
9903e566
CL
97.Xr en 4
98device, and to allow passing
99.Tn XNS
100packets through an
ef8cc9a4
KS
101Arpanet-Milnet gateway, to facilitate testing between some co-operating
102universities.