IMPORTANT
If you use a Windows system to download a corrected script, be sure to run the script through dos2unix after you have moved it to your Linux system.
When the instructions say to install a corrected firewall script in /etc/shorewall/firewall, use the 'cp' (or 'scp') utility to overwrite the existing file. DO NOT REMOVE OR RENAME THE OLD /etc/shorewall/firewall before you do that. /etc/shorewall/firewall is a symbolic link that points to the 'shorewall' file used by your system initialization scripts to start Shorewall during boot and it is that file that must be overwritten with the corrected script.
Some users have reported problems installing the RPM
on SuSE 7.3 where rpm reports a conflict with kernel <= 2.2 even
though a 2.4 kernel RPM is installed. To get around this problem, use
the --nodeps option to rpm (e.g., "rpm -ivh --nodeps
shorewall-1.2-13.noarch.rpm").
The problem stems from the fact that SuSE does not
include a package named "kernel" but rather has a number of packages
that provide the virtual package "kernel". Since virtual packages have
no version associated with them, a conflict results. Since the
workaround is simple, I don't intend to change the Shorewall package.
Shorewall accepts invalid rules of the form:
ACCEPT <src> <dest>:<ip addr> all <port number> -
<original ip address>
The <port number> is ignored with the result that all
connection requests from the <src> zone whose original destination IP
address matches the last column are forwarded to the <dest> zone, IP
address <ip addr>.
This corrected firewall script correctly generates an error when
such a rule is encountered.
The 'try' command is broken.
The usage text printed by the shorewall utility doesn't show the optional timeout for the 'try' command.
Both problems are corrected by this new version of /sbin/shorewall.
There have been several problems with SSH, DNS and ping in the two- and three-interface examples. Before reporting problems with these services, please verify that you have the latest version of the appropriate sample 'rules' file.
The documentation for running PoPToP on the firewall system contained an incorrect entry in the /etc/shorewall/hosts file. The corrected entry (underlined) is shown here:
ZONE HOST(S) OPTIONS loc eth2:192.168.1.0/24 routestopped loc ppp+:192.168.1.0/24
The shorewall.conf file and the documentation incorrectly refer to a parameter in /etc/shorewall/shorewall.conf called LOCKFILE; the correct name for the parameter is SUBSYSLOCK (see the corrected online documentation). Users of the rpm should change the name (and possibly the value) of this parameter so that Shorewall interacts properly with the SysV init scripts. The documentation on this web site has been corrected and here's a corrected version of shorewall.conf.
The documentation indicates that a comma-separated list of IP/subnet addresses may appear in an entry in the hosts file. This is not the case; if you want to specify multiple addresses for a zone, you need to have a separate entry for each address.
Version 1.2.7 is quite broken -- please install 1.2.8
If you have installed and started version 1.2.7 then before trying to restart under 1.2.8:
You may now restart using 1.2.8.
GRE and IPIP tunnels are broken.
The following rule results in a start error:
ACCEPT z1 z2
icmp
To correct the above problems, install this corrected firewall script in /etc/shorewall/firewall..
The new ADDRESS column in /etc/shorewall/masq cannot contain a $-variable name.
Errors result if $FW appears in the /etc/shorewall/policy file.
Using Blacklisting without setting BLACKLIST_LOGLEVEL results in an error at start time.
To correct the above problems, install this corrected firewall script in /etc/shorewall/firewall.
The /sbin/shorewall script produces error messages saying that 'mygrep' cannot be found. Here is the correct version of /sbin/shorewall.
This version will not install "out of the box" without modification. Before attempting to start the firewall, please change the STATEDIR in /etc/shorewall/shorewall.conf to refer to /var/lib/shorewall. This only applies to fresh installations -- if you are upgrading from a previous version of Shorewall, version 1.2.4 will work without modification.
When BLACKLIST_LOGLEVEL is set, packets from blacklisted hosts aren't logged. Install this corrected firewall script in /etc/shorewall/firewall.
Alternatively, edit /etc/shorewall/firewall and change line 1564 from:
run_iptables -A blacklst -d $addr -j LOG $LOGPARAMS --log-prefix \
to
run_iptables -A blacklst -s $addr -j LOG $LOGPARAMS --log-prefix \
status)
clear
to this:
status)
get_config
clear
Note: If you are upgrading from one of the Beta RPMs to 1.2.0, you must use the "--oldpackage" option to rpm (e.g., rpm -Uvh --oldpackage shorewall-1.2-0.noarch.rpm).
The tunnel script released in version 1.2.0 contained errors -- a corrected script is available.
There are a couple of serious bugs in iptables 1.2.3 that prevent it from working with Shorewall. Regrettably, RedHat released this buggy iptables in RedHat 7.2.
I have built a corrected 1.2.3 rpm which you can download here and I have also built an iptables-1.2.4 rpm which you can download here. If you are currently running RedHat 7.1, you can install either of these RPMs before you upgrade to RedHat 7.2.
Update 11/9/2001: RedHat has released an iptables-1.2.4 RPM of their own which you can download from http://www.redhat.com/support/errata/RHSA-2001-144.html. I have installed this RPM on my firewall and it works fine.
If you would like to patch iptables 1.2.3 yourself, the patches are available for download. This patch which corrects a problem with parsing of the --log-level specification while this patch corrects a problem in handling the TOS target.
To install one of the above patches:
- cd iptables-1.2.3/extensions
- patch -p0 < the-patch-file
Users who use RedHat iptables RPMs and who upgrade to kernel 2.4.18 may experience the following:
# shorewall start Processing /etc/shorewall/shorewall.conf ... Processing /etc/shorewall/params ... Starting Shorewall... Loading Modules... Initializing... Determining Zones... Zones: net Validating interfaces file... Validating hosts file... Determining Hosts in Zones... Net Zone: eth0:0.0.0.0/0 iptables: libiptc/libip4tc.c:380: do_check: Assertion `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed. Aborted (core dumped) iptables: libiptc/libip4tc.c:380: do_check: Assertion `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed. Aborted (core dumped)The RedHat iptables RPM is compiled with debugging enabled but the user-space debugging code was not updated to reflect recent changes in the Netfilter 'mangle' table. You can correct the problem by installing this iptables RPM. If you are already running a 1.2.5 version of iptables, you will need to specify the --oldpackage option to rpm (e.g., "iptables -Uvh --oldpackage iptables-1.2.5-1.i386.rpm").
Last updated 5/24/2002 - Tom Eastep