Seattle Firewall (Seawall)

This is an Open Source Software project with no ties to Seawall, Incorporated.

This site is hosted by SourceForge Logo

 


 

What is it?

The Seattle firewall is an ipchains based firewall that can be used on a dedicated masquerading firewall machine (including LRP), a multi-function masquerade gateway/server or on a standalone Linux system.

What features does it provide?

Will it work with my Linux distribution?

I have personally used Seattle Firewall with RedHat 6.0, 6.1 and 6.2, Caldera 2.4, TurboLinux 6.0, SuSE 6.2, Slackware 7.0, Mandrake 7.0 and with LRP. The only real requirements are that you have a Bourne shell and that your kernel supports ipchains.

Where can I get it?

I strongly urge you to read and print a copy of the Seattle Firewall Documentation. Once you've done that go to the Seattle Firewall project page at Sourceforge to download one of the modules:

Now that I've got it, how do I install and configure it?

If you haven't done so already, please read and print a copy of the Seattle Firewall Documentation.

If you have an older version of Seattle Firewall installed, see the Upgrade Instructions below.

If you downloaded the rpm version, install the RPM. If yours is a standalone system with either a dynamic or static IP address on a single ethernet adapter, the seawall.conf, apps, servers and tunnels files distributed with 3.1 and later versions of Seattle Firewall may be installed "as is" and then modified as your needs become clearer.

With versions 3.0 and later, to install Seattle Firewall using the tarball and install script:

How do I customize it?

Most firewall parameters can be set by editing the file /etc/seawall.conf and by modifying the files /etc/seawall/apps and /etc/seawall/servers. For customization beyond what is provided by editing these files, additional rules can be defined in other files in the /etc/seawall directory.

Upgrading

NOTE: If you already have Seattle Firewall installed and you want to begin using the RPM version, it is a good idea to first upgrade to the current version using the install script THEN install the RPM. By doing so, you preserve the option to fall back to your current version of Seattle Firewall using the the fallback script. Subsequent upgrades may be done with just the rpm since you can always use RPM to fall back to your previous version.

I have Seattle Firewall 2.x -- How do I upgrade to the latest Version?

I have Seattle Firewall 3.x -- How do I upgrade to the latest Version?

I upgraded to your latest version and it doesn't work for me -- how can I fall back to my previously installed version?

If a version of Seattle Firewall 3.1 or later doesn't work for you and you installed the version using "install.sh", you can fall back to the version you were previously running using the fallback script.

Where do I get Help or Report Bugs?

There's a mailing list at seawall-user@lists.sourceforge.net (the author regularly monitors this list).


Updated 6/2/2000 - Tom Eastep