SHOREWALL6-ROUTESTO(5) [FIXME: manual] SHOREWALL6-ROUTESTO(5)NAME
routestopped - The Shorewall6 file that governs what traffic flows
through the firewall while it is in 'stopped' state.
SYNOPSIS
/etc/shorewall6/routestopped
DESCRIPTION
This file is deprecated in favor of the shorewall6-stoppedrules[1](5)
file.
This file is used to define the hosts that are accessible when the
firewall is stopped or is being stopped. When shorewall6-shell is being
used, the file also determines those hosts that are accessible when the
firewall is in the process of being [re]started.
The columns in the file are as follows (where the column name is
followed by a different name in parentheses, the different name is used
in the alternate specification syntax).
INTERFACE - interface
Interface through which host(s) communicate with the firewall
HOST(S) - [-|address[,address]...]
Optional comma-separated list of IP/subnet addresses. If your
kernel and ip6tables include iprange match support, IP address
ranges are also allowed.
If left empty or supplied as "-", 0.0.0.0/0 is assumed.
OPTIONS - [-|option[,option]...]
An optional comma-separated list of options. The order of the
options is not important but the list can contain no embedded
white-space. The currently-supported options are:
routeback
Set up a rule to ACCEPT traffic from these hosts back to
themselves. Beginning with Shorewall 4.4.9, this option is
automatically set if routeback is specified in
shorewall6-interfaces[2] (5) or if the rules compiler detects
that the interface is a bridge.
source
Allow traffic from these hosts to ANY destination. Without this
option or the dest option, only traffic from this host to other
listed hosts (and the firewall) is allowed. If source is
specified then routeback is redundant.
dest
Allow traffic to these hosts from ANY source. Without this
option or the source option, only traffic from this host to
other listed hosts (and the firewall) is allowed. If dest is
specified then routeback is redundant.
critical
Allow traffic between the firewall and these hosts throughout
'[re]start', 'stop' and 'clear'. Specifying critical on one or
more entries will cause your firewall to be "totally open" for
a brief window during each of those operations. Examples of
where you might want to use this are:
· 'Ping' nodes with heartbeat.
· LDAP server(s) if you use LDAP Authentication
· NFS Server if you have an NFS-mounted root filesystem.
Note
The source and dest options work best when used in conjunction with
ADMINISABSENTMINDED=Yes in shorewall6.conf[3](5).
EXAMPLE
Example 1:
#INTERFACE HOST(S) OPTIONS
eth2 2002:ce7c:92b4::/64
eth0 2002:ce7c:92b4:1::/64
br0 - routeback
eth3 - source
FILES
/etc/shorewall6/routestopped
SEE ALSO
http://shorewall.net/starting_and_stopping_shorewall.htm
http://shorewall.net/configuration_file_basics.htm#Pairs
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5),
shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shorewall6-netmap(5),shorewall6-params(5),
shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(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-stoppedrules
http://www.shorewall.net/manpages6/shorewall-stoppedrules.html
2. shorewall6-interfaces
http://www.shorewall.net/manpages6/shorewall6-interfaces.html
3. shorewall6.conf
http://www.shorewall.net/manpages6/shorewall6.conf.html
[FIXME: source] 12/19/2013 SHOREWALL6-ROUTESTO(5)
