Copyright © 2001-, 2006, 2009 Thomas M. Eastep
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
2010/02/27
Table of Contents
This article applies to Shorewall 4.3 and later. If you are installing or upgrading to a version of Shorewall earlier than Shorewall 4.3.5 then please see the documentation for that release.
Before attempting installation, I strongly urge you to read and print a copy of the Shorewall QuickStart Guide for the configuration that most closely matches your own. This article only tells you how to install the product on your system. The QuickStart Guides describe how to configure the product.
Before upgrading, be sure to review the Upgrade Issues.
Shorewall RPMs are signed. To avoid warnings such as the following
warning: shorewall-3.2.1-1.noarch.rpm: V3 DSA signature: NOKEY, key ID 6c562ac4
download the Shorewall GPG key and run this command:
rpm --import shorewall.gpg.keyTo install Shorewall using the RPM:
Be sure that you have the correct RPM package!
The standard RPM package from shorewall.net and the mirrors is known to work with SUSE™, Power PPC™, Trustix™ and TurboLinux™. There is also an RPM package provided by Simon Matter that is tailored for RedHat/Fedora™ and another package from Jack Coates that is customized for Mandriva™. All of these are available from the download page.
If you try to install the wrong package, it probably won't work.
Install the RPMs
rpm -ivh <shorewall rpm>Some users are in the habit of using the rpm -U command for installing packages as well as for updating them. If you use that command when installing the Shorewall RPM then you will have to manually enable Shorewall startup at boot time by running chkconfig, insserv or whatever utility you use to manipulate you init symbolic links.
Shorewall is dependent on the iproute package. Unfortunately, some distributions call this package iproute2 which will cause the installation of Shorewall to fail with the diagnostic:
error: failed dependencies:iproute is needed by shorewall-3.2.x-1
This problem should not occur if you are using the correct RPM package (see 1., above) but may be worked around by using the --nodeps option of rpm.
rpm -ivh --nodeps <rpms>Example:
rpm -ivh shorewall-4.3.5-0base.noarch.rpmTo install Shorewall using the tarball and install script:
unpack the tarballs:
tar -jxf shorewall-4.3.5.tar.bz2cd to the shorewall directory (the version is encoded in the directory name as in “shorewall-4.3.5”).
Type:
./install.sh or if you are installing Shorewall or Shorewall6 version 4.4.8 or later, you may type:
./install.sh -sThe -s option supresses
installation of all files in /etc/shorewall except
shorewall.conf. You can copy any other files you
need from one of the Samples
or from /usr/share/shorewall/configfiles/.
If the install script was unable to configure Shorewall to be started automatically at boot, see these instructions.
Once you have installed the .deb packages and before you attempt to configure Shorewall, please heed the advice of Lorenzo Martignoni, former Shorewall Debian Maintainer:
“For more information about Shorewall usage on Debian system please look at /usr/share/doc/shorewall-common/README.Debian provided by [the] shorewall-common Debian package.”
The easiest way to install Shorewall on Debian, is to use apt-get.
First, to ensure that you are installing the latest version of
Shorewall, please modify your
/etc/apt/preferences:
Package: shorewall Pin: release o=Debian,a=testing Pin-Priority: 700 Package: shorewall-doc Pin: release o=Debian,a=testing Pin-Priority: 700
Then run:
# apt-get update # apt-get install shorewall
Once you have completed configuring
Shorewall, you can enable startup at boot time by setting startup=1 in
/etc/default/shorewall.
Most problems associated with upgrades come from two causes:
The user didn't read and follow the migration considerations in the release notes (these are also reproduced in the Shorewall Upgrade Issues).
The user mis-handled the
/etc/shorewall/shorewall.conf file during
upgrade. Shorewall is designed to allow the default behavior of the
product to evolve over time. To make this possible, the design assumes
that you will not replace your current
shorewall.conf file during
upgrades. It is recommended that after you first install
Shorewall that you modify
/etc/shorewall/shorewall.conf so as to prevent
your package manager from overwriting it during subsequent upgrades
(since the addition of STARTUP_ENABLED, such modification is assured
since you must manually change the setting of that option). If you
feel absolutely compelled to have the latest options in your
shorewall.conf then you must proceed carefully. You should determine
which new options have been added and you must reset their value (e.g.
OPTION=""); otherwise, you will get different behavior from what you
expect.
If you already have the Shorewall RPM installed and are upgrading to a new version:
Be sure that you have the correct RPM package!
The standard RPM package from shorewall.net and the mirrors is known to work with SUSE™, Power PPC, Trustix and TurboLinux. There is also an RPM package provided by Simon Matter that is tailored for RedHat/Fedora and another package from Jack Coates that is customized for Mandriva. If you try to upgrade using the wrong package, it probably won't work.
Simon Matter names his 'common' rpm 'shorewall' rather than 'shorewall-common'.
If you are upgrading from a 2.x or 3.x version to a 4.x version or later, please see the upgrade issues for specific instructions.
Upgrade the RPM
rpm -Uvh <shorewall rpm file> Shorewall is dependent on the iproute package. Unfortunately, some distributions call this package iproute2 which will cause the upgrade of Shorewall to fail with the diagnostic:
error: failed dependencies:iproute is needed by shorewall-3.2.1-1
This may be worked around by using the --nodeps option of rpm.
rpm -Uvh --nodeps <shorewall rpm> ...See if there are any incompatibilities between your configuration and the new Shorewall version and correct as necessary.
shorewall checkRestart the firewall.
shorewall restartIf you are upgrading from a 2.x or 3.x version to a 4.x version or later, please see the upgrade issues for specific instructions.
If you already have Shorewall installed and are upgrading to a new version using the tarball:
unpack the tarball:
tar -jxf shorewall-4.3.5.tar.bz2cd to the shorewall-perl directory (the version is encoded in the directory name as in “shorewall-4.3.5”).
Type:
./install.shor if you are installing Shorewall or Shorewall6 version 4.4.8 or later, you may type:
./install.sh -sThe -s option supresses
installation of all files in /etc/shorewall except
shorewall.conf. You can copy any other files you
need from one of the Samples
or from /usr/share/shorewall/configfiles/.
See if there are any incompatibilities between your configuration and the new Shorewall version and correct as necessary.
shorewall checkStart the firewall by typing
shorewall startIf the install script was unable to configure Shorewall to be started automatically at boot, see these instructions.
When the installer asks if you want to replace /etc/shorewall/shorewall.conf with the new version, we strongly advise you to say No. See above.
You will need to edit some or all of the configuration files to match your setup. In most cases, the Shorewall QuickStart Guides contain all of the information you need.
See “Fallback and Uninstall”.