Re: CFR: bridge locking

From: Daniel C. Sobral (dcs_at_tcoip.com.br)
Date: 08/20/03

  • Next message: Robert Watson: "Re: CFR: bridge locking" 
    Date: Wed, 20 Aug 2003 14:52:46 -0300
To: Lars Eggert <larse@ISI.EDU>

    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.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Robert Watson: "Re: CFR: bridge locking"

    Relevant Pages

    • UPDATE: New Mozilla SpiderMonkey bridge code release
      ... The bridge code has undergone its final large renovation. ... Javascript objects in real-time from both Delphi/Kylix and script. ...
      (borland.public.delphi.thirdpartytools.general)
    • Re: CFR: bridge locking
      ... >> This patch adds locking and also overhauls the bridge code some to do ... It forwards a copy of bridged packets to bpfs attached to interfaces ... > in the bridge set that have no carrier. ...
      (freebsd-net)
    • Re: CFR: bridge locking
      ... this in addition to your locking changes... ... I have a PR about the bridge code sitting at ... a bridge set its own pseudo interface. ...
      (freebsd-arch)
    • Re: CFR: bridge locking
      ... > If you use netgraph bridging then you are using a more ... >>required some cleanup of the interactions between the bridge code and IPFW ... The penalty for laughing in a courtroom is six months in jail; if it were not for this penalty, the jury would never hear the evidence. ...
      (freebsd-arch)
    • Re: CFR: bridge locking
      ... this in addition to your locking changes... ... I have a PR about the bridge code sitting at ... a bridge set its own pseudo interface. ...
      (freebsd-net)