From owner-freebsd-arch@FreeBSD.ORG Wed Aug 20 10:54:05 2003 Return-Path: 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 6FDCD16A4BF; Wed, 20 Aug 2003 10:54:05 -0700 (PDT) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0953443FA3; Wed, 20 Aug 2003 10:54:03 -0700 (PDT) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h7KHqlj31005; Wed, 20 Aug 2003 14:52:47 -0300 Message-ID: <3F43B56E.1070100@tcoip.com.br> Date: Wed, 20 Aug 2003 14:52:46 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030702 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Lars Eggert References: <510776858.1061372094@melange.errno.com> <3F43AFFD.6080504@isi.edu> In-Reply-To: <3F43AFFD.6080504@isi.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Sam Leffler cc: freebsd-arch@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: CFR: bridge locking X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2003 17:54:05 -0000 Lars Eggert wrote: > Sam Leffler wrote: > >> http://www.freebsd.org/~sam/bridge.patch >> >> This patch adds locking and also overhauls the bridge code some to do >> things like replace explicit numbers with #defines and cleanup the >> debugging code. > > > This is only mildly related, but maybe someone feels like looking at > this in addition to your locking changes... > > I have a PR about the bridge code sitting at > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/41632; the latest patch > is at http://www.isi.edu/larse/software/bridge.patch > > It does two things: > > 1. Disables bridging for IPv6. This is probably too aggressive, > since bridging is only problematic for link-local packets, but it > makes a routed IPv6 configuration coexist with a bridged IPv4 one. > > A much better fix would be an overhaul of the bridge code so that > each bridge has a single link-local address, instead of one per > physical interface. (Similar to how it should/must only have one IPv4 > address, but link-locals are auto-assigned.) Essentially, make > a bridge set its own pseudo interface. > > 2. It forwards a copy of bridged packets to bpfs attached to interfaces > in the bridge set that have no carrier. This makes dhcpd work on an > interface of a bridge set that is unplugged. > > Again, a much better fix would be to have bridge sets show up as > pseudo interfaces that dhcpd's bpf can then listen on. If you get bridge to send/receive packets to/from vlan interfaces attached to them, I'll be forever grateful. I've been trying to configure a setup where a firewall is connected to redundant switches, but no solution I found could handle the vlan attachments. :-( -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Many pages make a thick book.