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

Update the providers manpage re balanced IPv6 routes

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2017-08-05 10:12:42 -07:00
parent 56c8f70b52
commit f2ee8013fc
No known key found for this signature in database
GPG Key ID: 96E6B3F2423A4D10
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -214,7 +214,14 @@
BALANCE_PROVIDERS=Yes, <option>balance=1</option> is assumed BALANCE_PROVIDERS=Yes, <option>balance=1</option> is assumed
unless the <option>fallback</option>, <option>loose</option>, unless the <option>fallback</option>, <option>loose</option>,
<option>load</option> or <option>tproxy</option> option is <option>load</option> or <option>tproxy</option> option is
specified.</para> specified.I</para>
<caution>
<para>In IPV6, the <option>balance</option> option does not
cause balanced default routes to be created; it rather
causes a sequence of default routes with different metrics
to be created. </para>
</caution>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -337,6 +344,14 @@
<para>Prior to Shorewall 4.4.24, the option is ignored with a <para>Prior to Shorewall 4.4.24, the option is ignored with a
warning message if USE_DEFAULT_RT=Yes in warning message if USE_DEFAULT_RT=Yes in
<filename>shorewall.conf</filename>.</para> <filename>shorewall.conf</filename>.</para>
<caution>
<para>In IPV6, specifying the <option>fallback</option>
option on multiple providers does not cause balanced
fallback routes to be created; it rather causes a sequence
of fallback routes with different metrics to be
created.</para>
</caution>
</listitem> </listitem>
</varlistentry> </varlistentry>