From d583d40787bb0ca7e9c20644cf7a09b386ce3886 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Sat, 11 Dec 2004 15:36:42 +0000
Subject: [PATCH] Documentation updates for 2.2.0 Beta 8

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1820 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 Shorewall-docs2/SimpleBridge.xml | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/Shorewall-docs2/SimpleBridge.xml b/Shorewall-docs2/SimpleBridge.xml
index 27f5bad9c..e7de1cc7f 100644
--- a/Shorewall-docs2/SimpleBridge.xml
+++ b/Shorewall-docs2/SimpleBridge.xml
@@ -15,7 +15,7 @@
       </author>
     </authorgroup>
 
-    <pubdate>2004-09-23</pubdate>
+    <pubdate>2004-12-07</pubdate>
 
     <copyright>
       <year>2004</year>
@@ -71,8 +71,8 @@
 
     <para>There are cases where you want to create a bridge to join two or
     more LAN segments and you don't need to restrict the traffic between those
-    segments. This is the environment that is described in this article.
-    </para>
+    segments. This is the environment that is described in this
+    article.</para>
 
     <para>If you do need to restrict traffic through the bridge, please refer
     to the <ulink url="bridge.html">Shorewall Bridge/Firewall
@@ -114,6 +114,11 @@ loc            <emphasis role="bold">br0</emphasis>             10.0.1.255     <
         <para>The <emphasis role="bold">routeback</emphasis> option is
         specified for <filename class="devicefile">br0</filename>.</para>
       </listitem>
+
+      <listitem>
+        <para>The default gateway for hosts in the local segments will be
+        192.168.1.254 — the IP address of the bridge itself.</para>
+      </listitem>
     </itemizedlist>
   </section>
 </article>
\ No newline at end of file