From 1db3bfb53e87597deabc9931d6906ae43b39842c Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Sat, 10 Oct 2015 13:19:41 -0700 Subject: [PATCH] Manpage updates Signed-off-by: Tom Eastep --- Shorewall/manpages/shorewall.conf.xml | 5 +++-- Shorewall6/manpages/shorewall6.conf.xml | 11 ++++++++++- 2 files changed, 13 insertions(+), 3 deletions(-) diff --git a/Shorewall/manpages/shorewall.conf.xml b/Shorewall/manpages/shorewall.conf.xml index b3f8538b1..992ecd1db 100644 --- a/Shorewall/manpages/shorewall.conf.xml +++ b/Shorewall/manpages/shorewall.conf.xml @@ -89,7 +89,7 @@ colon (":") and a log tag. The log tag normally follows the packet disposition in Shorewall-generated Netfilter log messages, separated from the disposition by a colon (e.g, "DROP:mytag"). - See LOGTAGONLY below for additional information. + See LOGTAGONLY below for additional information. Beginning with Shorewall 4.4.22, LOGMARK is also a valid level which logs the packet's mark value along with the other usual information. The @@ -2479,7 +2479,8 @@ INLINE - - - ; -j REJECT role="bold">Yes|No|Internal|Simple|Shared] + role="bold">Simple|Shared] If you say Yes or TC_ENABLED=[Yes|No|Internal|Shared] + role="bold">Internal|Simple|Shared] If you say Yes or + If you set TC_ENABLED=Simple (Shorewall 4.4.6 and later), + simple traffic shaping using shorewall-tcinterfaces(5) + and shorewall-tcpri(5) is + enabled. + Beginning with Shorewall 4.4.15, if you set TC_ENABLED=Shared or shared, then you should create symbolic links from your Shorewall6 configuration directory (normally