From 6239218db53b2506817cffc4e4da88c1061fa8eb Mon Sep 17 00:00:00 2001
From: Tom Eastep <teastep@shorewall.net>
Date: Mon, 8 Feb 2010 06:45:11 -0800
Subject: [PATCH] Warn about absense of the 'flow' classifier.

Signed-off-by: Tom Eastep <teastep@shorewall.net>
---
 docs/simple_traffic_shaping.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/simple_traffic_shaping.xml b/docs/simple_traffic_shaping.xml
index a95fc115e..0f5b38d36 100644
--- a/docs/simple_traffic_shaping.xml
+++ b/docs/simple_traffic_shaping.xml
@@ -65,6 +65,21 @@
     <programlisting>#INTERFACE             TYPE          IN-BANDWIDTH
 eth0                   External</programlisting>
 
+    <note>
+      <para>If you experience an error such as the following during
+      <command>shorewall start</command> or <command>shorewall
+      restart</command>, your kernel and iproute do not support the <emphasis
+      role="bold">flow</emphasis> classifier. In that case, you must leave the
+      TYPE column empty (or specify '-').</para>
+
+      <programlisting>Unknown filter "flow", hence option "hash" is unparsable
+   ERROR: Command "tc filter add dev eth0 protocol all prio 1 parent 11: handle 11 flow hash keys nfct-src divisor 1024" Failed</programlisting>
+
+      <para>RHEL5-based systems such as <trademark>CentOS</trademark> 5 and
+      <trademark>Foobar</trademark> 5 are known to experience this
+      error.</para>
+    </note>
+
     <para>With this simple configuration, packets to be sent through interface
     eth0 will be assigned to a priority band based on the value of their TOS
     field:</para>