Date: Wed, 13 Oct 2010 10:07:31 -0700 From: Julian Elischer <julian@freebsd.org> To: sthaug@nethelp.no Cc: freebsd-net@freebsd.org, jon.otterholm@ide.resurscentrum.se Subject: Re: SV: VPLS implementation Message-ID: <4CB5E753.5080709@freebsd.org> In-Reply-To: <20101013.123602.41726980.sthaug@nethelp.no> References: <4CB57781.1030402@gmx.com> <20101013.113223.74662610.sthaug@nethelp.no> <C44C550808114E4B9F4CF3FCA16F10A101019C0C@edusrv05.edu.irc.local> <20101013.123602.41726980.sthaug@nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/13/10 3:36 AM, sthaug@nethelp.no wrote: >>> 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 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > this is pretty much what netgraph was developed for. you can make a node that implements just the control part of VPLS and use the netgraph framework to hook it all together.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CB5E753.5080709>