shorewall68Administrative Commandsshorewall6Administration tool for Shoreline Firewall 6
(Shorewall6)shorewall6|-optionsinterface[:host-list]zone | zone host-list
shorewall6|-optionsaddressshorewall6|-optionsaddressshorewall6|-optionsfunctionparameter
...shorewall6|-optionsdirectoryshorewall6|-optionsshorewall6|-optionsopen-number |
sourcedestprotocolportshorewall6|-optionsdirectorypathnameshorewall6|-optionsinterface[:host-list]zone | zone host-list
shorewall6|-options{ interface |
provider }shorewall6|-optionsaddressshorewall6|-optionsshorewall6|-options{ interface |
provider }shorewall6|-optionsdirectory1[user@]system[directory2]shorewall6|-optionsfilenameshorewall6|-optionsshorewall6|-optionsiptables match
expressionshorewall6|-optionsaddressshorewall6|-optionsrefresh-intervalshorewall6|-optionsaddressshorewall6|-optionsiptables match
expressionshorewall6|-options
source destprotocolportshorewall6|-options{ interface |
provider }shorewall6|-options-
directorychainshorewall6|-optionsaddressshorewall6|-optionsroot-user-namedirectorysystemshorewall6|-optionsroot-user-namedirectorysystemshorewall6|-optionsroot-user-namedirectorysystemshorewall6|-optionschain
...shorewall6|-optionsdirectoryshorewall6|-optionsdirectoryshorewall6|-optionsfilenameshorewall6|-optionscommandparameter ...shorewall6|-optionstimeoutdirectoryshorewall6|-optionstimeoutdirectoryshorewall6|-optionstimeoutdirectoryshorewall6|-optionsfilenameshorewall6|-optionsshorewall6|-optionsshorewall6|-options
{||}chainshorewall6|-optionsshorewall6|-optionsshorewall6|-optionseventshorewall6|-optionsshorewall6|-optionsshorewall6|-optionsshorewall6|-optionsshorewall6|-optionsdirectoryshorewall6|-optionsshorewall6|-optionsshorewall6|-optionsdirectorytimeoutshorewall6|-optionsdirectoryshorewall6|-optionsDescriptionThe shorewall6 utility is used to control the Shoreline Firewall 6
(Shorewall6).OptionsThe and options are
used for debugging. See http://www.shorewall.net/starting_and_stopping_shorewall.htm#Trace.The option prevents the command from
attempting to acquire the Shorewall6 lockfile. It is useful if you need to
include shorewall6 commands in
/etc/shorewall6/started.The options control the amount of output that
the command produces. They consist of a sequence of the letters v and q. If the
options are omitted, the amount of output is determined by the setting of
the VERBOSITY parameter in shorewall6.conf(5). Each
v adds one to the effective verbosity and
each q subtracts one from the effective
VERBOSITY. Alternatively, v may be
followed immediately with one of -1,0,1,2 to specify a specify VERBOSITY.
There may be no white-space between v and
the VERBOSITY.The options may also include the letter
which causes all progress messages to be
timestamped.CommandsThe available commands are listed below.add {
interface[:host-list]...
zone | zonehost-list }Added in Shorewall 4.4.21. Adds a list of hosts or subnets to
a dynamic zone usually used with VPN's.The interface argument names an interface
defined in the shorewall6-interfaces(5)
file. A host-list is comma-separated list whose
elements are host or network addresses.The add command is not very robust. If
there are errors in the host-list,
you may see a large number of error messages yet a subsequent
shorewall show zones command will indicate
that all hosts were added. If this happens, replace
add by delete and run the
same command again. Then enter the correct command.Beginning with Shorewall 4.5.9, the dynamic_shared zone option (shorewall6-zones(5))
allows a single ipset to handle entries for multiple interfaces.
When that option is specified for a zone, the add
command has the alternative syntax in which the
zone name precedes the
host-list.allow
addressRe-enables receipt of packets from hosts previously
blacklisted by a drop, logdrop, reject, or logreject command.blacklistaddress [ option
... ]Added in Shorewall 5.0.8 and requires
DYNAMIC_BLACKLIST=ipset.. in shorewall6.conf(5).
Causes packets from the given host or network
address to be dropped, based on the
setting of BLACKLIST in shorewall6.conf(5).
The address along with any
options are passed to the ipset
add command.call function [
parameter ... ]Added in Shorewall 4.6.10. Allows you to call a function in
one of the Shorewall libraries or in your compiled script. function
must name the shell function to be called. The listed parameters are
passed to the function.The function is first searched for in
lib.base, lib.common,
lib.cli and lib.cli-std.
If it is not found, the call command is passed to the generated
script to be executed.check [-]
[-] [-] [-]
[-] [-]
[directory]Compiles the configuration in the specified
directory and discards the compiled output
script. If no directory is given, then
/etc/shorewall6 is
assumed.The option causes the compiler to look for
a file named capabilities. This file is produced using the command
shorewall6-lite show -f capabilities >
capabilities on a system with Shorewall6 Lite
installed.The option causes the compiler to be run
under control of the Perl debugger.The option causes the compiler to be
profiled via the Perl command-line
option.The option was added in Shorewall 4.5.2
and causes the compiler to print the generated ruleset to standard
out.The option was added in Shorewall 4.4.20
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).clear
[-]Clear will remove all rules and chains installed by
Shorewall6. The firewall is then wide open and unprotected. Existing
connections are untouched. Clear is often used to see if the
firewall is causing connection problems.close {
open-number |
sourcedest [
protocol [ port
] ] }Added in Shorewall 4.5.8. This command closes a temporary open
created by the open command. In the first form,
an open-number specifies the open to be
closed. Open numbers are displayed in the num column of the output of the
shorewall6 show opens command.When the second form of the command is used, the parameters
must match those given in the earlier open
command.compile [-]
[-] [-] [-]
[-] [-]
[directory]
[pathname ]Compiles the current configuration into the executable file
pathname. If a directory is supplied,
Shorewall6 will look in that directory first for configuration
files. If the pathname is omitted, the file
firewall in the VARDIR (normally /var/lib/shorewall/) is assumed. A
pathname of '-' causes the compiler to send the
generated script to it's standard output file. Note that '-v-1' is
usually specified in this case (e.g., shorewall6 -v-1
compile -- -) to suppress the 'Compiling...' message
normally generated by /sbin/shorewall6.When is specified, the compilation is
being performed on a system other than where the compiled script
will run. This option disables certain configuration options that
require the script to be compiled where it is to be run. The use of
requires the presence of a configuration file
named capabilities which may be produced using
the command shorewall6-lite show -f capabilities >
capabilities on a system with Shorewall6 Lite
installed.The option was added in Shorewall 4.5.17
and causes conditional compilation of a script. The script specified
by pathname (or implied if pathname is omitted) is compiled if it
doesn't exist or if there is any file in the
directory or in a directory on the
CONFIG_PATH that has a modification time later than the file to be
compiled. When no compilation is needed, a message is issued and an
exit status of zero is returned.The option causes the compiler to be run
under control of the Perl debugger.The option causes the compiler to be
profiled via the Perl command-line
option.The option was added in Shorewall 4.4.20
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).delete {
interface[:host-list]...
zone | zonehost-list }Added in Shorewall 4.4.21. The delete command reverses the
effect of an earlier add
command.The interface argument names an interface
defined in the shorewall6-interfaces(5)
file. A host-list is comma-separated list whose
elements are a host or network address.Beginning with Shorewall 4.5.9, the dynamic_shared zone option (shorewall6-zones(5))
allows a single ipset to handle entries for multiple interfaces.
When that option is specified for a zone, the
delete command has the alternative syntax in
which the zone name precedes the
host-list.disable { interface |
provider }Added in Shorewall 4.4.26. Disables the optional provider
associated with the specified interface
or provider. Where more than one provider
share a single network interface, a
provider name must be given.Beginning with Shorewall 4.5.10, this command may be used with
any optional network interface. interface
may be either the logical or physical name of the interface. The
command removes any routes added from shorewall6-routes(5)
and any traffic shaping configuration for the interface.drop
addressCauses traffic from the listed addresses
to be silently dropped.dump [-]
[-] [-]
[-]Produces a verbose report about the firewall configuration for
the purpose of problem analysis.The option causes actual packet and byte
counts to be displayed. Without that option, these counts are
abbreviated.The option causes any MAC addresses
included in Shorewall6 log messages to be displayed.The option causes the rule number for each
Netfilter rule to be displayed.The option causes the route cache to be
dumped in addition to the other routing information.enable {
interface |
provider }Added in Shorewall 4.4.26. Enables the optional provider
associated with the specified interface
or provider. Where more than one provider
share a single network interface, a
provider name must be given.Beginning with Shorewall 4.5.10, this command may be used with
any optional network interface. interface
may be either the logical or physical name of the interface. The
command sets /proc entries for the interface,
adds any route specified in shorewall6-routes(5)
and installs the interface's traffic shaping configuration, if
any.export
[directory1 ]
[user@]system[:directory2
]If directory1 is omitted, the current
working directory is assumed.Allows a non-root user to compile a shorewall6 script and
stage it on a system (provided that the user has access to the
system via ssh). The command is equivalent to:/sbin/shorewall6 compile -edirectory1directory1/firewall &&\scp directory1/firewalldirectory1/firewall.conf [user@]system:[directory2]In other words, the configuration in the specified (or
defaulted) directory is compiled to a file called firewall in that
directory. If compilation succeeds, then firewall and firewall.conf
are copied to system using scp.forget [
filename ]Deletes /var/lib/shorewall6/filename
and /var/lib/shorewall6/save
. If no filename is given then the
file specified by RESTOREFILE in shorewall6.conf(5) is
assumed.helpDisplays a syntax summary.iptrace ip6tables
match expressionThis is a low-level debugging command that causes iptables
TRACE log records to be created. See ip6tables(8) for
details.The ip6tables match expression must
be one or more matches that may appear in both the raw table OUTPUT
and raw table PREROUTING chains.The log message destination is determined by the
currently-selected IPv6 logging
backend.listlist is a synonym for
show -- please see below.logdrop
addressCauses traffic from the listed addresses
to be logged then discarded. Logging occurs at the log level
specified by the BLACKLIST_LOGLEVEL setting in shorewall6.conf
(5).logwatch [-]
[refresh-interval]Monitors the log file specified by the LOGFILE option in
shorewall6.conf(5) and
produces an audible alarm when new Shorewall6 messages are logged.
The option causes the MAC address of each packet
source to be displayed if that information is available. The
refresh-interval specifies the time in
seconds between screen refreshes. You can enter a negative number by
preceding the number with "--" (e.g., shorewall6 logwatch
-- -30). In this case, when a packet count changes, you
will be prompted to hit any key to resume screen refreshes.logrejectaddressCauses traffic from the listed addresses
to be logged then rejected. Logging occurs at the log level
specified by the BLACKLIST_LOGLEVEL setting in shorewall6.conf
(5).lsls is a synonym for show
-- please see below.noiptrace
ip6tables match
expressionThis is a low-level debugging command that cancels a trace
started by a preceding iptrace command.The iptables match expression must
be one given in the iptrace command being
canceled.opensourcedest [
protocol [ port
] ]Added in Shorewall 4.6.8. This command requires that the
firewall be in the started state and that DYNAMIC_BLACKLIST=Yes in
shorewall6.conf
(5). The effect of the command is to temporarily open the
firewall for connections matching the parameters.The source and
dest parameters may each be specified as
all if you don't wish to restrict
the connection source or destination respectively. Otherwise, each
must contain a host or network address or a valid DNS name.The protocol may be specified
either as a number or as a name listed in /etc/protocols. The
port may be specified numerically or as a
name listed in /etc/services.To reverse the effect of a successful open
command, use the close command with the same
parameters or simply restart the firewall.Example: To open the firewall for SSH connections to address
2001:470:b:227::1, the command would be: shorewall6 open all 2001:470:b:227::1 tcp 22To reverse that command, use: shorewall6 close all 2001:470:b:227::1 tcp 22reenable{
interface |
provider }Added in Shorewall 4.6.9. This is equivalent to a
disable command followed by an
enable command on the specified
interface or
provider.refresh [-]
[-] [-] [-i]
[-directory ] [
chain... ]All steps performed by restart are
performed by refresh with the exception that
refresh only recreates the chains specified in
the command while restart recreates the entire
Netfilter ruleset.When no chain name is given to the
refresh command, the mangle table is refreshed
along with the blacklist chain (if any). This allows you to modify
/etc/shorewall6/tcrulesand install the changes
using refresh.The listed chains are assumed to be in the filter table. You
can refresh chains in other tables by prefixing the chain name with
the table name followed by ":" (e.g., nat:net_dnat). Chain names
which follow are assumed to be in that table until the end of the
list or until an entry in the list names another table. Built-in
chains such as FORWARD may not be refreshed.The option was added in Shorewall 4.5.3
causes Shorewall to avoid updating the routing table(s).The option was added in Shorewall 4.5.3
causes the compiler to run under the Perl debugger.The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).The - option was added in Shorewall 4.5.3
and causes Shorewall to look in the given
directory first for configuration files.Refresh the 'net-fw' chain in the filter table and the
'net_dnat' chain in the nat tableshorewall6 refresh net-fw nat:net_dnat
reject
addressCauses traffic from the listed addresses
to be silently rejected.reload [-]
[-] [-] [-]
[-] [-] [-]
[-] [ directory ]This command was re-implemented in Shorewall 5.0.0. The
pre-5.0.0 reload command is now called
remote-restart (see below).Reload is similar to shorewall6 start
except that it assumes that the firewall is already started.
Existing connections are maintained. If a
directory is included in the command,
Shorewall6 will look in that directory first
for configuration files.The option causes Shorewall6 to avoid
updating the routing table(s).The option causes the connection tracking
table to be flushed; the conntrack utility must
be installed to use this option.The option causes the compiler to run
under the Perl debugger.The option suppresses the compilation step
and simply reused the compiled script which last started/restarted
Shorewall, provided that /etc/shorewall6
and its contents have not been modified since the last
start/restart.The option was added in Shorewall 4.4.20
and performs the compilation step unconditionally, overriding the
AUTOMAKE setting in shorewall6.conf(5).
When both and are present,
the result is determined by the option that appears last.The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).The option was added in Shorewall 4.6.5
and is only meaningful when AUTOMAKE=Yes in shorewall6.conf(5). If
an existing firewall script is used and if that script was the one
that generated the current running configuration, then the running
netfilter configuration will be reloaded as is so as to preserve the
iptables packet and byte counters.remote-reload
[-] [-]
[- root-user-name]
[-] [-] [
directory ]
systemThis command was added in Shorewall 5.0.0.If directory is omitted, the current
working directory is assumed. Allows a non-root user to compile a
shorewall6 script and install it on a system (provided that the user
has root access to the system via ssh). The command is equivalent
to:/sbin/shorewall6 compile -edirectorydirectory/firewall &&\scpdirectory/firewalldirectory/firewall.confroot@system:/var/lib/shorewall6-lite/ &&\ssh root@system'/sbin/shorewall6-lite reload'In other words, the configuration in the specified (or
defaulted) directory is compiled to a file called firewall in that
directory. If compilation succeeds, then firewall is copied to
system using scp. If the copy succeeds,
Shorewall6 Lite on system is restarted via
ssh.If is specified and the
restart command succeeds, then the remote
Shorewall6-lite configuration is saved by executing
shorewall6-lite save via ssh.if is included, the command
shorewall6-lite show capabilities -f >
/var/lib/shorewall6-lite/capabilities is executed via ssh
then the generated file is copied to directory
using scp. This step is performed before the configuration is
compiled.If is included, it specifies that the root
user on system is named
root-user-name rather than "root".The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).remote- restart
[-] [-]
[- root-user-name]
[-] [-] [
directory ]
systemThis command was renamed from reload in
Shorewall 5.0.0.If directory is omitted, the current
working directory is assumed. Allows a non-root user to compile a
shorewall6 script and install it on a system (provided that the user
has root access to the system via ssh). The command is equivalent
to:/sbin/shorewall6 compile -edirectorydirectory/firewall &&\scpdirectory/firewalldirectory/firewall.confroot@system:/var/lib/shorewall6-lite/ &&\ssh root@system'/sbin/shorewall6-lite restart'In other words, the configuration in the specified (or
defaulted) directory is compiled to a file called firewall in that
directory. If compilation succeeds, then firewall is copied to
system using scp. If the copy succeeds,
Shorewall6 Lite on system is restarted via
ssh.If is specified and the
restart command succeeds, then the remote
Shorewall6-lite configuration is saved by executing
shorewall6-lite save via ssh.if is included, the command
shorewall6-lite show capabilities -f >
/var/lib/shorewall6-lite/capabilities is executed via ssh
then the generated file is copied to directory
using scp. This step is performed before the configuration is
compiled.If is included, it specifies that the root
user on system is named
root-user-name rather than "root".The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).remote-start
[-] [-] [-
root-user-name] [-]
[-] [ directory ]
systemThis command was added in Shorewall 5.0.0.If directory is omitted, the current
working directory is assumed. Allows a non-root user to compile a
shorewall6 script and install it on a system (provided that the user
has root access to the system via ssh). The command is equivalent
to:/sbin/shorewall6 compile -edirectorydirectory/firewall &&\scpdirectory/firewalldirectory/firewall.confroot@system:/var/lib/shorewall6-lite/ &&\ssh root@system'/sbin/shorewall6-lite start'In other words, the configuration in the specified (or
defaulted) directory is compiled to a file called firewall in that
directory. If compilation succeeds, then firewall is copied to
system using scp. If the copy succeeds,
Shorewall6 Lite on system is started via
ssh.If is specified and the start command succeeds, then the remote
Shorewall6-lite configuration is saved by executing
shorewall6-lite save via ssh.if is included, the command
shorewall6-lite show capabilities -f >
/var/lib/shorewall6-lite/capabilities is executed via ssh
then the generated file is copied to
directory using scp. This step is
performed before the configuration is compiled.If is included, it specifies that the root
user on system is named
root-user-name rather than "root".The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).reset [chain,
...]Resets the packet and byte counters in the specified
chain(s). If no
chain is specified, all the packet and
byte counters in the firewall are reset.Beginning with Shorewall 5.0.0,
chain may be composed of both a table
name and a chain name separated by a colon (e.g.,
mangle:PREROUTING). Chain names following that don't include a table
name are assumed to be in that same table. If no table name is given
in the command, the filter table is assumed.restart [-]
[-] [-] [-]
[-] [-] [-]
[-] [ directory ]Beginning with Shorewall 5.0.0, this command performs a true
restart. The firewall is completely stopped as if a
stop command had been issued then it is started
again.If a directory is included in the
command, Shorewall6 will look in that directory
first for configuration files.The option causes Shorewall6 to avoid
updating the routing table(s).The option causes the connection tracking
table to be flushed; the conntrack utility must
be installed to use this option.The option causes the compiler to run
under the Perl debugger.The option suppresses the compilation step
and simply reused the compiled script which last started/restarted
Shorewall, provided that /etc/shorewall6
and its contents have not been modified since the last
start/restart.The option was added in Shorewall 4.4.20
and performs the compilation step unconditionally, overriding the
AUTOMAKE setting in shorewall6.conf(5).
When both and are present,
the result is determined by the option that appears last.The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).The option was added in Shorewall 4.6.5
and is only meaningful when AUTOMAKE=Yes in shorewall6.conf(5). If
an existing firewall script is used and if that script was the one
that generated the current running configuration, then the running
netfilter configuration will be reloaded as is so as to preserve the
iptables packet and byte counters.restore [-]
[-] [-] [
filename ]Restore Shorewall6 to a state saved using the
shorewall6 save command. Existing connections are
maintained. The filename names a restore file
in /var/lib/shorewall6
created using shorewall6 save; if no
filename is given then Shorewall6 will be
restored from the file specified by the RESTOREFILE option in shorewall6.conf(5).If your ip6tables ruleset depends on variables that are
detected at run-time, either in your params file or by
Shorewall-generated code, restore will use the
values that were current when the ruleset was saved, which may be
different from the current values.The option was added in Shorewall 4.6.5.
If the option was specified during
shorewall6 save, then the counters saved by that
operation will be restored.runcommand [
parameter ... ]Added in Shorewall 4.6.3. Executes
command in the context of the generated
script passing the supplied parameters.
Normally, the command will be a function
declared in lib.private.Before executing the command, the
script will detect the configuration, setting all SW_* variables and
will run your init extension script with
$COMMAND = 'run'.If there are files in the CONFIG_PATH that were modified after
the current firewall script was generated, the following warning
message is issued before the script's run command is executed:
WARNING: /var/lib/shorewall6/firewall is not up to
datesafe-restart
[-] [-]
[-timeout ] [
directory ]Only allowed if Shorewall6 is running. The current
configuration is saved in /var/lib/shorewall6/safe-restart
(see the save command
below) then a shorewall6 restart is done. You
will then be prompted asking if you want to accept the new
configuration or not. If you answer "n" or if you fail to answer
within 60 seconds (such as when your new configuration has disabled
communication with your terminal), the configuration is restored
from the saved configuration. If a directory is given, then
Shorewall6 will look in that directory first when opening
configuration files.Beginning with Shorewall 4.5.0, you may specify a different
timeout value using the
option. The numeric
timeout may optionally be followed by an
, or suffix
(e.g., 5m) to specify seconds, minutes or hours respectively. If the
suffix is omitted, seconds is assumed.safe-start
[-] [-]
[-timeout ] [
directory ]Shorewall6 is started normally. You will then be prompted
asking if everything went all right. If you answer "n" or if you
fail to answer within 60 seconds (such as when your new
configuration has disabled communication with your terminal), a
shorewall6 clear is performed for you. If a directory is given, then
Shorewall6 will look in that directory first when opening
configuration files.Beginning with Shorewall 4.5.0, you may specify a different
timeout value using the
option. The numeric
timeout may optionally be followed by an
, or suffix
(e.g., 5m) to specify seconds, minutes or hours respectively. If the
suffix is omitted, seconds is assumed.save [-] [
filename ]The dynamic blacklist is stored in
/var/lib/shorewall6/save. The state of the firewall is
stored in
/var/lib/shorewall6/filename
for use by the shorewall6 restore and
shorewall6 -f start commands. If filename
is not given then the state is saved in the file
specified by the RESTOREFILE option in shorewall6.conf(5).The option, added in Shorewall 4.6.5,
causes the ip6tables packet and byte counters to be saved along with
the chains and rules.savesetsAdded in shorewall 4.6.8. Performs the same action as the
stop command with respect to saving ipsets (see
the SAVE_IPSETS option in shorewall6.conf (5)).
This command may be used to proactively save your ipset contents in
the event that a system failure occurs prior to issuing a
stop command.showThe show command can have a number of different
arguments:actionsProduces a report about the available actions (built-in,
standard and user-defined).[-] bl|blacklists
Added in Shorewall 4.6.2. Displays the dynamic chain
along with any chains produced by entries in
shorewall-blrules(5).The option is passed
directly through to ip6tables and causes actual packet and
byte counts to be displayed. Without this option, those counts
are abbreviated.[-] capabilitiesDisplays your kernel/ip6tables capabilities. The
option causes the display to be formatted
as a capabilities file for use with shorewall6
compile -e.[-] [-]
[-] [-
{||||}][
chain... ]The rules in each chain are
displayed using the ip6tables -Lchain-n
-v command. If no chain is
given, all of the chains in the filter table are displayed.
The option is passed directly through to
ip6tables and causes actual packet and byte counts to be
displayed. Without this option, those counts are abbreviated.
The option specifies the Netfilter table
to display. The default is filter.The ('brief') option causes rules
which have not been used (i.e. which have zero packet and byte
counts) to be omitted from the output. Chains with no rules
displayed are also omitted from the output.The option causes the rule number
for each Netfilter rule to be displayed.If the option and the
keyword are both omitted and any of the
listed chains do not exist, a usage
message is displayed.classifiers|filtersDisplays information about the packet classifiers
defined on the system as a result of traffic shaping
configuration.configDisplays distribution-specific defaults.connections
[filter_parameter
...]Displays the IP connections currently being tracked by
the firewall.If the conntrack utility is
installed, beginning with Shorewall 4.6.11 the set of
connections displayed can be limited by including conntrack
filter parameters (-p , -s, --dport, etc). See conntrack(8)
for details.event
eventAdded in Shorewall 4.5.19. Displays the named
event.eventsAdded in Shorewall 4.5.19. Displays all events.ipDisplays the system's IPv6 configuration.[-] logDisplays the last 20 Shorewall6 messages from the log
file specified by the LOGFILE option in shorewall6.conf(5).
The option causes the MAC address of each
packet source to be displayed if that information is
available.macrosDisplays information about each macro defined on the
firewall system.macro
macroAdded in Shorewall 4.4.6. Displays the file that
implements the specified macro
(usually
/usr/share/shorewall6/macro.macro).[-] mangleDisplays the Netfilter mangle table using the command
ip6tables -t mangle -L -n -v.The
option is passed directly through to
ip6tables and causes actual packet and byte counts to be
displayed. Without this option, those counts are
abbreviated.marksAdded in Shorewall 4.4.26. Displays the various fields
in packet marks giving the min and max value (in both decimal
and hex) and the applicable mask (in hex).[-] natDisplays the Netfilter nat table using the command
ip6tables -t nat -L -n -v.
The -x option is passed
directly through to ip6tables and causes actual packet and
byte counts to be displayed. Without this option, those counts
are abbreviated.opensAdded in Shorewall 4.5.8. Displays the iptables rules in
the 'dynamic' chain created through use of the open
command..policiesAdded in Shorewall 4.4.4. Displays the applicable policy
between each pair of zones. Note that implicit intrazone
ACCEPT policies are not displayed for zones associated with a
single network where that network doesn't specify
.[-] rawDisplays the Netfilter raw table using the command
ip6tables -t raw -L -n -v.
The -x option is passed
directly through to ip6tables and causes actual packet and
byte counts to be displayed. Without this option, those counts
are abbreviated.[-]routingDisplays the system's IPv6 routing configuration. The -c
option causes the route cache to be displayed in addition to
the other routing information.tcDisplays information about queuing disciplines, classes
and filters.zonesDisplays the current composition of the Shorewall6 zones
on the system.start [-] [-]
[-] [-] [-]
[-] [-] [-] [
directory ]Start shorewall6. Existing connections through shorewall6
managed interfaces are untouched. New connections will be allowed
only if they are allowed by the firewall rules or policies. If a
directory is included in the command,
Shorewall6 will look in that directory first
for configuration files. If is specified, the
saved configuration specified by the RESTOREFILE option in shorewall6.conf(5)
will be restored if that saved configuration exists and has been
modified more recently than the files in /etc/shorewall6. When is given, a directory may not
be specified.Update: In Shorewall6 4.4.20, a new LEGACY_FASTSTART option
was added to shorewall6.conf(5).
When LEGACY_FASTSTART=No, the modification times of files in
/etc/shorewall6 are compared
with that of /var/lib/shorewall6/firewall (the
compiled script that last started/restarted the firewall).The option causes Shorewall6 to avoid
updating the routing table(s).The option was added in Shorewall 4.4.20
and performs the compilation step unconditionally, overriding the
AUTOMAKE setting in shorewall6.conf(5).
When both and are present,
the result is determined by the option that appears last.The option was added in Shorewall 4.5.3
and causes a Perl stack trace to be included with each
compiler-generated error and warning message.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall6.conf(5).The option was added in Shorewall 4.6.5
and is only meaningful when the option is also
specified. If the previously-saved configuration is restored, and if
the option was also specified in the
save command, then the packet and byte counters
will be restored along with the chains and rules.stop
[-]Stops the firewall. All existing connections, except those
listed in shorewall6-routestopped(5)
or permitted by the ADMINISABSENTMINDED option in shorewall6.conf(5),
are taken down. The only new traffic permitted through the firewall
is from systems listed in shorewall6-routestopped(5)
or by ADMINISABSENTMINDED.If is given, the command will be processed
by the compiled script that executed the last successful start, restart or refresh command if that script exists.statusProduces a short report about the state of the
Shorewall6-configured firewall.The option was added in Shorewall 4.6.2
and causes the status of each optional or provider interface to be
displayed.try
directory [
timeout ]If Shorewall6 is started then the firewall state is saved to a
temporary saved configuration
(/var/lib/shorewall6/.try). Next, if Shorewall6
is currently started then a restart
command is issued using the specified configuration
directory; otherwise, a start command is performed using the
specified configuration directory. If an
error occurs during the compilation phase of the restart or start
, the command terminates without changing the Shorewall6
state. If an error occurs during the restart
phase, then a shorewall6 restore is
performed using the saved configuration. If an error occurs during
the start phase, then Shorewall6 is
cleared. If the start/ restart succeeds and a
timeout is specified then a clear or restore
is performed after timeout
seconds.Beginning with Shorewall 4.5.0, the numeric
timeout may optionally be followed by an
, or suffix
(e.g., 5m) to specify seconds, minutes or hours respectively. If the
suffix is omitted, seconds is assumed.update [-]
[-] [-] [-]
[-] [-] [
directory ]Added in Shorewall 4.4.21 and causes the compiler to update
/etc/shorewall/shorewall.conf then validate the
configuration. The update will add options not present in
the old file with their default values, and will move deprecated
options with non-defaults to a deprecated options section at the
bottom of the file. Your existing
shorewall.conf file is renamed
shorewall.conf.bak.The command was extended over the years with a set
of options that caused additional configuration
updates.Convert an existing blacklist file
into an equivalent blrules file.Convert an existing routestopped file
into an equivalent stoppedrules
file.Convert existing tcrules and
tos files into an equivalent mangle
file.Convert an existing notrack file into
an equivalent conntrack file.Convert FORMAT, SECTION and COMMENT entries into ?FORMAT,
?SECTION and ?COMMENT directives.In each case, the old file is renamed with a .bak
suffix.In Shorewall 5.0.0, the options were eliminated and the
update command performs all of the updates
described above.There are some notable restrictions with the
update command:Converted rules will be appended to the existing file;
if there is no existing file in the CONFIG_PATH, one will be
created in the directory specified in the command or in the
first entry in the CONFIG_PATH (normally /etc/shorewall6)
otherwise.Existing comments in the file being converted will not
be transferred to the output file.INCLUDEd files will be expanded inline in the output
file.Columns in the output file will be separated by a single
tab character; there is no attempt made to otherwise align the
columns.The option causes the updated
shorewall.conf file to be annotated with
documentation.The option was added in Shorewall 4.6.0
and causes a warning message to be issued if the current line
contains alternative input specifications following a semicolon
(";"). Such lines will be handled incorrectly if INLINE_MATCHES is
set to Yes in shorewall.conf(5).The option is included for compatibility
with Shorewall 4.6 and is equivalent to specifying the
option.For a description of the other options, see the check command above.version
[-]Displays Shorewall6's version. If the
option is included, the version of Shorewall will also be
displayed.EXIT STATUSIn general, when a command succeeds, status 0 is returned; when the
command fails, a non-zero status is returned.The status command returns exit status as
follows:0 - Firewall is started.3 - Firewall is stopped or cleared4 - Unknown state; usually means that the firewall has never been
started.ENVIRONMENTTwo environmental variables are recognized by Shorewall6:SHOREWALL_INIT_SCRIPTWhen set to 1, causes Std out to be redirected to the file
specified in the STARTUP_LOG option in shorewall6.conf(5).SW_LOGGERTAGAdded in Shorewall 5.0.8. When set to a non-empty value, that
value is passed to the logger utility in its -t (--tag)
option.See ALSOhttp://www.shorewall.net/starting_and_stopping_shorewall.htmshorewall6-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-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)