From owner-freebsd-net Mon Jan 29 15:53:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from hera.drwilco.net (10dyn120.dh.casema.net [212.64.31.120]) by hub.freebsd.org (Postfix) with ESMTP id 60AA037B6A3; Mon, 29 Jan 2001 15:53:17 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0U0Fcb05888; Tue, 30 Jan 2001 01:15:38 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010130001851.00aed910@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 30 Jan 2001 00:21:51 +0100 To: Erwan Arzur , Roman Le Houelleur From: "Rogier R. Mulhuijzen" Subject: Re: bandwidth analyser Cc: freebsd-ipfw , freebsd-net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Use the ng_bridge node if you want to have precise control over which interfaces are being bridged. Another thing, be careful when you enable the netgraph node when you have BRIDGE compiled into your kernel. 2 reasons: 1) if you have the bridging code activated you'll get broadcast loops resulting in links being deactivated and whatnot. 2) when you have the bridging deactivated you'll run into some nice problems due to this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=24720 (patch included). Nothing earth shattering, but when you alter your setup in anyway some machines suddenly become unreachable until the arp tables age out on them.... DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message