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

Warning when 'persistent' used with RESTORE_DEFAULT_ROUTE=Yes

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2017-10-11 14:11:20 -07:00
parent 02ed36332a
commit 8ea96098bf
No known key found for this signature in database
GPG Key ID: 96E6B3F2423A4D10
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Shorewall/Perl/Shorewall/Providers.pm
View File

@ -602,6 +602,7 @@ sub process_a_provider( $ ) {
} elsif ( $option eq 'nohostroute' ) {
$hostroute = 0;
} elsif ( $option eq 'persistent' ) {
warning_message "When RESTORE_DEFAULT_ROUTE=Yes, the 'persistent' option may not work as expected" if $config{RESTORE_DEFAULT_ROUTE};
$persistent = 1;
} else {
fatal_error "Invalid option ($option)";

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

@ -220,7 +220,7 @@
<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>
to be created.</para>
</caution>
</listitem>
</varlistentry>
@ -438,6 +438,14 @@
<command>enable</command> and <command>reenable</command>
commands can reenable the provider.</para>
</note>
<important>
<para>RESTORE_DEFAULT_OPTION=Yes in shorewall[6].conf is not
recommended when the <option>persistent</option> option is
used, as restoring default routes to the main routing table
can prevent link status monitors such as foolsm from
correctly detecting non-working providers.</para>
</important>
</listitem>
</varlistentry>
</variablelist>