Provided by: shorewall6_220.127.116.11-1_all
exclusion - Exclude a set of hosts from a definition in a shorewall6
Exclusion is used when you wish to exclude one or more addresses from a
definition. An exclaimation point is followed by a comma-separated list
of addresses. The addresses may be single host addresses (e.g.,
fe80::2a0:ccff:fedb:31c4) or they may be network addresses in CIDR
format (e.g., fe80::2a0:ccff:fedb:31c4/64). If your kernel and
ip6tables include iprange support, you may also specify ranges of ip
addresses of the form lowaddress-highaddress
No embedded whitespace is allowed.
Exclusion can appear after a list of addresses and/or address ranges.
In that case, the final list of address is formed by taking the first
list and then removing the addresses defined in the exclusion.
Beginning in Shorewall 4.4.13, the second form of exclusion is allowed
after all and any in the SOURCE and DEST columns of
/etc/shorewall/rules. It allows you to omit arbitrary zones from the
list generated by those key words.
If you omit a sub-zone and there is an explicit or explicit
CONTINUE policy, a connection to/from that zone can still be
matched by the rule generated for a parent zone.
#SOURCE DEST POLICY
z1 net CONTINUE
z2 net REJECT
#ACTION SOURCE DEST PROTO DEST
ACCEPT all!z2 net tcp 22
In this case, SSH connections from z2 to net will be accepted by
the generated z1 to net ACCEPT rule.
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5),
shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5),
shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5),
[FIXME: source] 12/13/2011 SHOREWALL6-EXCLUSIO(5)