shorewall6-tunnels(5)

1SHOREWALL6-TUNNELS(5)           [FIXME: manual]          SHOREWALL6-TUNNELS(5)
2
3
4

NAME

6       tunnels - Shorewall6 VPN definition file
7

SYNOPSIS

9       /etc/shorewall6/tunnels
10

DESCRIPTION

12       The tunnels file is used to define rules for encapsulated (usually
13       encrypted) traffic to pass between the Shorewall6 system and a remote
14       gateway. Traffic flowing through the tunnel is handled using the normal
15       zone/policy/rule mechanism. See http://www.shorewall.net/VPNBasics.html
16       for details.
17
18       The columns in the file are as follows.
19
20       TYPE -
21       {ipsec[:{noah|ah}]|ipsecnat|gre|l2tp|pptpclient|pptpserver|{openvpn|openvpnclient|openvpnserver}[:{tcp|udp}][:port]|generic:protocol[:port]}
22           Types are as follows:
23
24                       ipsec         - IPv6 IPSEC
25                       ipsecnat      - IPv6 IPSEC with NAT Traversal (UDP port 4500 encapsulation)
26                       gre           - Generalized Routing Encapsulation (Protocol 47)
27                       l2tp          - Layer 2 Tunneling Protocol (UDP port 1701)
28                       openvpn       - OpenVPN in point-to-point mode
29                       openvpnclient - OpenVPN client runs on the firewall
30                       openvpnserver - OpenVPN server runs on the firewall
31                       generic       - Other tunnel type
32
33           If the type is ipsec, it may be followed by :ah to indicate that
34           the Authentication Headers protocol (51) is used by the tunnel (the
35           default is :noah which means that protocol 51 is not used). NAT
36           traversal is only supported with ESP (protocol 50) so ipsecnat
37           tunnels don't allow the ah option (ipsecnat:noah may be specified
38           but is redundant).
39
40           If type is openvpn, openvpnclient or openvpnserver it may
41           optionally be followed by ":" and tcp or udp to specify the
42           protocol to be used. If not specified, udp is assumed. Note: At
43           this writing, OpenVPN does not support IPv6.
44
45           If type is openvpn, openvpnclient or openvpnserver it may
46           optionally be followed by ":" and the port number used by the
47           tunnel. if no ":" and port number are included, then the default
48           port of 1194 will be used. . Where both the protocol and port are
49           specified, the protocol must be given first (e.g.,
50           openvpn:tcp:4444).
51
52           If type is generic, it must be followed by ":" and a protocol name
53           (from /etc/protocols) or a protocol number. If the protocol is tcp
54           or udp (6 or 17), then it may optionally be followed by ":" and a
55           port number.
56
57       ZONE - zone
58           The zone of the physical interface through which tunnel traffic
59           passes. This is normally your internet zone.
60
61       GATEWAY - address-or-range
62           The IP address of the remote tunnel gateway. If the remote gateway
63           has no fixed address (Road Warrior) then specify the gateway as
64           ::/0. May be specified as a network address and if your kernel and
65           ip6tables include iprange match support then IP address ranges are
66           also allowed.
67
68       GATEWAY ZONES (Optional) - [zone[,zone]...]
69           If the gateway system specified in the third column is a standalone
70           host then this column should contain a comma-separated list of the
71           names of the zones that the host might be in. This column only
72           applies to IPSEC tunnels where it enables ISAKMP traffic to flow
73           through the tunnel to the remote gateway.
74

EXAMPLE

76       Example 1:
77           IPSec tunnel.
78
79           The remote gateway is 2001:cec792b4:1::44. The tunnel does not use
80           the AH protocol
81
82                       #TYPE           ZONE    GATEWAY
83                       ipsec:noah      net     2002:cec792b4:1::44
84
85       Example 2:
86           Road Warrior (LapTop that may connect from anywhere) where the "gw"
87           zone is used to represent the remote LapTop
88
89                       #TYPE           ZONE    GATEWAY                 GATEWAY ZONES
90                       ipsec           net     ::/0                    gw
91
92       Example 3:
93           Host 2001:cec792b4:1::44 is a standalone system connected via an
94           ipsec tunnel to the firewall system. The host is in zone gw.
95
96                       #TYPE           ZONE    GATEWAY                 GATEWAY ZONES
97                       ipsec           net     2001:cec792b4:1::44     gw
98
99       Example 4:
100           OPENVPN tunnel. The remote gateway is 2001:cec792b4:1::44 and
101           openvpn uses port 7777.
102
103                       #TYPE           ZONE    GATEWAY                 GATEWAY ZONES
104                       openvpn:7777    net     2001:cec792b4:1::44
105
106       Example 8:
107           You have a tunnel that is not one of the supported types. Your
108           tunnel uses UDP port 4444. The other end of the tunnel is
109           2001:cec792b4:1::44.
110
111                       #TYPE            ZONE    GATEWAY                GATEWAY ZONES
112                       generic:udp:4444 net     2001:cec792b4:1::44
113

FILES

115       /etc/shorewall6/tunnels
116

NAME

SYNOPSIS

DESCRIPTION

EXAMPLE

FILES

SEE ALSO