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

Re-enables receipt of packets from hosts previously blacklisted by a drop, logdrop, reject, or logreject command.

Compiles the configuration in the specified directory and discards the compiled output script. If no directory is given, then /etc/shorewall6 is assumed. 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 line 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].

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.

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 -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 line 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].

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

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

Causes traffic from the listed addresses to be silently dropped.

Produces a verbose report about the firewall configuration for the purpose of problem analysis. 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.

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

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: 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.

Deletes /var/lib/shorewall6/filename and /var/lib/shorewall6/save. If no filename is given then the file specified by RESTOREFILE in shorewall6.conf[2](5) is assumed.

Displays a syntax summary.

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

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: 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 -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 line 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).

Causes 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[2] (5).

Monitors the log file specified by the LOGFILE option in shorewall6.conf[2](5) and produces an audible alarm when new Shorewall6 messages are logged. The -m 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.

Causes 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[2] (5).

This 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.

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 -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 line 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:

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: 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 -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 line 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).

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.

Restart 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 line 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).

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

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:

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

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

The show command can have a number of different arguments: actions bl|blacklists capabilities [ [ chain ] chain... ] classifiers|filters config connections event event events ip log macros mangle marks policies Routing tc zones

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 -f is specified, the saved configuration specified by the RESTOREFILE option in shorewall6.conf[2](5) will be restored if that saved configuration exists and has been modified more recently than the files in /etc/shorewall6. When -f is given, a directory may not be specified. 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 line 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).

Stops the firewall. All existing connections, except those listed in shorewall6-routestopped[7](5) or permitted by the ADMINISABSENTMINDED option in shorewall6.conf[2](5), are taken down. The only new traffic permitted through the firewall is from systems listed in shorewall6-routestopped[7](5) or by ADMINISABSENTMINDED.

Produces a short report about the state of the Shorewall6-configured firewall. The -i option was added in Shorewall 4.6.2 and causes the status of each optional or provider interface to be displayed.

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 s, m or h suffix (e.g., 5m) to specify seconds, minutes or hours respectively. If the suffix is omitted, seconds is assumed.

Added in Shorewall 4.4.21 and causes the compiler to update /etc/shorewall6/shorewall6.conf then validate the configuration. The update will add options not present in the existing 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 shorewall6.conf file is renamed shorewall6.conf.bak. The -a option causes the updated shorewall6.conf file to be annotated with documentation. The -b option was added in Shorewall 4.4.26 and causes legacy blacklisting rules ( shorewall6-blacklist[8] (5) ) to be converted to entries in the blrules file ( shorewall6-blrules[9] (5) ). The blacklist keyword is removed from shorewall6-zones[4] (5), shorewall6-interfaces[3] (5) and shorewall6-hosts[10] (5). The unmodified files are saved with a .bak suffix. The -D option was added in Shorewall 4.5.11. When this option is specified, the compiler will walk through the directories in the CONFIG_PATH replacing FORMAT and COMMENT entries to compiler directives (e.g., ?FORMAT and ?COMMENT. When a file is updated, the original is saved in a .bak file in the same directory. The -i option was added in Shorewall 4.6.0 and causes a warning message to be issued if the line 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 -t option was added in Shorewall 4.6.0. When specified, -t causes shorewall6-tcrules(5)[11] to be converted to shorewall6-mangle(5)[12]. The old file is renamed with a .bak suffix. The -A option was added in Shorewall 4.6.0 and is equivalent to specifying the -b, -D and the -t options. For a description of the other options, see the check command above.

Displays Shorewall6's version. If the -a option is included, the version of Shorewall will also be displayed.