diff --git a/STABLE/shorewall.conf b/STABLE/shorewall.conf
index ea84b080a..5d6c3e8a5 100644
--- a/STABLE/shorewall.conf
+++ b/STABLE/shorewall.conf
@@ -502,4 +502,20 @@ RFC1918_LOG_LEVEL=info
 
 MARK_IN_FORWARD_CHAIN=No
 
+#
+# Clear Traffic Shapping/Control
+#
+# If this option is set to 'No' then Shorewall won't clear the current
+# traffic control rules during [re]start. This setting is intended
+# for use by people that prefer to configure traffic shaping when
+# the network interfaces come up rather than when the firewall
+# is started. If that is what you want to do, set TC_ENABLED=Yes and
+# CLEAR_TC=No and do not supply an /etc/shorewall/tcstart file. That
+# way, your traffic shaping rules can still use the 'fwmark'
+# classifier based on packet marking defined in /etc/shorewall/tcrules.
+#
+# If omitted, CLEAR_TC=Yes is assumed.
+
+CLEAR_TC=Yes
+
 #LAST LINE -- DO NOT REMOVE
diff --git a/Shorewall/shorewall.conf b/Shorewall/shorewall.conf
index ea84b080a..5d6c3e8a5 100755
--- a/Shorewall/shorewall.conf
+++ b/Shorewall/shorewall.conf
@@ -502,4 +502,20 @@ RFC1918_LOG_LEVEL=info
 
 MARK_IN_FORWARD_CHAIN=No
 
+#
+# Clear Traffic Shapping/Control
+#
+# If this option is set to 'No' then Shorewall won't clear the current
+# traffic control rules during [re]start. This setting is intended
+# for use by people that prefer to configure traffic shaping when
+# the network interfaces come up rather than when the firewall
+# is started. If that is what you want to do, set TC_ENABLED=Yes and
+# CLEAR_TC=No and do not supply an /etc/shorewall/tcstart file. That
+# way, your traffic shaping rules can still use the 'fwmark'
+# classifier based on packet marking defined in /etc/shorewall/tcrules.
+#
+# If omitted, CLEAR_TC=Yes is assumed.
+
+CLEAR_TC=Yes
+
 #LAST LINE -- DO NOT REMOVE