diff --git a/Shorewall-docs/errata.xml b/Shorewall-docs/errata.xml
index af2da271d..7f22bb3d0 100644
--- a/Shorewall-docs/errata.xml
+++ b/Shorewall-docs/errata.xml
@@ -2,7 +2,7 @@
-
+
Shorewall Errata
@@ -45,8 +45,8 @@
If you are installing Shorewall for the first time and plan to
use the .tgz and install.sh script, you can untar the archive, replace
- the 'firewall' script in the untarred directory with the one
- you downloaded below, and then run install.sh.
+ the firewall
script in the untarred directory with the
+ one you downloaded below, and then run install.sh.
@@ -90,8 +90,9 @@
- Using some versions of 'ash' (such as from RH8) as the
- SHOREWALL_SHELL causes "shorewall [re]start" to fail with: local: --limit: bad variable name
+ Using some versions of ash
(such as from RH8)
+ as the SHOREWALL_SHELL causes shorewall [re]start
to
+ fail with: local: --limit: bad variable name
iptables v1.2.8: Couldn't load match `-j':/lib/iptables/libipt_-j.so:
cannot open shared object file: No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
@@ -133,8 +134,8 @@
If TC_ENABLED is set to yes in shorewall.conf then Shorewall
- would fail to start with the error "ERROR: Traffic
- Control requires Mangle"; that problem has been corrected in
+ would fail to start with the error ERROR: Traffic
+ Control requires Mangle
; that problem has been corrected in
this
firewall script which may be installed in
@@ -153,8 +154,8 @@
url="http://shorewall.net/pub/shorewall/errata/1.4.6/firewall">this
firewall script which may be installed in
/usr/share/shorewall/firewall as described above. For all other
- versions, you will have to edit your 'firewall' script (in
- versions 1.4.*, it is located in /usr/share/shorewall/firewall).
+ versions, you will have to edit your firewall
script
+ (in versions 1.4.*, it is located in /usr/share/shorewall/firewall).
Locate the function add_tcrule_() and in that function, replace this
line: r=`mac_match $source` with r="`mac_match $source` "Note
that there must be a space before the ending quote!
@@ -235,9 +236,9 @@
- When an 'add' or 'delete' command is executed,
- a temporary directory created in /tmp is not being removed. This
- problem may be corrected by installing When an add
or delete
command is
+ executed, a temporary directory created in /tmp is not being
+ removed. This problem may be corrected by installing this
firewall script in /usr/share/shorewall/firewall as
described above.
@@ -250,8 +251,8 @@
- Some TCP requests are rejected in the 'common' chain
- with an ICMP port-unreachable response rather than the more
+ Some TCP requests are rejected in the common
+ chain with an ICMP port-unreachable response rather than the more
appropriate TCP RST response. This problem is corrected in this
updated common.def file which may be installed in
@@ -265,8 +266,8 @@
- When a "shorewall check" command is executed, each
- "rule" produces the harmless additional message: /usr/share/shorewall/firewall: line 2174: [: =: unary operator expectedYou
+ When a shorewall check
command is executed,
+ each rule
produces the harmless additional message: /usr/share/shorewall/firewall: line 2174: [: =: unary operator expectedYou
may correct the problem by installing this
corrected script in /usr/share/shorewall/firewall as
@@ -360,12 +361,12 @@ 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
+ 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").
+ iptables -Uvh --oldpackage iptables-1.2.5-1.i386.rpm
).
@@ -400,13 +401,13 @@ Aborted (core dumped)
192.0.2.22 eth0 192.168.9.22 yes yes
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE
- Error message is:
+ Error message is:
Setting up NAT...
iptables: Invalid argument
Terminated
- The solution is to put "no" in the LOCAL column. Kernel
+ The solution is to put no
in the LOCAL column. Kernel
support for LOCAL=yes has never worked properly and 2.4.18-10 has disabled
it. The 2.4.19 kernel contains corrected support under a new kernel
configuraiton option; see
Problems with RH Kernels after 2.4.20-9 and REJECT (also applies to
2.4.21-RC1)
- Beginning with errata kernel 2.4.20-13.9, "REJECT --reject-with
- tcp-reset" is broken. The symptom most commonly seen is that REJECT
- rules act just like DROP rules when dealing with TCP. A kernel patch and
- precompiled modules to fix this problem are available at ftp://ftp1.shorewall.net/pub/shorewall/errata/kernel.
+ Beginning with errata kernel 2.4.20-13.9, REJECT
+ --reject-with tcp-reset
is broken. The symptom most commonly seen
+ is that REJECT rules act just like DROP rules when dealing with TCP. A
+ kernel patch and precompiled modules to fix this problem are available at
+ ftp://ftp1.shorewall.net/pub/shorewall/errata/kernel.
\ No newline at end of file
diff --git a/Shorewall-docs/fallback.xml b/Shorewall-docs/fallback.xml
index a20989034..f206ee36a 100644
--- a/Shorewall-docs/fallback.xml
+++ b/Shorewall-docs/fallback.xml
@@ -2,7 +2,7 @@
-
+
Fallback and Uninstall
@@ -48,7 +48,7 @@
- Type "./fallback.sh"
+ Type ./fallback.sh
@@ -65,9 +65,9 @@
Falling Back to the Previous Version of Shorewall using rpm
If your previous version of Shorewall was installed using RPM, you
- may fall back to that version by typing "rpm -Uvh --force <old
- rpm>" at a root shell prompt (Example: "rpm -Uvh --force
- /downloads/shorewall-3.1=0noarch.rpm" would fall back to the 3.1-0
+ may fall back to that version by typing rpm -Uvh --force <old
+ rpm>
at a root shell prompt (Example: rpm -Uvh --force
+ /downloads/shorewall-3.1=0noarch.rpm
would fall back to the 3.1-0
version of Shorewall).
@@ -83,11 +83,11 @@
- type "./uninstall.sh"
+ type ./uninstall.sh
- If you installed using an rpm, at a root shell prompt type "rpm
- -e shorewall".
+ If you installed using an rpm, at a root shell prompt type
+ rpm -e shorewall
.
\ No newline at end of file