shorewall8shorewallAdministration tool for Shoreline Firewall
(Shorewall)shorewall-optionsaddinterface[:host-list]zoneshorewall-optionsallowaddressshorewall-optionscheckdirectoryshorewall-optionsclearshorewall-optionscompiledirectorypathnameshorewall-optionsdeleteinterface[:host-list]zoneshorewall-optionsdropaddressshorewall-optionsdumpshorewall-optionsexportdirectory1[user@]system:[directory2]shorewall-optionsforgetfilenameshorewall-optionshelpcommandshorewall-optionshitsshorewall-optionsipcalcaddress maskaddress/vlsmshorewall-optionsiprangeaddress1-address2shorewall-optionsloaddirectorysystemshorewall-optionslogdropaddressshorewall-optionslogwatchrefresh-intervalshorewall-optionslogrejectaddressshorewall-optionsrefreshshorewall-optionsrejectaddressshorewall-optionsreloaddirectorysystemshorewall-optionsrestartdirectoryshorewall-optionsrestorefilenameshorewall-optionssafe-restartshorewall-optionssafe-startshorewall-optionssavefilenameshorewall-optionsshowchainshorewall-optionsshowcapabilitiesshorewall-optionsshowshorewall-optionsshowshorewall-optionsshowlogshorewall-optionsstartdirectoryshorewall-optionsstopshorewall-optionsstatusshorewall-optionstrydirectorytimeoutshorewall-optionsversionDescriptionThe shorewall utility is used to control the Shoreline Firewall
(Shorewall).OptionsThe 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 shorewall.conf(5). Each v adds one to the effective verbosity and each
q subtracts one from the effective
VERBOSITY.CommandsThe available commands are listed below.addAdds a list of hosts or subnets to a dynamic zone usually used
with VPN's.The interface argument names an interface
defined in the shorewall-interfaces(5) file. A
host-list is comma-separated list whose
elements are: A host or network address
The name of a bridge port
The name of a bridge port followed by a colon (:) and a host or network addressallowRe-enables receipt of packets from hosts previously
blacklisted by a drop, logdrop, reject, or logreject command.checkCompiles the configuraton in the specified
directory and discards the compiled output
script. If no directory is given, then
/etc/shorewall is assumed.The -e option causes the
compiler to look for a file named capabilities. This file is
produced using the command shorewall-lite show
-f capabilities > capabities on a system with
Shorewall Lite installed.clearClear will remove all rules and chains installed by Shorewall.
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.compileCompiles the current configuration into the executable file
pathname. If a directory is supplied, Shorewall
will look in that directory first for configuration files.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 presense
of a configuration file named capabilities which may be produced
using the command shorewall-lite show -f
capabilities > capabities on a system with Shorewall
Lite installeddeleteThe delete command reverses the effect of an earlier add command.dropCauses traffic from the listed addresses
to be silently dropped.dumpProduces 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 Shorewall log messages
to be displayed.exportIf directory1 is omitted, the current
working directory is assumed. Allows a non-root user to compile a shorewall script and stage
it on a system (provided that the user has access to the system via
ssh). The command is equivalent to:/sbin/shorewall 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.forgetDeletes /var/lib/shorewall/filename and
/var/lib/shorewall/save. If no filename is
given then the file specified by RESTOREFILE in shorewall.conf(5) is
assumed.helpDisplays information about a particular
command. If no command is
given, a syntax summary is displayed.hitsGenerates several reports from Shorewall log messages in the
current log file.ipcalcIpcalc displays the network address, broadcast address,
network in CIDR notation and netmask corresponding to the
input[s].iprangeIprange decomposes the specified range of IP addresses into
the equivalent list of network/host addresses.loadIf directory is omitted, the current
working directory is assumed. Allows a non-root user to compile a
shorewall 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/shorewall compile -edirectorydirectory/firewall &&\scpdirectory/firewalldirectory/firewall.confroot@system:/var/lib/shorewall-lite/ &&\ssh root@system'/sbin/shorewall-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,
Shorewall Lite on system is started via
ssh.If -s is specified and the
start command succeeds, then the
remote Shorewall-lite configuration is saved by executing shorewall-lite save via ssh.if -c is included, the
command shorewall-lite show capabilities -f
> /var/lib/shorewall-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.logdropCauses traffic from the listed addresses
to be logged then discarded.logwatchMonitors the log file specified by theLOGFILE option in
shorewall.conf(5) and produces an audible alarm when new Shorewall
messages are logged. The -m option
causes the MAC address of each packet source to be displayed if that
information is available.logrejectCauses traffic from the listed addresses
to be logged then rejected.refreshThe rules involving the the black list, ECN control rules, and
traffic shaping are recreated to reflect any changes made to your
configuration files. Existing connections are untouched.reloadIf directory is omitted, the current
working directory is assumed. Allows a non-root user to compile a
shorewall 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/shorewall compile -edirectorydirectory/firewall &&\scpdirectory/firewalldirectory/firewall.confroot@system:/var/lib/shorewall-lite/ &&\ssh root@system'/sbin/shorewall-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,
Shorewall Lite on system is restarted via
ssh.If -s is specified and the
restart command succeeds, then the
remote Shorewall-lite configuration is saved by executing shorewall-lite save via ssh.if -c is included, the
command shorewall-lite show capabilities -f
> /var/lib/shorewall-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.resetAll the packet and byte counters in the firewall are
reset.restartRestart is similar to shorewall
stop followed by shorewall
start. Existing connections are maintained. If a
directory is included in the command, Shorewall
will look in that directory first for
configuration files.restoreRestore Shorewall to a state saved using the shorewall save command. Existing connections
are maintained. The filename names a restore
file in /var/lib/shorewall created using shorewall save; if no
filename is given then Shorewall will be
restored from the file specified by the RESTOREFILE option in
shorewall.conf(5).safe-restartOnly allowed if Shorewall is running. The current
configuration is saved in /var/lib/shorewall/safe-restart (see the
save command below) then a shorewall
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.safe-startShorewall 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
shorewall clear is performed for you.saveThe dynamic blacklist is stored in /var/lib/shorewall/save.
The state of the firewall is stored in
/var/lib/shorewall/filename for use by the
shorewall restore and shorewall -f start commands. If
filename is not given then the state is saved
in the file specified by the RESTOREFILE option in
shorewall.conf(5).showThe show command can have a number of different
arguments:[ chain ] ...Using the iptables -Lchain-n
-v command, the rules in each
chain are displayed. If no
chain is given, all of the chains in the
filter table are displayed. The -x option is passed directly through to
iptables.capabilitiesDisplays your kernel/iptables capabilities. The
-f option causes the display
to be formatted as a capabilities file for use with compile -e.connectionsDisplays the IP connections currently being tracked by
the firewall.FILES/etc/shorewall/See ALSOshorewall-accounting(5), shorewall-actions(5),
shorewall-blacklist(5), shorewall-hosts(5), shorewall-interfaces(5),
shorewall-ipsec(5), shorewall-maclist(5), shorewall-masq(5),
shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5),
shorewall-route_rules(5), shorewall-routestopped(5), shorewall-rules(5),
shorewall.conf(5), shorewall-tcclasses(5), shorewall-tcdevices(5),
shorewall-tcrules(5), shorewall-tos(5), shorewall-tunnels(5),
shorewall-zones(5)