diff --git a/docs/MultiISP.xml b/docs/MultiISP.xml
index e7d6ab15b..7113112bc 100644
--- a/docs/MultiISP.xml
+++ b/docs/MultiISP.xml
@@ -237,23 +237,6 @@
low-order 8 bits being zero).
-
-
- A bug in Shorewall versions 3.2.0-3.2.10, 3.4.0-3.4.6 and
- 4.0.0-4.0.2 prevents proper handling of PREROUTING marks when
- HIGH_ROUTE_MARKS=No. Patches are available to correct this
- problem:
-
- Shorewall version 3.2.0-3.4.3: http://www1.shorewall.net/pub/shorewall/3.2/shorewall-3.2.10/errata/patches/Shorewall/patch-3.2.10-2.diff
-
-
- Shorewall version 3.4.4-3.4.6: http://www1.shorewall.net/pub/shorewall/3.4/shorewall-3.4.6/errata/patches/Shorewall/patch-3.4.6-1.diff
-
- Shorewall-shell version 4.0.0-4.0.2: http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.2/errata/patches/Shorewall-shell/patch-shell-4.0.2-2.diff
-
@@ -323,12 +306,22 @@
It does not require the ROUTE target extension.
- iptables 1.3.1 is broken with respect to CONNMARK
- and iptables-save/iptables-restore. This means that if you
- configure multiple ISPs, shorewall
- restore may fail. If it does, you may patch your
- iptables using the patch at http://shorewall.net/pub/shorewall/contrib/iptables/CONNMARK.diff.
+ A bug in Shorewall
+ versions 3.2.0-3.2.10, 3.4.0-3.4.6 and 4.0.0-4.0.2
+ prevents proper handling of PREROUTING marks when
+ HIGH_ROUTE_MARKS=No and the track option is specified. Patches
+ are available to correct this problem:
+
+ Shorewall version 3.2.0-3.4.3: http://www1.shorewall.net/pub/shorewall/3.2/shorewall-3.2.10/errata/patches/Shorewall/patch-3.2.10-2.diff
+
+
+ Shorewall version 3.4.4-3.4.6: http://www1.shorewall.net/pub/shorewall/3.4/shorewall-3.4.6/errata/patches/Shorewall/patch-3.4.6-1.diff
+
+ Shorewall-shell version 4.0.0-4.0.2: http://www1.shorewall.net/pub/shorewall/4.0/shorewall-4.0.2/errata/patches/Shorewall-shell/patch-shell-4.0.2-2.diff