Shorewall Installation and UpgradeTomEastep2005-11-232001-2005Thomas M. EastepPermission 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.This article applies to Shorewall 3.0 and
later. If you are installing or upgradeing to a version of Shorewall
earlier than Shorewall 3.0.0 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.Before upgrading, be sure to review the Upgrade Issues.Shorewall RPMs are signed. To avoid warnings such as the
followingwarning: shorewall-3.0.1-1.noarch.rpm: V3 DSA signature: NOKEY, key ID 6c562ac4download the Shorewall GPG
key and run this command:rpm --import shorewall.gpg.keyInstall using RPMTo 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 taylored 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 RPMrpm -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.Some SUSE users have encountered a problem whereby rpm reports
a conflict with kernel <= 2.2 even though a 2.4 kernel is
installed. If this happens, simply use the --nodeps option to
rpm.rpm -ivh --nodeps <shorewall rpm>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-2.2.x-1This 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 <shorewall rpm>Edit the configuration files
to match your configuration.YOU CAN NOT SIMPLY INSTALL
THE RPM AND ISSUE A shorewall start COMMAND. SOME
CONFIGURATION IS REQUIRED BEFORE THE FIREWALL WILL START. IF YOU
ISSUE A start COMMAND AND THE FIREWALL FAILS TO
START, YOUR SYSTEM WILL NO LONGER ACCEPT ANY NETWORK TRAFFIC. IF
THIS HAPPENS, ISSUE A shorewall clear COMMAND TO
RESTORE NETWORK CONNECTIVITY.Enable startup by removing
/etc/shorewall/startup_disabled (If you are
running Shorewall 2.1.3 or later, edit
/etc/shorewall/shorewall.conf and set
STARTUP_ENABLED to Yes).Start the firewall by typingshorewall startInstall using tarballTo install Shorewall using the tarball and install script:unpack the tarball (tar -zxf shorewall-x.y.z.tgz).cd to the shorewall directory (the version is encoded in the
directory name as in shorewall-3.0.0).Type:./install.shEdit the configuration files
to match your configuration.Enable Startup by editing
/etc/shorewall/shorewall.conf and set
STARTUP_ENABLED=Yes.Start the firewall by typingshorewall startIf the install script was unable to configure Shorewall to be
started automatically at boot, see these
instructions.Install the .lrpTo install my version of Shorewall on a fresh Bering disk, simply
replace the shorwall.lrp file on the image with the file
that you downloaded. For example, if you download
shorewall-lrp-2.2.0.tgz then you will rename the file
to shorwall.lrp and replace the file by that name on
the Bering disk with the new file. Then proceed to configure Shorewall as
described in the Bering (or Bering uClibc) documentation.Install the .debOnce you have installed the .deb package and before you attempt to
configure Shorewall, please heed the advice of Lorenzo Martignoni, the
Shorewall Debian Maintainer:For more information about Shorewall usage on Debian system
please look at /usr/share/doc/shorewall/README.Debian provided by [the]
shorewall Debian package.The easiest way to install Shorewall on Debian, is to use
apt-get:apt-get install shorewallTo ensure that you are installing the latest version of Shorewall,
please modify your /etc/apt/sources.list file as
described here.Once you have completed configuring Shorewall,
you can enable startup at boot time by setting startup=1 in
/etc/default/shorewall.General Notes about Upgrading ShorewallMost 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.conffile 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 comments and 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.Upgrade using RPMIf 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 taylored 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.Upgrade the RPMrpm -Uvh <shorewall rpm file>Some SUSE users have encountered a problem whereby rpm reports
a conflict with kernel <= 2.2 even though a 2.4 kernel is
installed. If this happens, simply use the --nodeps option to
rpm.rpm -Uvh --nodeps <shorewall rpm>Beginning with Shorewall 1.4.0, 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-1.4.0-1This 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 restartUpgrade using tarballIf you already have Shorewall installed and are upgrading to a new
version using the tarball:unpack the tarball.tar -zxf shorewall-x.y.z.tgzcd to the shorewall directory (the version is encoded in the
directory name as in shorewall-3.0.1).Type:./install.shSee if there are any incompatibilities between your
configuration and the new Shorewall version and correct as
necessary.shorewall checkStart the firewall by typingshorewall startIf the install script was unable to configure Shorewall to be
started automatically at boot, see these
instructions.Upgrade the .lrpThe following was contributed by Charles Steinkuehler on the Leaf
mailing list:
It's *VERY* simple...just put in a new CD and reboot! :-)
Actually, I'm only slightly kidding...that's exactly how I upgrade my
prodution firewalls. The partial backup feature I added to
Dachstein allows configuration data to be stored seperately from the
rest of the package.Once the config data is seperated from the rest of the package,
it's an easy matter to upgrade the pacakge while keeping your current
configuration (in my case, just inserting a new CD and
re-booting).Users who aren't running with multiple package paths and using
partial backups can still upgrade a package, it just takes a bit of
extra work. The general idea is to use a partial backup to save
your configuration, replace the package, and restore your old
configuration files. Step-by-step instructions for one way to do this
(assuming a conventional single-floppy LEAF system) would be:Make a backup copy of your firewall disk ('NEW'). This
is the disk you will add the upgraded package(s) to.Format a floppy to use as a temporary location for your
configuration file(s) ('XFER'). This disk should have the same
format as your firewall disk (and could simply be another backup
copy of your current firewall).Make sure you have a working copy of your existing firewall
('OLD') in a safe place, that you *DO NOT* use durring this process.
That way, if anything goes wrong you can simply reboot off the OLD
disk to get back to a working configuration.Remove your current firewall configuration disk and replace it
with the XFER disk.Use the lrcfg backup menu to make a partial backup of the
package(s) you want to upgrade, being sure to backup the files to
the XFER disk. From the backup menu:t e <enter> p <enter>
b <package1> <enter>
b <package2> <enter>
...Download and copy the package(s) you want to upgrade onto the
NEW disk.Reboot your firewall using the NEW disk...at this point your
upgraded packages will have their default configuration.Mount the XFER disk (mount -t msdos /dev/fd0u1680 /mnt)CD to the root directory (cd /)Manually extract configuration data for each package you
upgraded:tar -xzvf /mnt/package1.lrp
tar -xzvf /mnt/package2.lrp
...Unmount (umount /mnt) and remove the XFER diskUsing lrcfg, do *FULL* backups of your upgraded
packages.Reboot, verifying the firewall works as expected. Some
configuration files may need to be 'tweaked' to work properly with
the upgraded package binaries.The new package file <package>.local can be used to
fine-tune which files are included (and excluded) from the partial
backup (see the Dachstein-CD README for details). If this file
doesn't exist, the backup scripts assume anything from the
<package>.list file that resides in /etc or /var/lib/lrpkg is
part of the configuration data and is used to create the partial
backup. If shorewall puts anything in /etc that isn't a user
modified configuration file, a proper shorwall.local file should be
created prior to making the partial backup [Editor's note: Shorewall places only
user-modifiable files in /etc].It's obviously possible to do the above 'in-place', without
using multiple disks, and even without making a partial backup (ie:
copy current config files to /tmp, manually extract new package on top
of current running firewall, then copy or merge config data from /tmp
and backup...or similar), but anyone capable of that level of command
line gymnastics is probably doing it already, without needing detailed
instructions! :-)
For information on other LEAF/Bering upgrade tools, check out this
article by Alex Rhomberg.Configuring ShorewallYou 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.Uninstall/FallbackSee Fallback and
Uninstall.