extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-08 08:44:05 +01:00
Code Issues Packages Projects Releases Wiki Activity

Yet more enhancements to Lenny->Squeeze doc

Browse Source
This commit is contained in:
Tom Eastep 2009-09-07 09:35:15 -07:00
parent 180024c1fc
commit 8da5fd42d0
1 changed files with 26 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
docs/LennyToSqueeze.xml
View File

@ -410,9 +410,11 @@ ipsec2 ipv4</programlisting>
contains anything except 'detect' or '-', then you will receive this
warning:</para>
<para><emphasis role="bold">WARNING: Shorewall no longer uses broadcast
addresses in rule generation when Address Type Match is
<blockquote>
<para><emphasis role="bold">WARNING: Shorewall no longer uses
broadcast addresses in rule generation when Address Type Match is
available</emphasis></para>
</blockquote>
<para>To eliminate the warning, replace the contents of the BROADCAST
column with '-' or 'detect'.</para>
@ -420,12 +422,10 @@ ipsec2 ipv4</programlisting>
<para>The 'norfc1918' option has been removed. If you specify the
option, you will receive the following warning:</para>
<para><emphasis role="bold">WARNING: Support for the norfc1918 interface
option has been removed from Shorewall</emphasis></para>
<para>To suppress the warning, remove 'norfc1918' from the OPTIONS list.
As a replacement, consider setting NULL_ROUTE_RFC1919=Yes in <ulink
url="manpages/shorewall.conf.html">shorewall.conf</ulink> (5).</para>
<blockquote>
<para><emphasis role="bold">WARNING: Support for the norfc1918
interface option has been removed from Shorewall</emphasis></para>
</blockquote>
</section>
<section>
@ -434,12 +434,10 @@ ipsec2 ipv4</programlisting>
<para>The 'norfc1918' option has been removed. If you specify the
option, you will receive the following warning:</para>
<para><emphasis role="bold">WARNING: The 'norfc1918' option is no longer
supported</emphasis></para>
<para>To suppress the warning, remove 'norfc1918' from the OPTIONS list.
As a replacement, consider setting NULL_ROUTE_RFC1919=Yes in <ulink
url="manpages/shorewall.conf.html">shorewall.conf</ulink> (5).</para>
<blockquote>
<para><emphasis role="bold">WARNING: The 'norfc1918' option is no
longer supported</emphasis></para>
</blockquote>
</section>
<section>
@ -462,9 +460,11 @@ ipsec2 ipv4</programlisting>
SOURCE column of one or more entries, a single warning as follows is
issued:</para>
<blockquote>
<para><emphasis role="bold">WARNING: Using an interface as the masq
SOURCE requires the interface to be up and configured when Shorewall
starts/restarts</emphasis></para>
</blockquote>
<para>To suppress this warning, replace the interface name with the list
of networks that are routed out of the interface.</para>
@ -502,8 +502,10 @@ eth0 172.20.1.0/24</programlisting>
<para>If you include a destination zone in a 'nonat' rule, Shorewall
issues the following warning:</para>
<para><emphasis role="bold">WARNING: Destination zone
(<firstterm>zonename</firstterm>) ignored.</emphasis></para>
<blockquote>
<para><emphasis role="bold">WARNING: Destination zone (zonename)
ignored.</emphasis></para>
</blockquote>
<para>Nonat rules include:</para>
@ -539,8 +541,10 @@ NONAT loc - tcp 80</programlisting>
supported. If you have critical hosts defined, you will receive this
warning:</para>
<para><emphasis role="bold">WARNING: The 'critical' option is no longer
supported (or needed)</emphasis></para>
<blockquote>
<para><emphasis role="bold">WARNING: The 'critical' option is no
longer supported (or needed)</emphasis></para>
</blockquote>
<para>To suppress the warning, simply remove the option.</para>