Date: Wed, 13 Oct 2010 12:36:02 +0200 (CEST) From: sthaug@nethelp.no To: jon.otterholm@ide.resurscentrum.se Cc: freebsd-net@freebsd.org Subject: Re: SV: VPLS implementation Message-ID: <20101013.123602.41726980.sthaug@nethelp.no> In-Reply-To: <C44C550808114E4B9F4CF3FCA16F10A101019C0C@edusrv05.edu.irc.local> References: <4CB57781.1030402@gmx.com> <20101013.113223.74662610.sthaug@nethelp.no> <C44C550808114E4B9F4CF3FCA16F10A101019C0C@edusrv05.edu.irc.local>
next in thread | previous in thread | raw e-mail | index | archive | help
> > So the question is - *why* would you want FreeBSD to support VPLS? And > > what exactly do you mean by implementing VPLS on FreeBSD? If you want a > > multipoint bridge across several interfaces, this can be done. If you want > > something with MPLS support (labels etc) it's a completely different ball > > game. > > > I want to be able to interact with other vendors using VPLS. I am familiar with 802.1Q, if_bridge and if_gif and its possibilities. If you want to interact with other vendors using VPLS, you need, as far as I can see, a full MPLS/VPLS implementation. I know there is some Quagga support for MPLS on Linux, don't know about FreeBSD. In any case this is a much more complex scenario than simple bridging. Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101013.123602.41726980.sthaug>