SHOREWALL6-ZONES(5) | Configuration Files | SHOREWALL6-ZONES(5) |
NAME¶
zones - Shorewall6 zone declaration fileSYNOPSIS¶
/etc/shorewall6/zones
DESCRIPTION¶
The /etc/shorewall6/zones file declares your network zones. You specify the hosts in each zone through entries in /etc/shorewall6/interfaces or /etc/shorewall6/hosts.The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in the alternate specification syntax).
ZONE - zone[:parent-zone[,parent-zone]...]
Example:
#ZONE TYPE OPTIONS IN OPTIONS OUT OPTIONS a ipv6 b ipv6 c:a,b ipv6
Currently, Shorewall6 uses this information to reorder the zone list so that parent zones appear after their subzones in the list. The IMPLICIT_CONTINUE option in shorewall6.conf[1](5) can also create implicit CONTINUE policies to/from the subzone.
Where an ipsec zone is explicitly included as a child of an ipv6 zone, the ruleset allows CONTINUE policies (explicit or implicit) to work as expected.
In the future, Shorewall6 may make additional use of nesting information.
TYPE
ipv6
ipsec (or ipsec6)
firewall
bport (or bport6)
vserver
Vserver zones are implicitly handled as subzones of the firewall zone.
loopback
Normally, Shorewall treats the loopback interface (lo) in the following way:
By defining a loopback zone and associating it with the loopback interface in shorewall-interfaces(5), you can effect a slightly different model. Suppose that the loopback zone name is 'local'; then:
Rules to/from the loopback zone and any zone other than the firewall zone are ignored with a warning.
loopback zones may be nested within other loopback zones.
local
OPTIONS, IN OPTIONS and OUT OPTIONS (options, in_options, out_options) - [option[,option]...]
blacklist
When specified in the IN_OPTIONS column, causes all traffic from this zone to be passed against the src entries in shorewall6-blacklist[4](5).
When specified in the OUT_OPTIONS column, causes all traffic to this zone to be passed against the dst entries in shorewall6-blacklist[4](5).
Specifying this option in the OPTIONS column is equivalent to entering it in both of the IN_OPTIONS and OUT_OPTIONS column.
dynamic_shared
reqid=number
spi=<number>
proto=ah|esp|ipcomp
mss=number
mode=transport|tunnel
tunnel-src=address[/mask]
tunnel-dst=address[/mask]
strict
next
The options in the OPTIONS column are applied to both incoming and outgoing traffic. The IN OPTIONS are applied to incoming traffic (in addition to OPTIONS) and the OUT OPTIONS are applied to outgoing traffic.
If you wish to leave a column empty but need to make an entry in a following column, use "-".
FILES¶
/etc/shorewall6/zonesSEE ALSO¶
http://www.shorewall.net/Multiple_Zones.html[5].http://www.shorewall.net/configuration_file_basics.htm#Pairs[6]
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5), shorewall6-nesting(8), shorewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5), shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-mangle(5), shorewall6-tos(5), shorewall6-tunnels(5)
NOTES¶
- 1.
- shorewall6.conf
- 2.
- shorewall6-nesting
- 3.
- shorewall6-hosts
- 4.
- shorewall6-blacklist
03/16/2017 | Configuration Files |