Date: Wed, 16 Jan 2002 00:35:58 +0100 From: "Rogier R. Mulhuijzen" <drwilco@drwilco.net> To: Julian Elischer <julian@elischer.org> Cc: freebsd-net@freebsd.org Subject: Re: bridged interfaces don't see broadcasts Message-ID: <5.1.0.14.0.20020116003008.02a4d650@mail.drwilco.net> In-Reply-To: <Pine.BSF.4.21.0201151456530.82675-100000@InterJet.elischer .org> References: <20020115224933.GB3520@frolic.no-support.loc>
next in thread | previous in thread | raw e-mail | index | archive | help
the 'all' mode on one2many maybe?
Doc
At 14:58 15-1-2002 -0800, you wrote:
>ok..
>I'll see if I can come up with a way to hook multiple netgraph nodes to an
>ethernet node...
>(but since my daughter was born yesterday I'm a little deistracted at the
>moment :-)
>
>julian
>
>
>On Tue, 15 Jan 2002, Bjoern Fischer wrote:
>
> > Hello Julian,
> >
> > > What happens if you use netgraph bridging?
> > > (/usr/share/examples/netgraph)
> >
> > I knew that you would advertise this ;-)
> >
> > Ok, since I'm already using netgraph for pppoe on the same machine,
> > I tried netgraph bridging at first. But with netgraph bridging it
> > was even worse: Not even the clients on the vr0 segment could reach
> > the server via broadcast (192.168.43.255). All our production
> > workstations are on this segment. All of them are diskless clients
> > using DHCP, amd with NIS maps, NIS for user DBs; so that broadcast
> > feature was heavily needed.
> >
> > With Luigi's bridging code at least the vr0 segment was working
> > normally. Only the broadcast problem on the ed1 segment. I could
> > live with that up till now.
> >
> > -Bj=F6rn
> >
> >
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-net" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20020116003008.02a4d650>