From owner-freebsd-doc@FreeBSD.ORG  Tue Oct 21 04:42:43 2003
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1D4F816A4B3
	for <doc@FreeBSD.org>; Tue, 21 Oct 2003 04:42:43 -0700 (PDT)
Received: from kogut.o2.pl (kogut.o2.pl [212.126.20.60])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CD0E343FCB
	for <doc@FreeBSD.org>; Tue, 21 Oct 2003 04:42:41 -0700 (PDT)
	(envelope-from rc1977@o2.pl)
Received: from 192.168.2.9 (wojciech.wssk.wroc.pl [156.17.61.26])
	by kogut.o2.pl (o2.pl Mailer 2.0.1) with ESMTP id 767D51A33CA
	for <doc@FreeBSD.org>; Tue, 21 Oct 2003 13:42:35 +0200 (CEST)
Date: Tue, 21 Oct 2003 13:51:21 +0200
From: =?Windows-1250?B?UmFkb3OzYXcgQ2ljaHk=?= <rc1977@o2.pl>
X-Mailer: The Bat! (v1.62 Christmas Edition) Personal
Organization: SR Ltd.
X-Priority: 3 (Normal)
Message-ID: <7213362559.20031021135121@o2.pl>
To: doc@FreeBSD.org
MIME-Version: 1.0
Content-Type: text/plain; charset=Windows-1250
Content-Transfer-Encoding: 8bit
Subject: Bug in article.
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: =?Windows-1250?B?UmFkb3OzYXcgQ2ljaHk=?= <rc1977@o2.pl>
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Oct 2003 11:42:43 -0000

Hello

I've found bug in article "Filtering bridges"

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/filtering-bridges/article.html

In Chapter 4 "Enabling the Bridge" has been written :

# sysctl net.link.ether.bridge_cfg=fxp0:0,xl0:0
# sysctl net.link.ether.bridge_ipfw=1
# sysctl net.link.ether.bridge=1

But bridge configuration should be done AFTER bringing it UP (and that agrees to
manual for bridge module).

I spend 3 days doing it this way before I caught the bug :)

Greetings from Poland
Radek Cichy

BTW: In polish translation of this article there's bug too.