Clarify when a bridge/firewall is appropriate

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4193 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-07-06 15:22:50 +00:00
parent 199416cbef
commit 9a9d03e748
2 changed files with 15 additions and 7 deletions

View File

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>2006-03-20</pubdate>
<pubdate>2006-07-06</pubdate>
<copyright>
<year>2004</year>
@ -168,6 +168,16 @@
</listitem>
</itemizedlist>
<warning>
<para>Inserting a bridge/firewall between a router and a set of local
hosts only works if those local hosts form a single IP network. In the
above diagram, all of the hosts in the loc zone are in the
192.168.1.0/24 network. If the router is routing between several local
networks through the same physical interface (there are multiple IP
networks sharing the same LAN), then inserting a bridge/firewall between
the router and the local LAN won't work.</para>
</warning>
<para>There are other possibilities here -- there could be a hub or switch
between the router and the Bridge/Firewall and there could be other
systems connected to that switch. All of the systems on the local side of
@ -239,8 +249,8 @@ BOOTPROTO=dhcp
ONBOOT=yes</programlisting>
</blockquote>
<para>On both the <trademark>SUSE</trademark> and Mandriva systems,
a separate script is required to configure the bridge itself.</para>
<para>On both the <trademark>SUSE</trademark> and Mandriva systems, a
separate script is required to configure the bridge itself.</para>
<para>Here are scripts that I used on a <trademark>SUSE</trademark> 9.1
system.</para>
@ -607,4 +617,4 @@ dmz br0:eth2</programlisting>
</listitem>
</itemizedlist>
</section>
</article>
</article>

View File

@ -15,9 +15,7 @@
<pubdate>2006-05-24</pubdate>
<copyright>
<year>2002-</year>
<year>2006</year>
<year>2002-2006</year>
<holder>Thomas M. Eastep</holder>
</copyright>