shorewall6-proxyndp(5) [debian man page]

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

NAME

       proxyndp - Shorewall6 Proxy NDP file

SYNOPSIS

       /etc/shorewall6/proxyndp

DESCRIPTION

       This file was added in Shoreall 4.4.16 and is used to define Proxy NDP. There is one entry in this file for each IPv6 address to be
       proxied.

       The columns in the file are as follows.

       ADDRESS - address
	   IPv6 Address.

       INTERFACE - interface (Optional)
	   Local interface where system with the ip address in ADDRESS is connected. Only required when the HAVEROUTE column is left empty or is
	   set to no or No.

       EXTERNAL - interface
	   External Interface to be used to access this system from the Internet.

       HAVEROUTE - [-|Yes|No]
	   If there is already a route from the firewall to the host whose address is given, enter Yes or yes in this column. Otherwise, enter no
	   or No or leave the column empty and Shorewall will add the route for you. If Shorewall6 adds the route, its persistence depends on the
	   value of thePERSISTENT column contains Yes; otherwise, shorewall6 stop or shorewall clear6 will delete the route.

       PERSISTENT - [-|Yes|No]
	   If HAVEROUTE is No or no, then the value of this column determines if the route added by Shorewall persists after a shorewall6 stop or
	   a shorewall6 clear. If this column contains Yes or yes then the route persists; If the column is empty or contains No or no then the
	   route is deleted by shorewall6 stop or shorewall6 clear.

EXAMPLE

       Example 1:
	   Host with IPv6 2001:470:b:227::44 is connected to interface eth1 and we want hosts attached via eth0 to be able to access it using that
	   address.

		      #ADDRESS		   INTERFACE	   EXTERNAL
		      2001:470:b:227::44   eth1 	   eth0

FILES

       /etc/shorewall6/proxyndp

SEE ALSO

       http://shorewall.net/configuration_file_basics.htm#Pairs

       shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-exclusion(5), shorewall6-hosts(5),
       shorewall6-interfaces(5), shorewall6-maclist(5), shorewall6-nesting(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)

[FIXME: source] 						    06/28/2012						    SHOREWALL6-PROXYNDP(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)