From owner-freebsd-current@FreeBSD.ORG Tue May 18 16:12:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC3E16A5E3 for ; Tue, 18 May 2004 16:12:22 -0700 (PDT) Received: from backmaster.cdsnet.net (backmaster.cdsnet.net [63.163.68.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 5FD4843EDC for ; Tue, 18 May 2004 15:51:58 -0700 (PDT) (envelope-from mrcpu@backmaster.cdsnet.net) Received: (qmail 47950 invoked by uid 29999); 18 May 2004 22:49:18 -0000 Date: Tue, 18 May 2004 15:49:18 -0700 From: Jaye Mathisen To: current@freebsd.org Message-ID: <20040518224917.GA6273@backmaster.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: Limitations of -curent Bridinging... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2004 23:12:30 -0000 WHat exactly is the issue (besides no loop detection support) in 5.x? I was going to use 5.x as a bridge between my main router and the rest of my network, mainly for trafshow/iftop type stuff. Of course, I want the ability to ipfw on it as well, if I need to, and possibly traffic shape with dummynet. Possibly snort as well, although I'm not sure. If I can't do that, then will Netgraph work, and give me something that I can actually filter with? Or do I need to switch BSD's and go with Open for this project, because their bridging code has some function that I'm not comprehending (besides STP). Is there anything wrong with this plan?