From owner-freebsd-arch@FreeBSD.ORG Tue Oct 4 19:09:46 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAC8716A41F for ; Tue, 4 Oct 2005 19:09:46 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F3A643D45 for ; Tue, 4 Oct 2005 19:09:46 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 04 Oct 2005 12:09:46 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id j94J9kxp093233; Tue, 4 Oct 2005 12:09:46 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id j94J9jvd093228; Tue, 4 Oct 2005 12:09:45 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200510041909.j94J9jvd093228@ambrisko.com> In-Reply-To: <20050925002212.GA77857@heff.fud.org.nz> To: PeterJeremy@optushome.com.au Date: Tue, 4 Oct 2005 12:09:45 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-arch@freebsd.org Subject: Re: Bridges X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 19:09:47 -0000 On Sun, Sep 25, 2005 at 05:22:38AM +1000, Peter Jeremy wrote: > On Sat, 2005-Sep-24 15:25:06 +0200, Max Laier wrote: > >for some time now, we have three bridge implementations in the tree: > > - net/bridge.c - the "old" bridge > > - net/if_bridge.c - the "new" bridge from Net/OpenBSD > > - netgraph/ng_bridge.c - the netgraph version [1] > > > >The new code has several advantages over the old version: > > - Spanning Tree Protocol (802.1D) > > - better firewall support (IPv6, stateful filtering, ...) > > - easy ifconfig(8) configuration > > Since I've recently needed it, neither bridge.c nor if_bridge.c allow > you to bridge VLAN trunks (you can bridge individual VLANs but that > becomes unwieldly when you have dozens of VLANs). I have code to do > this in bridge.c. I think I ran into the related problem. The vlan device calls IFQ_HANDOFF directly versus the "normal" output bits so you can't use netgraph etc. I broke up ether_output so that I could call the stuff that ether_output does so it would go through netgraph hooks if configured. Doug A.