Shorewall Version 4
Tom
Eastep
2007
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
.
Introduction
Shorewall version 4 is currently in development and is available for
beta testing.
Shorewall version 4 represents a substantial shift in direction for
Shorewall. Up to now
Shorewall has been written entirely in Bourne Shell.
Shorewall has run the iptables utility to add
each Netfilter rule.
Shorewall version 4 offers you a choice. You can continue to use the
existing shell-based implementation or you can use a new implementation of
the Shorewall compiler written in the Perl programming language. The new
compiler:
has a small disk footprint
is very fast.
generates a firewall script that uses
iptables-restore; so the script is very
fast.
generates better and more consistent error messages.
does a much more thorough job of checking the configuration to
avoid run-time errors.
Both compilers may be installed on your system and you can use
whichever one suits you in a particular case.
Installing Shorewall Version 4
You can download the development version of Shorewall Version 4 from
any of the download sites with the exception of SourceForge. It is
contained in the /pub/shorewall/development/4.0
directory.
Shorewall 4 contains four packages:
Shorewall-shell - the old shell-based compiler and related
components.
Shorewall-perl - the new Perl-based compiler. May be installed
under Shorewall 3.4.2 or later or 4.0.x.
Shorewall - the part of Shorewall common to both
compilers.
Shorewall-lite- same as the 3.4 version of Shorewall Lite. Can
run scripts generated by either Shorewall-perl or
Shorewall-shell.
If you upgrade to Shorewall Version 4, you must install
Shorewall-shell and/or Shorewall-perl; in fact, if you are using the
tarball for your installation, you must install Shorewall-shell and/or
Shorewall-perl before you upgrade
Shorewall.
Prerequisites for using the Shorewall Version 4 Perl-based
Compiler
Perl (I use Perl 5.8.8 but other versions should work
fine)
Perl Cwd Module
Perl File::Basename Module
Perl File::Temp Module
Perl Getopt::Long Module
Perl Carp Module
Incompatibilities Introduced in the Shorewall Version 4 Perl-based
Compiler
The Shorewall-perl compiler is not 100% compatible with the
Shorewall-shell version. See this
document for details.
Compiler Selection
If you only install one compiler, then that compiler will be
used.
If you install both compilers, then the compiler actually used
depends on the SHOREWALL_COMPILER setting in
shorewall.conf.
The value of this new option can be either 'perl' or 'shell'.
If you add 'SHOREWALL_COMPILER=perl' to
/etc/shorewall/shorewall.conf then by default, the
new compiler will be used on the system. If you add it to
shorewall.conf in a separate directory (such as a
Shorewall-lite export directory) then the new compiler will only be used
when you compile from that directory.
If you only install one compiler, it is suggested that you do not
set SHOREWALL_COMPILER.
You can select the compiler to use on the command line using the 'C
option:
'-C shell' means use the shell compiler
'-C perl' means use the perl compiler
The -C option overrides the setting in
shorewall.conf.
Example:shorewall restart -C perlRegardless
of the setting of SHOREWALL_COMPILER, there is one change in Shorewall
operation that is triggered simply by installing shorewall-perl. Your
params file will be processed during compilation with the shell's '-a'
option which causes any variables that you set or create in that file to
be automatically exported. Since the params file is processed before
shorewall.conf, using -a insures that the settings of your params
variables are available to the new compiler should its use be specified in
shorewall.conf.