shorewall6-params(5) [debian man page]

SHOEWALL6-NETMAP(5)(5)						  [FIXME: manual]					    SHOEWALL6-NETMAP(5)(5)

NAME

       params - Shorewall6 parameters file

SYNOPSIS

       /etc/shorewall6/params

DESCRIPTION

       Assign any shell variables that you need in this file. The file is always processed by /bin/sh or by the shell specified through
       SHOREWALL_SHELL in shorewall6.conf[1] (5) so the full range of shell capabilities may be used.

       It is suggested that variable names begin with an upper case letter to distinguish them from variables used internally within the Shorewall
       programs

       The following variable names must be avoided. Those in bold font must be avoided in all Shorewall versions; those in regular font must be
       avoided in versions prior to 4.4.8.
	   Any option from shorewall6.conf[1]
		 (5)
	   COMMAND
	   CONFDIR
	   DEBUG
	   ECHO_E
	   ECHO_N
	   EXPORT
	   FAST
	   FILEMODE
	   HOSTNAME
	   IPT_OPTIONS
	   NOROUTES
	   PREVIEW
	   PRODUCT
	   PROFILE
	   PURGE
	   RECOVERING
	   RESTOREPATH
	   RING_BELL
	   SHAREDIR
	   Any name beginning with SHOREWALL_ or
		 SW_
	   STOPPING
	   TEST
	   TIMESTAMP
	   USE_VERBOSITY
	   VARDIR
	   VERBOSE
	   VERBOSE_OFFSET
	   VERSION

       Example params file:

	   NET_IF=eth0
	   NET_OPTIONS=dhcp,nosmurfs

       Example shorewall6-interfaces[2](5) file.

	   ZONE    INTERFACE	   BROADCAST	   OPTIONS
	   net	   $NET_IF	   -		   $NET_OPTIONS

       This is the same as if the interfaces file had contained:

	   ZONE    INTERFACE	   BROADCAST	   OPTIONS
	   net	   eth0 	   -		   dhcp,nosmurfs

FILES

       /etc/shorewall6/params

SEE ALSO

       http://www.shorewall.net/configuration_file_basics.htm#Variables[3]

       shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
       shorewall6-maclist(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.conf
	   http://www.shorewall.net/manpages6/shorewall6.conf.html

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

	3. http://www.shorewall.net/configuration_file_basics.htm#Variables
	   http://www.shorewall.net/configuration_file_basics.htm#Variables?

[FIXME: source] 						    06/28/2012						    SHOEWALL6-NETMAP(5)(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)