Deleted Added
full compact
natmip.4 (116493) natmip.4 (116735)
1.\" $FreeBSD: head/share/man/man4/natmip.4 116493 2003-06-17 16:15:47Z harti $
1.\" $FreeBSD: head/share/man/man4/natmip.4 116735 2003-06-23 14:46:12Z harti $
2.\"
3.Dd June 13, 2003
4.Dt NATMIP 4
5.Os
6.Sh NAME
7.Nm natmip
8.Nd IP over ATM PVCs
9.Sh SYNOPSIS
10.Cd "device atm"
11.Cd "options NATM"
12.Sh DESCRIPTION
13The NATM protocol stack includes support for IP over ATM. Without any
14additional signalling stacks or other modules it is possible to build
15a CLIP (classical IP over ATM) network based on PVCs.
16.Pp
17An ATM network card (en0 in this example) is configured for IP by something
18like:
19.Pp
20.Dl # ifconfig en0 128.252.200.1 netmask 0xffffff00 up
21.Pp
22A PVC is added with the
23.Dq route
24utility:
25.Pp
26.Dl # route add -iface <remote IP address> -link en0:z.0.x.y
27.Pp
28where x and y are the hexadecimal byte encoding of the VCI to use,
29and z is the byte encoding of the following flags:
30.Pp
31.Bl -tag -width "0x02" -offset indent -compact
32.It 0x01
33use AAL5.
34.It 0x02
35if using AAL5, use an LLC/SNAP header.
36.El
37.Pp
38Thus, parameter 3 means AAL5 and LLC/SNAP encapsulation (this is the required
39setting for interworking with other CLIP clients).
40Note that BPF works only with LLC/SNAP encapsulation.
41.Sh EXAMPLES
42Suppose you have 3 hosts 128.252.200.1, 128.252.200.2 and
43128.252.200.3 connected by ATM through PVCs:
44.Pp
45.Bl -item -offset indent -compact
46.It
47between 128.252.200.1 and 128.252.200.2: 0xc9
48.It
49between 128.252.200.1 and 128.252.200.3: 0xca
50.It
51between 128.252.200.2 and 128.252.200.3: 0xcb
52.El
53.Pp
54To enable the links use the following commands:
55.Pp
56on host 128.252.200.1:
57.Bd -literal -offset indent -compact
58# ifconfig en0 128.252.200.1 netmask 0xffffff00 up
59# route add -iface 128.252.200.2 -link en0:3.0.0.c9
60# route add -iface 128.252.200.3 -link en0:3.0.0.ca
61.Ed
62.Pp
63on host 128.252.200.2:
64.Bd -literal -offset indent -compact
65# ifconfig en0 128.252.200.2 netmask 0xffffff00 up
66# route add -iface 128.252.200.1 -link en0:3.0.0.c9
67# route add -iface 128.252.200.3 -link en0:3.0.0.cb
68.Ed
69.Pp
70on host 128.252.200.3:
71.Bd -literal -offset indent -compact
72# ifconfig en0 128.252.200.3 netmask 0xffffff00 up
73# route add -iface 128.252.200.1 -link en0:3.0.0.ca
74# route add -iface 128.252.200.2 -link en0:3.0.0.cb
75.Ed
76.Pp
77This can also be done in
78.Xr rc.conf 5 :
79.Pp
80on host 128.252.200.1:
81.Bd -literal -offset indent -compact
82network_interfaces="lo0 en0"
83ifconfig_en0="inet 128.252.200.1 netmask 255.255.255.0"
84static_routes="host2 host3"
85route_host2="-iface 128.252.200.2 -link en0:3.0.0.c9"
86route_host3="-iface 128.252.200.3 -link en0:3.0.0.ca"
87.Ed
88.Pp
89on host 128.252.200.2:
90.Bd -literal -offset indent -compact
91network_interfaces="lo0 en0"
92ifconfig_en0="inet 128.252.200.2 netmask 255.255.255.0"
93static_routes="host1 host3"
94route_host1="-iface 128.252.200.1 -link en0:3.0.0.c9"
95route_host3="-iface 128.252.200.3 -link en0:3.0.0.cb"
96.Ed
97.Pp
98on host 128.252.200.3:
99.Bd -literal -offset indent -compact
100network_interfaces="lo0 en0"
101ifconfig_en0="inet 128.252.200.3 netmask 255.255.255.0"
102static_routes="host1 host2"
103route_host1="-iface 128.252.200.1 -link en0:3.0.0.ca"
104route_host2="-iface 128.252.200.2 -link en0:3.0.0.cb"
105.Ed
106.Sh SEE ALSO
107.Xr en 4 ,
108.Xr hatm 4 ,
2.\"
3.Dd June 13, 2003
4.Dt NATMIP 4
5.Os
6.Sh NAME
7.Nm natmip
8.Nd IP over ATM PVCs
9.Sh SYNOPSIS
10.Cd "device atm"
11.Cd "options NATM"
12.Sh DESCRIPTION
13The NATM protocol stack includes support for IP over ATM. Without any
14additional signalling stacks or other modules it is possible to build
15a CLIP (classical IP over ATM) network based on PVCs.
16.Pp
17An ATM network card (en0 in this example) is configured for IP by something
18like:
19.Pp
20.Dl # ifconfig en0 128.252.200.1 netmask 0xffffff00 up
21.Pp
22A PVC is added with the
23.Dq route
24utility:
25.Pp
26.Dl # route add -iface <remote IP address> -link en0:z.0.x.y
27.Pp
28where x and y are the hexadecimal byte encoding of the VCI to use,
29and z is the byte encoding of the following flags:
30.Pp
31.Bl -tag -width "0x02" -offset indent -compact
32.It 0x01
33use AAL5.
34.It 0x02
35if using AAL5, use an LLC/SNAP header.
36.El
37.Pp
38Thus, parameter 3 means AAL5 and LLC/SNAP encapsulation (this is the required
39setting for interworking with other CLIP clients).
40Note that BPF works only with LLC/SNAP encapsulation.
41.Sh EXAMPLES
42Suppose you have 3 hosts 128.252.200.1, 128.252.200.2 and
43128.252.200.3 connected by ATM through PVCs:
44.Pp
45.Bl -item -offset indent -compact
46.It
47between 128.252.200.1 and 128.252.200.2: 0xc9
48.It
49between 128.252.200.1 and 128.252.200.3: 0xca
50.It
51between 128.252.200.2 and 128.252.200.3: 0xcb
52.El
53.Pp
54To enable the links use the following commands:
55.Pp
56on host 128.252.200.1:
57.Bd -literal -offset indent -compact
58# ifconfig en0 128.252.200.1 netmask 0xffffff00 up
59# route add -iface 128.252.200.2 -link en0:3.0.0.c9
60# route add -iface 128.252.200.3 -link en0:3.0.0.ca
61.Ed
62.Pp
63on host 128.252.200.2:
64.Bd -literal -offset indent -compact
65# ifconfig en0 128.252.200.2 netmask 0xffffff00 up
66# route add -iface 128.252.200.1 -link en0:3.0.0.c9
67# route add -iface 128.252.200.3 -link en0:3.0.0.cb
68.Ed
69.Pp
70on host 128.252.200.3:
71.Bd -literal -offset indent -compact
72# ifconfig en0 128.252.200.3 netmask 0xffffff00 up
73# route add -iface 128.252.200.1 -link en0:3.0.0.ca
74# route add -iface 128.252.200.2 -link en0:3.0.0.cb
75.Ed
76.Pp
77This can also be done in
78.Xr rc.conf 5 :
79.Pp
80on host 128.252.200.1:
81.Bd -literal -offset indent -compact
82network_interfaces="lo0 en0"
83ifconfig_en0="inet 128.252.200.1 netmask 255.255.255.0"
84static_routes="host2 host3"
85route_host2="-iface 128.252.200.2 -link en0:3.0.0.c9"
86route_host3="-iface 128.252.200.3 -link en0:3.0.0.ca"
87.Ed
88.Pp
89on host 128.252.200.2:
90.Bd -literal -offset indent -compact
91network_interfaces="lo0 en0"
92ifconfig_en0="inet 128.252.200.2 netmask 255.255.255.0"
93static_routes="host1 host3"
94route_host1="-iface 128.252.200.1 -link en0:3.0.0.c9"
95route_host3="-iface 128.252.200.3 -link en0:3.0.0.cb"
96.Ed
97.Pp
98on host 128.252.200.3:
99.Bd -literal -offset indent -compact
100network_interfaces="lo0 en0"
101ifconfig_en0="inet 128.252.200.3 netmask 255.255.255.0"
102static_routes="host1 host2"
103route_host1="-iface 128.252.200.1 -link en0:3.0.0.ca"
104route_host2="-iface 128.252.200.2 -link en0:3.0.0.cb"
105.Ed
106.Sh SEE ALSO
107.Xr en 4 ,
108.Xr hatm 4 ,
109.Xr fatm 4 ,
109.Xr natm 4
110.Sh AUTHORS
111.An Chuck Cranor
112of Washington University implemented the NATM protocol layer
113along with the EN ATM driver in 1996 for
114.Nx .
110.Xr natm 4
111.Sh AUTHORS
112.An Chuck Cranor
113of Washington University implemented the NATM protocol layer
114along with the EN ATM driver in 1996 for
115.Nx .