From 0e8d1e958fc7a4b0907fb2eaef52ed921b24e7f3 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Mon, 16 May 2005 01:47:01 +0000
Subject: [PATCH] More ROUTE updates

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2125 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 Shorewall-docs2/Shorewall_Doesnt.xml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Shorewall-docs2/Shorewall_Doesnt.xml b/Shorewall-docs2/Shorewall_Doesnt.xml
index 02ca7745f..495a8c202 100644
--- a/Shorewall-docs2/Shorewall_Doesnt.xml
+++ b/Shorewall-docs2/Shorewall_Doesnt.xml
@@ -13,7 +13,7 @@
       <surname>Eastep</surname>
     </author>
 
-    <pubdate>2005-02-20</pubdate>
+    <pubdate>2005-05-15</pubdate>
 
     <copyright>
       <year>2003</year>
@@ -76,7 +76,9 @@
 
       <listitem>
         <para>Set up Routing (except to support <ulink
-        url="ProxyARP.htm">Proxy ARP</ulink>)</para>
+        url="ProxyARP.htm">Proxy ARP</ulink>) — Shorewall 2.3.3 and later CAN
+        be used to set up complex routing provided that your kernel and
+        iptables include ROUTE target support.</para>
       </listitem>
 
       <listitem>