shorewall6-exclusion(5) [debian man page]

SHOREWALL6-EXCLUSIO(5)						  [FIXME: manual]					    SHOREWALL6-EXCLUSIO(5)

NAME

       exclusion - Exclude a set of hosts from a definition in a shorewall6 configuration file.

SYNOPSIS

       !address-or-range[,address-or-range]...

       !zone-name[,zone-name]...

DESCRIPTION

       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.

	   Warning
	   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.

	   For example:

	   /etc/shorewall6/zones:

	       #ZONE	      TYPE
	       z1	      ip
	       z2:z1	      ip
	       ...

	   /etc/shorewall6/policy:

	       #SOURCE	       DEST	     POLICY
	       z1	       net	     CONTINUE
	       z2	       net	     REJECT

	   /etc/shorewall6/rules:

	       #ACTION	       SOURCE	     DEST	 PROTO	       DEST
	       #						       PORT(S)
	       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.

FILES

       /etc/shorewall6/hosts

       /etc/shorewall6/masq

       /etc/shorewall6/rules

       /etc/shorewall6/tcrules

SEE ALSO

       shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
       shorewall6-maclist(5), shoewall6-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-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall-zones(5)

[FIXME: source] 						    06/28/2012						    SHOREWALL6-EXCLUSIO(5)

SHOREWALL-IPSETS(5)						  [FIXME: manual]					       SHOREWALL-IPSETS(5)

NAME

       ipsets - Specifying the name if an ipset in Shorewall6 configuration files

SYNOPSIS

       +ipsetname

       +ipsetname[flag,...]

       +[ipsetname,...]

DESCRIPTION

       Note: In the above syntax descriptions, the square brackets ("[]") are to be taken literally rather than as meta-characters.

       In most places where a network address may be entered, an ipset may be substituted. Set names must be prefixed by the character "+", must
       start with a letter and may be composed of alphanumeric characters, "-" and "_".

       Whether the set is matched against the packet source or destination is determined by which column the set name appears (SOURCE or DEST).
       For those set types that specify a tupple, two alternative syntaxes are available:
	   [number] - Indicates that 'src' or
		 'dst' should repleated number times. Example: myset[2].
	   [flag,...] where
		 flag is src or
		 dst. Example: myset[src,dst].

       In a SOURCE column, the following pairs are equivalent:

       o   +myset[2] and +myset[src,src]

       In a DEST column, the following paris are equivalent:

       o   +myset[2] and +myset[dst,dst]

       Beginning with Shorewall 4.4.14, multiple source or destination matches may be specified by enclosing the set names within +[...]. The set
       names need not be prefixed with '+'. When such a list of sets is specified, matching packets must match all of the listed sets.

       For information about set lists and exclusion, see shorewall-exclusion[1] (5).

EXAMPLES

       +myset

       +myset[src]

       +myset[2]

       +[myset1,myset2[dst]]

FILES

       /etc/shorewall6/accounting

       /etc/shorewall6/blacklist

       /etc/shorewall6/hosts -- Note: Multiple matches enclosed in +[...] may not be used in this file.

       /etc/shorewall6/maclist -- Note: Multiple matches enclosed in +[...] may not be used in this file.

       /etc/shorewall6/rules

       /etc/shorewall6/secmarks

       /etc/shorewall6/tcrules

SEE ALSO

       shorewall6(8), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5),
       shoewall6-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-tcrules(5),
       shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)

NOTES

	1. shorewall-exclusion
	   http://www.shorewall.net/manpages6/shorewall-exclusion.html

[FIXME: source] 						    06/28/2012						       SHOREWALL-IPSETS(5)