Best bridging tunnel protocol for scalability?

We have several independent Mikrotiks deployed across a resort town, each running its own hotspot.
As the number of sites has increased, managing them all has gotten to be quite a headache.

I’ve been considering the use of a centralized hotspot server, and converting the individual sites into tunnel endpoints.

In order to eliminate the usual problems with a single large broadcast domain, we would use split horizon on a bridge interface of the central hotspot Mikrotik, as well as some basic bridge filtering at the individual sites to eliminate wasted throughput on the tunnels themselves.

My question is this - what sort of tunnelling protocol would be the most scalable as far as CPU resources on the concentrator/hotspot Mikrotik? I’ve built this for one site using an EoIP tunnel, but am concerned that after only a dozen or so sites, the centralized box would be getting its CPU hammered. (we have hundreds of sites currently)

Would the use of MRRU+BCP+PPP+L2TP be less resource intensive than simply creating EoIP tunnels?
Hotspot Aggregation.png

VPLS

That would definitely be the Cadillac. Unfortunately, we don’t have MPLS deployed in our core, and I’m not sure I’m knowledgable enough with it to do so at this time.

What would be the runner up?

I would go with EoIP. It is nice and simple and it scales reasonably well.

VPLS will be much easier to maintain for larger numbers of endpoints as it can autoconfigure via BGP signalled vpls.