Date: Mon, 1 Oct 2001 14:05:55 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: "Jasper O'Malley" <jooji@nickelkid.com> Cc: freebsd-net@freebsd.org Subject: Re: Netgraph bridging: what is LOCAL_IFACE? Message-ID: <Pine.BSF.4.21.0110011356010.87441-100000@InterJet.elischer.org> In-Reply-To: <Pine.BSF.4.21.0110011454150.37593-100000@cornflake.nickelkid.com>
next in thread | previous in thread | raw e-mail | index | archive | help
All the interfaces specified will stop working as normal interfaces, as their lower halves will be disconnected from their upper halves.. in other words the lower 'physical' part is run without any connection to the normal networking layer.. The bridging code (netgraph bridging) takes over this function instead. I think that if you send out a packet on one of these interfaces it may still make it out because we don't actually (last time I checked) bother to disconnect that, but all incoming packets will be passed to the bridge module, which will be keeoping track of MAC addresses and doing bridging as required.. Now, if you want to be on that bridged network as well, then you need to nominate which of the NICS should be your representative on that bridged network. The TOP part of that NIC (the bit you assign addresses to) will be joined into the bridging set, just like all the other NICS (logically there is no difference). The bridging code will send it a copy of any packets that have it's MAC address as destination and broadcast packets, just as it would any other segment.. Theoretically wo should remove teh bridged NICs from the ifconfig list but that would be too much work. Basically your NIC is just treated like another bridged segment, but with only one known node on it.. On Mon, 1 Oct 2001, Jasper O'Malley wrote: > On Mon, 1 Oct 2001, Julian Elischer wrote: > > > If you want any of these packets to also be passed to the local machine > > you should select one of the local interfaces (any will do) and add it in > > the LOCAL_INTERFACE entry. This entry specifies to the bridging code that > > the upper (i.e. KERNEL side) of that interface should also be added to the > > list of recipients of the packets being worked on. > > > > If you do not do this, the interfaces are linked to each other by the > > bridging code, but the local machine is not party to the traffic. No copy > > of the packets is sent up to it.. (this is a vaild configuration...) > > Ah. So you can't ifconfig the virtual bridge interface (e.g. bnet0) and > configure IP protocol information on it, then? > > If not, I misunderstood how the bridge interface behaves. I was thinking > that it acted more or less like a BVI interface does on a Cisco router. > Specifying the LOCAL_INTERFACE will work for me, though. Thanks. > > Cheers, > Mick > > 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?Pine.BSF.4.21.0110011356010.87441-100000>