diff --git a/docs/IPv6Support.xml b/docs/IPv6Support.xml
index 0e349ae65..02da2b303 100644
--- a/docs/IPv6Support.xml
+++ b/docs/IPv6Support.xml
@@ -98,7 +98,7 @@
family has no effect on the other address family.
As a consequence, there is very little interaction between
- Shorewall and Shorewall6.
+ Shorewall and Shorewall6.
DISABLE_IPV6
@@ -113,7 +113,7 @@
TC_ENABLED
- The other area where their configurations overlap is in traffic
+ Another area where their configurations overlap is in traffic
shaping; the tcdevices and tcclasses files do
exactly the same thing in both Shorewall and Shorewall6. Consequently,
you will have TC_ENABLED=Internal in Shorewall or in Shorewall6 and
@@ -134,6 +134,41 @@
+
+
+ KEEP_RT_TABLES
+
+ Multi-ISP users will need to be aware of this one. When there
+ are entries in the providers file, Shorewall normally installs a
+ modified /etc/iproute2/rt_tables during
+ shorewall start and shorewall
+ restart and restores a default file during
+ shorewall stop. Setting KEEP_RT_TABLES=Yes in
+ shorewall.conf(5)
+ stops Shorewall (Shorewall lite) from modifying
+ /etc/iproute2/rt_tables.
+
+ Shorewall6 is also capable of modifying
+ /etc/iproute2/rt_tables in a similar way.
+
+ Our recommendation to Multi-ISP users is to:
+
+
+
+ Select the same names for similar providers.
+
+
+
+ Set KEEP_RT_TABLES=No in shorewall.conf(5) and
+ set KEEP_RT_TABLES=Yes in shorewall6.conf(5).
+
+
+
+ These setting allow Shorewall to control the contents of
+ /etc/iproute2/rt_tables.
+