Add note for those who don't believe that they need 'balance' on their providers -- add a bit more

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4509 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-09-04 00:55:02 +00:00
parent 72c7e8953e
commit 05b5adc156

View File

@ -339,10 +339,32 @@
<para>There will be those of you who will say "Those <para>There will be those of you who will say "Those
idiots at shorewall.net don't understand. I don't want idiots at shorewall.net don't understand. I don't want
my traffic balanced so I'm not going to set that my traffic balanced so I'm not going to set that
option!" When you can't get your second interface to option!" If you are one of those users, then when you
work, check the mailing list archives -- there have can't get your second interface to work, check the
been others before you who thought we were fools mailing list archives -- there have been others before
too".</para> you who thought we were fools too.</para>
</note><note>
<para>"Oh Tom -- I can't figure out how to use
<filename>/etc/shorewall/tcrules</filename> to avoid
balancing if I set 'balance' on my interfaces".</para>
<para>I know -- this is only slightly less complex
than brain surgery but let me try to
help:<itemizedlist>
<listitem>
<para>Your first tcrule should mark the traffic so
that it goes out the "default" provider.</para>
</listitem>
<listitem>
<para>Your remaining rules should be the "exception"
rules that mark traffic to go out the other
providers.</para>
</listitem>
</itemizedlist></para>
<para>I hope your brain isn't swimming too badly from
those intricate instructions.</para>
</note></para> </note></para>
</important> </important>