xref: /freebsd/sbin/nos-tun/nos-tun.8 (revision e66dbdb6c09a044f96f8fd8edb8e35ac46092b8c)
1e66dbdb6SPoul-Henning Kamp.\"
2e66dbdb6SPoul-Henning Kamp.\" ----------------------------------------------------------------------------
3e66dbdb6SPoul-Henning Kamp.\" "THE BEER-WARE LICENSE" (Revision 42):
4e66dbdb6SPoul-Henning Kamp.\" <phk@FreeBSD.org> wrote this file.  As long as you retain this notice you
5e66dbdb6SPoul-Henning Kamp.\" can do whatever you want with this stuff. If we meet some day, and you think
6e66dbdb6SPoul-Henning Kamp.\" this stuff is worth it, you can buy me a beer in return.   Poul-Henning Kamp
7e66dbdb6SPoul-Henning Kamp.\" ----------------------------------------------------------------------------
8e66dbdb6SPoul-Henning Kamp.\"
9e66dbdb6SPoul-Henning Kamp.\" $Id$
10e66dbdb6SPoul-Henning Kamp.\"
11e66dbdb6SPoul-Henning Kamp.Dd April 11, 1998
12e66dbdb6SPoul-Henning Kamp.Dt NOS-TUN 8
13e66dbdb6SPoul-Henning Kamp.Os FreeBSD 3.0
14e66dbdb6SPoul-Henning Kamp.Sh NAME
15e66dbdb6SPoul-Henning Kamp.Nm nos-tun
16e66dbdb6SPoul-Henning Kamp.Nd Implement ``nos'' or ``ka9q'' style IP over IP tunnel
17e66dbdb6SPoul-Henning Kamp.Sh SYNOPSIS
18e66dbdb6SPoul-Henning Kamp.Nm nos-tun
19e66dbdb6SPoul-Henning Kamp.Fl t
20e66dbdb6SPoul-Henning Kamp.Ar tunnel
21e66dbdb6SPoul-Henning Kamp.Fl s
22e66dbdb6SPoul-Henning Kamp.Ar source
23e66dbdb6SPoul-Henning Kamp.Fl d
24e66dbdb6SPoul-Henning Kamp.Ar destination
25e66dbdb6SPoul-Henning Kamp.Ar target
26e66dbdb6SPoul-Henning Kamp.Sh DESCRIPTION
27e66dbdb6SPoul-Henning Kamp.Nm
28e66dbdb6SPoul-Henning Kampis used to establish an
29e66dbdb6SPoul-Henning Kamp.Em nos
30e66dbdb6SPoul-Henning Kampstyle tunnel, (also known as
31e66dbdb6SPoul-Henning Kamp.Em ka9q
32e66dbdb6SPoul-Henning Kampor
33e66dbdb6SPoul-Henning Kamp.Em IP-IP
34e66dbdb6SPoul-Henning Kamptunnel) using a
35e66dbdb6SPoul-Henning Kamp.Xr tun 4
36e66dbdb6SPoul-Henning Kampkernel interface.
37e66dbdb6SPoul-Henning Kamp.Pp
38e66dbdb6SPoul-Henning Kamp.Ar tunnel
39e66dbdb6SPoul-Henning Kampis the name of the tunnel device
40e66dbdb6SPoul-Henning Kamp.Dq /dev/tun0
41e66dbdb6SPoul-Henning Kampfor example.
42e66dbdb6SPoul-Henning Kamp.Pp
43e66dbdb6SPoul-Henning Kamp.Ar source
44e66dbdb6SPoul-Henning Kampand
45e66dbdb6SPoul-Henning Kamp.Ar destination
46e66dbdb6SPoul-Henning Kampare the addresses used on the tunnel device.
47e66dbdb6SPoul-Henning KampIf you configure the tunnel against a cisco router, use a netmask of
48e66dbdb6SPoul-Henning Kamp.Dq 255.255.255.252
49e66dbdb6SPoul-Henning Kampon the cisco.  This is because the tunnel is a point-to-point interface
50e66dbdb6SPoul-Henning Kampin the FreeBSD end, a concept cisco doesn't really implement.
51e66dbdb6SPoul-Henning Kamp.Pp
52e66dbdb6SPoul-Henning Kamp.Ar target
53e66dbdb6SPoul-Henning Kampis the address of the remote tunnel device, this must match the source
54e66dbdb6SPoul-Henning Kampaddress set on the remote end.
55e66dbdb6SPoul-Henning Kamp.Sh EXAMPLES
56e66dbdb6SPoul-Henning KampThis end, a FreeBSD box on address 192.168.59.34:
57e66dbdb6SPoul-Henning Kamp.Bd -literal -offset indent 4m
58e66dbdb6SPoul-Henning Kampnos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
59e66dbdb6SPoul-Henning Kamp.Ed
60e66dbdb6SPoul-Henning Kamp.Pp
61e66dbdb6SPoul-Henning KampRemote cisco on address 192.168.56.45:
62e66dbdb6SPoul-Henning Kamp.Bd -literal -offset indent 4m
63e66dbdb6SPoul-Henning Kampinterface tunnel 0
64e66dbdb6SPoul-Henning Kampip address 192.168.61.2 255.255.255.252
65e66dbdb6SPoul-Henning Kamptunnel mode nos
66e66dbdb6SPoul-Henning Kamptunnel destination 192.168.59.34
67e66dbdb6SPoul-Henning Kamptunnel source 192.168.56.45
68e66dbdb6SPoul-Henning Kamp.Ed
69e66dbdb6SPoul-Henning Kamp.Sh BUGS
70e66dbdb6SPoul-Henning KampWe don't allow for setting our source address for multihomed machines.
71e66dbdb6SPoul-Henning Kamp.Sh AUTHOR
72e66dbdb6SPoul-Henning KampNickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program,
73e66dbdb6SPoul-Henning KampPoul-Henning Kamp <phk@FreeBSD.org> wrote the man-page.
74