holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Update Multi-ISP documentation

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2012-05-01 10:28:12 -07:00
parent 45c637ad6b
commit 2dd82a9898
3 changed files with 14 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Shorewall/manpages/shorewall-providers.xml
View File

@ -87,8 +87,7 @@
being zero). Otherwise, the value must be between 1 and 255. Each being zero). Otherwise, the value must be between 1 and 255. Each
provider must be assigned a unique mark value. This column may be provider must be assigned a unique mark value. This column may be
omitted if you don't use packet marking to direct connections to a omitted if you don't use packet marking to direct connections to a
particular provider and you don't specify <option>track</option> in particular provider.</para>
the OPTIONS column.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>

12
Shorewall6/manpages/shorewall6-providers.xml
View File

@ -87,8 +87,7 @@
of the value being zero). Otherwise, the value must be between 1 and of the value being zero). Otherwise, the value must be between 1 and
255. Each provider must be assigned a unique mark value. This column 255. Each provider must be assigned a unique mark value. This column
may be omitted if you don't use packet marking to direct connections may be omitted if you don't use packet marking to direct connections
to a particular provider and you don't specify to a particular provider.</para>
<option>track</option> in the OPTIONS column.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -321,10 +320,9 @@
<para>shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), <para>shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5),
shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5),
shorewall6-policy(5), shorewall6-rtrules(5), shorewall6-policy(5), shorewall6-rtrules(5), shorewall6-routestopped(5),
shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5),
shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5),
shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)</para>
shorewall6-zones(5)</para>
</refsect1> </refsect1>
</refentry> </refentry>

37
docs/MultiISP.xml
View File

@ -50,7 +50,7 @@
<warning> <warning>
<para>This document describes the Multi-ISP facility in <emphasis <para>This document describes the Multi-ISP facility in <emphasis
role="bold">Shorewall 4.5.0 and later</emphasis>. If you are running an role="bold">Shorewall 4.4.26 and later</emphasis>. If you are running an
earlier release, please see the documentation for that release.</para> earlier release, please see the documentation for that release.</para>
</warning> </warning>
@ -251,25 +251,25 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>These mark values must be a multiple of 256 in the <para>With HIGH_ROUTE_MARKS=Yes (PROVIDER_OFFSET=8), these
range 256-65280 (hex equivalent 0x100 - 0xFF00 with the mark values must be a multiple of 256 in the range
256-65280 (hex equivalent 0x100 - 0xFF00 with the
low-order 8 bits being zero); or</para> low-order 8 bits being zero); or</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Set WIDE_TC_MARKS=Yes in <ulink <para>Set WIDE_TC_MARKS=Yes in <ulink
url="manpages/shorewall.conf.html">shorewall.conf url="manpages/shorewall.conf.html">shorewall.conf
</ulink>(5) and use mark values in the range 0x10000 - </ulink>(5) (PROVIDER_OFFSET=16), and use mark values in
0xFF0000 with the low-order 16 bits being zero.</para> the range 0x10000 - 0xFF0000 with the low-order 16 bits
being zero.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>This column may be omitted if you don´t use packet marking <para>This column may be omitted if you don´t use packet marking
to direct connections to a particular provider and you don´t to direct connections to a particular provider.</para>
specify <emphasis role="bold">track</emphasis> in the OPTIONS
column.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -417,27 +417,6 @@
url="FAQ.htm#faq58">FAQ 58</ulink>.</para> url="FAQ.htm#faq58">FAQ 58</ulink>.</para>
</note></para> </note></para>
</important> </important>
<important>
<para>If you specify <emphasis
role="bold">balance</emphasis> and still find that all
traffic is going out through only one provider, you may
need to install a kernel built with
CONFIG_IP_ROUTE_MULTIPATH_CACHED=n. Several users have
reported that this change has corrected similar
problems.</para>
<para>The SuSE 10.0 kernel is subject to this problem, and
<ulink
url="https://bugzilla.novell.com/show_bug.cgi?id=190908">
a kernel oops may result in this circumstance.</ulink>
SUSE 10.1 and SLES 10 have
CONFIG_IP_ROUTE_MULTIPATH_CACHED=n set by default. The
source of the problem seems to be <ulink
url="http://news.gmane.org/find-root.php?message_id=%3c00da01c5b35a%24b12b9860%241b00a8c0%40cruncher%3e">an
incompatibility between the LARTC patches and
CONFIG_IP_ROUTE_MULTIPATH_CACHED.</ulink></para>
</important>
</listitem> </listitem>
</varlistentry> </varlistentry>