I've never used it on Router OS, so I can't speak to that, but we use it between each POP and the BNG. Only real drawbacks that I see are: You need to be careful about MTUs. It is harder to use diverse geographically separated upstreams.
It makes life simple. We run a SVLAN over VPLS to each POP and then assign each customer a unique CVLAN on that SVLAN. The BNG dynamically creates the SVAN.CVLAN for the customer, authenticates them via radius, and assigns DHCP filters, routing instances, etc. We are still working on transitioning customers and POPs over but thus far it has been pretty painless. On Fri, Feb 17, 2017 at 3:29 PM, Jason McKemie < j.mcke...@veloxinetbroadband.com> wrote: > I'll have to catch up on some of those, just wondered what others had > found. > > On Fri, Feb 17, 2017 at 2:28 PM, Josh Reynolds <j...@kyneticwifi.com> > wrote: > >> There are a lot of NANOG presentations on this topic in Google. >> >> On Feb 17, 2017 2:27 PM, "Jason McKemie" <j.mckemie@veloxinetbroadband. >> com> wrote: >> >>> I'm starting to utilize MPLS/VPLS at the edge of my network for a >>> specific location, but am wondering if there is any reason to not just use >>> it all the way back to the core. What are the pros/cons of using MPLS? I >>> would think that you could save some public IPs if nothing else. >>> >>> Also, has anyone had any issues with MPLS/VPLS on the latest stable >>> RouterOS version (6.38.1)? >>> >>> -Jason >>> >> > -- Carl Peterson *PORT NETWORKS* 401 E Pratt St, Ste 2553 Baltimore, MD 21202 (410) 637-3707
