From J.Kois@web.de  Thu May  1 06:03:11 2003
Return-Path: <J.Kois@web.de>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8861D37B401; Thu,  1 May 2003 06:03:11 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B10B343F3F; Thu,  1 May 2003 06:03:10 -0700 (PDT)
	(envelope-from J.Kois@web.de)
Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 19BDiO-0001VC-00; Thu, 01 May 2003 15:03:08 +0200
Received: from [80.128.5.131] (helo=p50800583.dip0.t-ipconnect.de)
	by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
	id 19BDiO-00026z-00; Thu, 01 May 2003 15:03:08 +0200
Message-Id: <200305011503.09378.J.Kois@web.de>
Date: Thu, 1 May 2003 15:03:09 +0200
From: Johann Kois <J.Kois@web.de>
To: FreeBSD-gnats-submit@freebsd.org
Cc: murray@freebsd.org
Subject: [PATCH] - PR docs/50665 - fix suggestion

>Number:         51658
>Category:       docs
>Synopsis:       [PATCH] - PR docs/50665 - fix suggestion
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 01 06:10:15 PDT 2003
>Closed-Date:    Sun May 04 14:23:19 PDT 2003
>Last-Modified:  Sun May 04 14:23:19 PDT 2003
>Originator:     Johann Kois
>Release:        FreeBSD 4.7-RELEASE i386
>Organization:
>Environment:
System: FreeBSD 4.7-RELEASE FreeBSD 4.7-RELEASE #2 : Tue Dec 10 12:26:58 CET 2002, rta0043@MEIDESKTOP:/usr/src/sys/compile/FREEBSD i386
>Description:
 Fix suggestion for PR docs/50665
 paragraph does not use first person any longer and has moved to "other information"
 paragraph enclosed in <example>-tag.
>How-To-Repeat:
 Read handbook section 19.4.5
>Fix:
diff-file:
--- begin of diff-file: ---
--- chapter.sgml: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.208 ---
=================================================================================================
diff -u chapter.new.sgml chapter.sgml
--- chapter.sgml	Mon Apr 28 09:06:55 2003 v 1.208
+++ chapter.new.sgml	Thu May  1 13:07:52 2003
@@ -1061,19 +1061,7 @@
 
       <para>as well.</para>
     </sect2>
-
-    <sect2>
-      <title>Performance</title>
-
-      <para>My bridge/firewall is a Pentium 90 with one 3Com 3C900B
-	and one 3C905B.  The protected side of the network runs at
-	10&nbsp;mbps half duplex and the connection between the bridge
-	and my router (a Cisco 675) runs at 100&nbsp;mbps full duplex.
-	With no filtering enabled, I have found that the bridge adds
-	about 0.4&nbsp;milliseconds of latency to pings from the
-	protected 10&nbsp;mbps network to the Cisco 675.</para>
-    </sect2>
-
+    
     <sect2>
       <title>Other Information</title>
 
@@ -1085,6 +1073,23 @@
       <para>If you have multiple bridges on your network, there cannot be more
 	than one path between any two workstations.  Technically, this means
 	that there is no support for spanning tree link management.</para>
+
+      <para>A bridge can increase the reaction times in your network by
+        adding a lateny to your ping times, especially for traffic from
+        one segment to another. 
+      
+        <example>
+          <title>Increased ping times caused by a bridge</title>
+        
+          <para>A bridge/firewall was tested on a Pentium 90 with one
+            3Com 3C900B and one 3C905B.  The protected side of the network
+            ran at 10&nbsp;mbps half duplex and the connection between the
+            bridge and the router (a Cisco 675) ran at 100&nbsp;mbps full
+            duplex.  With no filtering enabled, the bridge added about
+            0.4&nbsp;milliseconds of latency to pings from the protected
+            10&nbsp;mbps network to the Cisco 675 router.</para>
+        </example>
+      </para>
     </sect2>
   </sect1>


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: murray 
State-Changed-When: Sun May 4 14:21:03 PDT 2003 
State-Changed-Why:  
Thanks for the submission.  An <example> isn't really appropriate for 
this testimonial either, as it could then show up in the list of 
examples after the table of contents and the assumption is that it 
generally provides a procedure that can be followed to accomplish a 
task. 

latency was mispelled once in this patch, so I fixed this and 
simplified the sentence about the bridge adding latency to ping times. 
I think that is all that is really required now that I think about it. 
It's a more useful statement than the Pentium 90 numbers that show the 
latency that was added. 

It may be up to 24 hours before this change is available on the web site. 

Thanks! 


http://www.freebsd.org/cgi/query-pr.cgi?pr=51658 
>Unformatted:
 >Submitter-ID:  current-users
 >Organisation:  n/a
