Add note for those who don't believe that they need 'balance' on their providers -- revise

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4510 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-09-04 01:44:39 +00:00
parent 05b5adc156
commit 848a48e462

View File

@ -338,22 +338,23 @@
to force traffic to one provider or another.<note>
<para>There will be those of you who will say "Those
idiots at shorewall.net don't understand. I don't want
my traffic balanced so I'm not going to set that
option!" If you are one of those users, then when you
can't get your second interface to work, check the
mailing list archives -- there have been others before
you who thought we were fools too.</para>
my traffic balanced so I'm not going to set the
'balance' option!" If you are one of those users, then
if you can't get your second interface to work, check
the mailing list archives -- there have been others
before you who also thought that we were fools.</para>
</note><note>
<para>"Oh Tom -- I can't figure out how to use
<para>"Oh Tom -- I don't understand 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
<para>I know -- that is only slightly less complex
than brain surgery but let me try to
help:<itemizedlist>
explain:<itemizedlist>
<listitem>
<para>Your first tcrule should mark the traffic so
that it goes out the "default" provider.</para>
<para>Your first tcrule should mark all traffic so
that it will go out through the "default"
provider.</para>
</listitem>
<listitem>
@ -363,8 +364,8 @@
</listitem>
</itemizedlist></para>
<para>I hope your brain isn't swimming too badly from
those intricate instructions.</para>
<para>I hope that you are not overwelmed by these
intricate instructions.</para>
</note></para>
</important>