Date: Tue, 15 Jan 2002 23:49:33 +0100 From: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE> To: Julian Elischer <julian@elischer.org> Cc: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>, freebsd-net@FreeBSD.ORG Subject: Re: bridged interfaces don't see broadcasts Message-ID: <20020115224933.GB3520@frolic.no-support.loc> In-Reply-To: <Pine.BSF.4.21.0201151407090.82675-100000@InterJet.elischer.org> References: <20020115212056.GA3520@frolic.no-support.loc> <Pine.BSF.4.21.0201151407090.82675-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020115224933.GB3520>