mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-08 16:54:10 +01:00
Remove another anachronism from the setup guide
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3073 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
5b89260fbb
commit
da92ac965b
@ -123,7 +123,7 @@
|
||||
|
||||
<para>As each file is introduced, I suggest that you look through the
|
||||
actual file on your system -- each file contains detailed configuration
|
||||
instructions and some contain default entries.</para>
|
||||
instructions.</para>
|
||||
|
||||
<para>Shorewall views the network where it is running as being composed of
|
||||
a set of zones. In this guide, we will use the following zones:</para>
|
||||
@ -248,7 +248,7 @@ dmz ipv4</programlisting>
|
||||
A to the firewall and are also allowed from the firewall to zone B
|
||||
<emphasis role="bold">DOES NOT mean that these connections are allowed
|
||||
from zone A to zone B</emphasis> (in other words, policies and rules
|
||||
involving the firewall zone are not transitibe). It rather means that you
|
||||
involving the firewall zone are not transitive). It rather means that you
|
||||
can have a proxy running on the firewall that accepts a connection from
|
||||
zone A and then establishes its own separate connection from the firewall
|
||||
to zone B.</para>
|
||||
|
Loading…
Reference in New Issue
Block a user