The interface argument names an interface defined in the shorewall6-interfaces[3](5) file. A host-list is comma-separated list whose elements are host or network addresses..if n .sp

Beginning with Shorewall 4.5.9, the dynamic_shared zone option (shorewall6-zones[4](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.

If the disconnect option is specified in the DYNAMIC_BLACKLISTING setting, then the effective VERBOSITY determines the amount of information displayed:

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.

The -e 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 -d option causes the compiler to be run under control of the Perl debugger.

The -p option causes the compiler to be profiled via the Perl -wd:DProf command-line option.

The -r option was added in Shorewall 4.5.2 and causes the compiler to print the generated ruleset to standard out.

The -T 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 -i 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)[2].

When the second form of the command is used, the parameters must match those given in the earlier open command.

When -e 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 -e 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 -c 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 -d option causes the compiler to be run under control of the Perl debugger.

The -p option causes the compiler to be profiled via the Perl -wd:DProf command-line option.

The -T 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 -i 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)[2].

The interface argument names an interface defined in the shorewall6-interfaces[3](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[4](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.

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](5) and any traffic shaping configuration for the interface.

The -x option causes actual packet and byte counts to be displayed. Without that option, these counts are abbreviated.

The -m option causes any MAC addresses included in Shorewall6 log messages to be displayed.

The -l option causes the rule number for each Netfilter rule to be displayed.

The -c option causes the route cache to be dumped in addition to the other routing information.

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](5) and installs the interface's traffic shaping configuration, if any.

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 -e directory1 directory1/firewall &&\
    scp directory1/firewall directory1/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.

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[6].

The iptables match expression must be one given in the iptrace command being canceled.

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 22

To reverse that command, use:

    shorewall6 close all 2001:470:b:227::1 tcp 22

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 -n option was added in Shorewall 4.5.3 causes Shorewall to avoid updating the routing table(s).

The -d option was added in Shorewall 4.5.3 causes the compiler to run under the Perl debugger.

The -T 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 -i 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[2](5).

The -D option was added in Shorewall 4.5.3 and causes Shorewall to look in the given directory first for configuration files.

Example 1. Refresh the 'net-fw' chain in the filter table and the 'net_dnat' chain in the nat table

shorewall6 refresh net-fw nat:net_dnat
            

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 -n option causes Shorewall6 to avoid updating the routing table(s).

The -p option causes the connection tracking table to be flushed; the conntrack utility must be installed to use this option.

The -d option causes the compiler to run under the Perl debugger.

The -f 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 -c option was added in Shorewall 4.4.20 and performs the compilation step unconditionally, overriding the AUTOMAKE setting in shorewall6.conf[2](5). When both -f and -c are present, the result is determined by the option that appears last.

The -T 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 -i 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[2](5).

The -C option was added in Shorewall 4.6.5 and is only meaningful when AUTOMAKE=Yes in shorewall6.conf[2](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.

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 -e directory directory/firewall &&\
    scp directory/firewall directory/firewall.conf root@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. Beginning with Shorewall 5.0.13, if system is omitted, then the FIREWALL option setting in shorewall6.conf(5)[7] is assumed. In that case, if you want to specify a directory, then the -D option must be given.

If -s is specified and the restart command succeeds, then the remote Shorewall6-lite configuration is saved by executing shorewall6-lite save via ssh.

if -c 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 -r is included, it specifies that the root user on system is named root-user-name rather than "root".

The -T 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 -i 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[2](5).

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 -e directory directory/firewall &&\
    scp directory/firewall directory/firewall.conf root@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.

Beginning with Shorewall 5.0.13, if system is omitted, then the FIREWALL option setting in shorewall6.conf(5)[7] is assumed. In that case, if you want to specify a directory, then the -D option must be given.

If -s is specified and the restart command succeeds, then the remote Shorewall6-lite configuration is saved by executing shorewall6-lite save via ssh.

if -c 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 -r is included, it specifies that the root user on system is named root-user-name rather than "root".

The -T 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 -i 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[2](5).

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 -e directory directory/firewall &&\
    scp directory/firewall directory/firewall.conf root@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. Beginning with Shorewall 5.0.13, if system is omitted, then the FIREWALL option setting in shorewall6.conf(5)[7] is assumed. In that case, if you want to specify a directory, then the -D option must be given.

If -s is specified and the start command succeeds, then the remote Shorewall6-lite configuration is saved by executing shorewall6-lite save via ssh.

if -c 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 -r is included, it specifies that the root user on system is named root-user-name rather than "root".

The -T 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 -i 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[2](5).

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.

If a directory is included in the command, Shorewall6 will look in that directory first for configuration files.

The -n option causes Shorewall6 to avoid updating the routing table(s).

The -p option causes the connection tracking table to be flushed; the conntrack utility must be installed to use this option.

The -d option causes the compiler to run under the Perl debugger.

The -f 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 -c option was added in Shorewall 4.4.20 and performs the compilation step unconditionally, overriding the AUTOMAKE setting in shorewall6.conf[2](5). When both -f and -c are present, the result is determined by the option that appears last.

The -T 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 -i 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[2](5).

The -C option was added in Shorewall 4.6.5 and is only meaningful when AUTOMAKE=Yes in shorewall6.conf[2](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.

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
          date

Beginning with Shorewall 4.5.0, you may specify a different timeout value using the -t option. The numeric timeout may optionally be followed by an s, m or h suffix (e.g., 5m) to specify seconds, minutes or hours respectively. If the suffix is omitted, seconds is assumed.

Beginning with Shorewall 4.5.0, you may specify a different timeout value using the -t option. The numeric timeout may optionally be followed by an s, m or h suffix (e.g., 5m) to specify seconds, minutes or hours respectively. If the suffix is omitted, seconds is assumed.

The -C option, added in Shorewall 4.6.5, causes the ip6tables packet and byte counters to be saved along with the chains and rules.

actions

[-x] bl|blacklists

[-f] capabilities

[-b] [-x] [-l] [-t {filter|mangle|nat|raw|rawpost}][ chain... ]

classifiers|filters

config

connections [filter_parameter ...]

event event

events

ip

[-m] log

macros

macro macro

[-x] mangle

marks

[-x] nat

opens

policies

[-x] raw

[-c] routing

tc

zones

Update: In Shorewall6 4.4.20, a new LEGACY_FASTSTART option was added to shorewall6.conf[2](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 -n option causes Shorewall6 to avoid updating the routing table(s).

The -c option was added in Shorewall 4.4.20 and performs the compilation step unconditionally, overriding the AUTOMAKE setting in shorewall6.conf[2](5). When both -f and -c are present, the result is determined by the option that appears last.

The -T 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 -i 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[2](5).

The -C option was added in Shorewall 4.6.5 and is only meaningful when the -f option is also specified. If the previously-saved configuration is restored, and if the -C option was also specified in the save command, then the packet and byte counters will be restored along with the chains and rules.

If -f 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.

The -i option was added in Shorewall 4.6.2 and causes the status of each optional or provider interface to be displayed.

Beginning with Shorewall 4.5.0, the numeric timeout may optionally be followed by an s, m or h suffix (e.g., 5m) to specify seconds, minutes or hours respectively. If the suffix is omitted, seconds is assumed.

The command was extended over the years with a set of options that caused additional configuration updates.

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.

 WARNING: "Omitted rules and compiler directives were not translated

The -i 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[9](5).

The -A option is included for compatibility with Shorewall 4.6 and is equivalent to specifying the -i option.

For a description of the other options, see the check command above.