From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1055b16f0706182034t581f9effr3bfd126fd5b7ba62@mail.gmail.com>
Date: Mon, 18 Jun 2007 23:34:44 -0400
From: "Artem Letko" <aletko@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan 9 bridging
In-Reply-To: <8fd450a6609094586f63a8f7d9b89920@coraid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1055b16f0706181510h6e17bc10maa2c43c73ed8208f@mail.gmail.com>
	<8fd450a6609094586f63a8f7d9b89920@coraid.com>
Topicbox-Message-UUID: 811abd94-ead2-11e9-9d60-3106f5b1d025

ok, i'm still not sure what you're trying to do but thought i'd
mention that bridge(3) is not something that implements an "Ethernet
bridge" as in ANSI/IEEE 802.1d

-art

On 6/18/07, erik quanstrom <quanstro@coraid.com> wrote:
> > i wonder what are you trying to do with bridge(3)
> >
> > -art
> >
> > On 6/18/07, erik quanstrom <quanstro@coraid.com> wrote:
> > > > Yes, there is now bridge(3).
> > > >
> > >
> > > thank you very much!  this will be tons easier than (mis)configuring linux.
> > >
> > > i assume that i will need to add jumbo support myself. ;-)
> > >
> > > - erik
>
> snoopy(1), eh? ;-)
>
> i need a simple jumbo-capable wide spot in the network.  snoopy+devbridge
> should do it.
>
> it seems it should be trivial adding jumbo support.
>
> - erik
>