Shorewall Installation and Upgrade Tom Eastep 2004-10-27 2001 2002 2003 2004 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. Note to Debian Users If you install using the .deb, you will find that your /etc/shorewall directory is empty. This is intentional. The released configuration file skeletons may be found on your system in the directory /usr/share/doc/shorewall/default-config. Simply copy the files you need from that directory to /etc/shorewall and modify the copies. Note that you must copy /usr/share/doc/shorewall/default-config/shorewall.conf and /usr/share/doc/shorewall/default-config/modules to /etc/shorewall even if you do not modify those files.
Install using RPM 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. To install Shorewall using the RPM: Install the RPM rpm -ivh <shorewall rpm> 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> Beginning with Shorewall 1.4.0, 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-1.4.x-1 This 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 typing shorewall start
Install using tarball 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. To 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-1.1.10). If you are running Slackware, you need Shorewall 2.0.2 RC1 or later. If you are installing a Shorewall version earlier than 2.0.3 Beta 1 then you must also edit the install.sh file and change the lines DEST="/etc/init.d" INIT="shorewall" to DEST="/etc/rc.d" INIT="rc.firewall" If you are running Slackware and are installing Shorewall 2.0.3 Beta 1 or later, then type: DEST=/etc/rc.d INIT=rc.firewall ./install.sh Otherwise, type: ./install.sh Edit the configuration files to match your configuration. Enable Startup: Users running Shorewall 2.1.3 or later, edit /etc/shorewall/shorewall.conf and set STARTUP_ENABLED=Yes. Users running Shorewall 2.1.2 or earlier and using the .deb should edit /etc/default/shorewall and set startup=1. All other users, remove the file /etc/shorewall/startup_disabled Start the firewall by typing shorewall start If the install script was unable to configure Shorewall to be started automatically at boot, see these instructions.
Install the .lrp 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. To 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. See the two-interface QuickStart Guide for information about further steps required.
Upgrade using RPM Before upgrading, be sure to review the Upgrade Issues. If you already have the Shorewall RPM installed and are upgrading to a new version: If you are upgrading from a 1.2 version of Shorewall to a 1.4 version or and you have entries in the /etc/shorewall/hosts file then please check your /etc/shorewall/interfaces file to be sure that it contains an entry for each interface mentioned in the hosts file. Also, there are certain 1.2 rule forms that are no longer supported under 1.4 (you must use the new 1.4 syntax). See the upgrade issues for details. Upgrade the RPM rpm -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-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 check Restart the firewall. shorewall restart
Upgrade using tarball Before upgrading, be sure to review the Upgrade Issues. If you already have Shorewall installed and are upgrading to a new version using the tarball: If you are upgrading from a 1.2 version of Shorewall to a 1.4 version and you have entries in the /etc/shorewall/hosts file then please check your /etc/shorewall/interfaces file to be sure that it contains an entry for each interface mentioned in the hosts file. Also, there are certain 1.2 rule forms that are no longer supported under 1.4 (you must use the new 1.4 syntax). See the upgrade issues for details. 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.1). If you are running Slackware, you should use Shorewall 2.0.2 RC1 or later. If you are installing a Shorewall version earlier than 2.0.3 Beta 1 then you must also edit the install.sh file and change the lines DEST="/etc/init.d" INIT="shorewall" to DEST="/etc/rc.d" INIT="rc.firewall" If you are running Slackware and are installing Shorewall 2.0.3 Beta 1 or later, then type: DEST=/etc/rc.d INIT=rc.firewall ./install.sh Otherwise, type: ./install.sh See if there are any incompatibilities between your configuration and the new Shorewall version and correct as necessary. shorewall check Start the firewall by typing shorewall start If the install script was unable to configure Shorewall to be started automatically at boot, see these instructions.
Upgrade the .lrp Before upgrading, be sure to review the Upgrade Issues. The 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 disk Using 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! :-)
Configuring Shorewall 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.
Uninstall/Fallback See Fallback and Uninstall.