From 4b3196b95987534db323f20c7ba95c8d287923f1 Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Fri, 18 Jul 2014 13:49:30 -0700 Subject: [PATCH] Add refmiscinfo to the shorewall-tcrules manpage Signed-off-by: Tom Eastep --- Shorewall/manpages/shorewall-tcrules.xml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/Shorewall/manpages/shorewall-tcrules.xml b/Shorewall/manpages/shorewall-tcrules.xml index 4e443a08a..c35ddbc92 100644 --- a/Shorewall/manpages/shorewall-tcrules.xml +++ b/Shorewall/manpages/shorewall-tcrules.xml @@ -6,6 +6,8 @@ shorewall-mangle 5 + + Configuration Files @@ -28,10 +30,10 @@ Unlike rules in the shorewall-rules(5) file, evaluation - of rules in this file will continue after a match. So the final mark for - each packet will be the one assigned by the LAST tcrule that - matches. + url="/manpages/shorewall-rules.html">shorewall-rules(5) file, + evaluation of rules in this file will continue after a match. So the + final mark for each packet will be the one assigned by the LAST tcrule + that matches. If you use multiple internet providers with the 'track' option, in /etc/shorewall/providers be sure to read the restrictions at When using Shorewall's built-in traffic shaping tool, the major class is the device number (the first device in shorewall-tcdevices(5) is - major class 1, the second device is major class 2, and so on) + url="/manpages/shorewall-tcdevices.html">shorewall-tcdevices(5) + is major class 1, the second device is major class 2, and so on) and the minor class is the class's MARK value in shorewall-tcclasses(5) @@ -487,7 +489,8 @@ [option] ...") after any matches specified at the end of the rule. If the target is not one known to Shorewall, then it must be defined as a builtin action in - shorewall-actions + shorewall-actions (5). The following rules are equivalent: @@ -500,8 +503,8 @@ INLINE eth0 - ; -p tcp -j MARK --set-mark If INLINE_MATCHES=Yes in shorewall.conf(5) then the - third rule above can be specified as follows: + url="/manpages/shorewall.conf.html">shorewall.conf(5) + then the third rule above can be specified as follows: 2:P eth0 - ; -p tcp