--- nos-tun.8 Tue Jul 27 13:48:37 1999 +++ nos-tun.8 Tue Jul 27 13:50:58 1999 @@ -24,6 +24,10 @@ .Ar destination .Fl p .Ar protocol_number +.Fl r +.Ar retry_count +.Fl w +.Ar retry_delay .Ar target .Sh DESCRIPTION .Nm Nos-tun @@ -46,20 +50,34 @@ and .Ar destination are the addresses used on the tunnel device. -If you configure the tunnel against a cisco router, use a netmask of +If you configure the tunnel against a Cisco router, use a netmask of .Dq 255.255.255.252 -on the cisco. This is because the tunnel is a point-to-point interface +on the Cisco router. This is because the tunnel is a point-to-point interface in the .Bx Free -end, a concept cisco doesn't really implement. +end, a concept Cisco doesn't really implement. Destination may be +a hostname. .Pp .Ar Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many peoples use 4 in worldwide backbone of ampr.org. .Pp +.Ar Retry count +if provided, limits the number of times +.Nm nos-tun +will attempt to re-establish a tunnel when a connection fails. Use 0 +for infinite retries. The default is 10. When performing a retry, the +tunnel is shut down and rebuilt, performing name lookups again if +applicable. This allows for building tunnels with static addresses +across links with dynamic addresses. +.Pp +.Ar Retry delay +Number of seconds to sleep before trying to re-establish a tunnel. +The default is 60 seconds. +.Pp .Ar Target is the address of the remote tunnel device, this must match the source -address set on the remote end. +address set on the remote end. Target may be a hostname. .Sh EXAMPLES This end, a .Bx Free @@ -68,7 +86,7 @@ nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45 .Ed .Pp -Remote cisco on address 192.168.56.45: +Remote Cisco router on address 192.168.56.45: .Bd -literal -offset indent 4m interface tunnel 0 ip address 192.168.61.2 255.255.255.252 @@ -85,3 +103,5 @@ wrote the man-page. .An Isao SEKI Aq iseki@gongon.com added a new flag, IP protocol number. +.An Nick Johnson +added retries, -r and -w flags.