mirror of
https://gitlab.com/shorewall/code.git
synced 2024-12-22 22:30:58 +01:00
Document CLASSIFY change
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4365 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
9de434881f
commit
27cec53079
@ -500,12 +500,16 @@ ppp0 6000kbit 500kbit</programlisting>
|
||||
<member>prio</member>
|
||||
</simplelist>
|
||||
|
||||
<para>Classify always occurs in the POSTROUTING chain. When used
|
||||
with the builtin traffic shaper, the <major> class is the
|
||||
device number (the first entry in
|
||||
<filename>/etc/shorewall/tcdevices</filename> is device 1, the
|
||||
second is device 2 and so on) and the <minor> class is the
|
||||
MARK value of the class + 100.</para>
|
||||
<para>With Shorewall versions prior to 3.2.3, classify always occurs
|
||||
in the POSTROUTING chain. Beginning with Shorewall 3.2.3, classify
|
||||
occurs in the POSTROUTING chain <emphasis
|
||||
role="bold">except</emphasis> when the SOURCE contains
|
||||
$FW[:<<emphasis>address</emphasis>>] in which case, the
|
||||
classify action takes place in the OUTPUT chain. When used with the
|
||||
builtin traffic shaper, the <major> class is the device number
|
||||
(the first entry in <filename>/etc/shorewall/tcdevices</filename> is
|
||||
device 1, the second is device 2 and so on) and the <minor>
|
||||
class is the MARK value of the class + 100.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
Loading…
Reference in New Issue
Block a user