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)

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

NAME

       nesting - shorewall6 Nested Zones

SYNOPSIS

       child-zone[:parent-zone[,parent-zone]...]

DESCRIPTION

       In shorewall6-zones[1](5), a zone may be declared to be a sub-zone of one or more other zones using the above syntax. The child-zone may be
       neither the firewall zone nor a vserver zone. The firewall zone may not appear as a parent zone, although all vserver zones are handled as
       sub-zones of the firewall zone.

       Where zones are nested, the CONTINUE policy in shorewall6-policy[2](5) allows hosts that are within multiple zones to be managed under the
       rules of all of these zones.

EXAMPLE

       /etc/shorewall6/zones:

		   #ZONE    TYPE	OPTION
		   fw	    firewall
		   net	    ipv6
		   sam:net  ipv6
		   loc	    ipv6

       /etc/shorewall6/interfaces:

		   #ZONE     INTERFACE	   BROADCAST	 OPTIONS
		   -	     eth0	   detect	 blacklist
		   loc	     eth1	   detect

       /etc/shorewall6/hosts:

		   #ZONE     HOST(S)			 OPTIONS
		   net	     eth0:[::]
		   sam	     eth0:[2001:19f0:feee::dead:beef:cafe]

       /etc/shorewall6/policy:

		   #SOURCE	DEST	    POLICY	 LOG LEVEL
		   loc		net	    ACCEPT
		   sam		all	    CONTINUE
		   net		all	    DROP	 info
		   all		all	    REJECT	 info

       The second entry above says that when Sam is the client, connection requests should first be processed under rules where the source zone is
       sam and if there is no match then the connection request should be treated under rules where the source zone is net. It is important that
       this policy be listed BEFORE the next policy (net to all). You can have this policy generated for you automatically by using the
       IMPLICIT_CONTINUE option in shorewall6.conf[3](5).

       Partial /etc/shorewall6/rules:

		   #ACTION   SOURCE    DEST		     PROTO    DEST PORT(S)
		   ...
		   ACCEPT    sam       loc:2001:19f0:feee::3 tcp      ssh
		   ACCEPT    net       loc:2001:19f0:feee::5 tcp      www
		   ...

       Given these two rules, Sam can connect with ssh to 2001:19f0:feee::3. Like all hosts in the net zone, Sam can connect to TCP port 80 on
       2001:19f0:feee::5. The order of the rules is not significant.

FILES

       /etc/shorewall6/zones

       /etc/shorewall6/interfaces

       /etc/shorewall6/hosts

       /etc/shorewall6/policy

       /etc/shorewall6/rules

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), shorewall6-zones(5)

NOTES

	1. shorewall6-zones
	   http://www.shorewall.net/manpages6/shorewall-zones.html

	2. shorewall6-policy
	   http://www.shorewall.net/manpages6/shorewall6-policy.html

	3. shorewall6.conf
	   http://www.shorewall.net/manpages6/shorewall6.conf.html

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