I did not mean to make anyone bow! You were right from start to end according to official documentation.(Now I kinda feel like a J*rk) I just wanted to make sure we all are on same page... ... ... and depending on my lab result ...All (me included) bow to @Ryan_Miles ...:D ... View more

So I'd like to thank you very much for your answer. So I would have avoided bothering any of you if following documentation (doc 1 below) is somewhat (complete from my perspective) contradiction with other documentation (doc2 below)  and with your very clear answer. doc 1: Extending the LAN with a Wireless Mesh Link - Cisco Meraki should be updated by doc 2: Mesh Deployment Guide - Cisco Meraki and ryan answer. so in visual: I suspect that this multi Vlan function is not very well known looking on the different thread I read before writing my ow. @GreenMan  could also provide an updated opinion (or not) . anyway thank you all I'll provide results. ... View more

So M. Greenman in case I need to extend 2 vlans to a remote (13m) location if clients contraints me to have same broadcast domain would this architectcure be valid? Inspired from the most basic first example from said documentation to extend L2 vlan 😄         ... View more

First thank you very much for such detailed and (sadly) clear feedback. I agree that documentation did specify the LAYER 3 MS on far right... I did not want to read that transit Bridge would not send any tagged frame 😄   But to be honest I wrongly suspected that documentation was not fully updated since following multivlan update: (source: https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Extending_the_LAN_with_a_Wireless_Mesh_Link ) Last question: looking @ this : Transit vlan (here VLAN2 20)  cannot be defined as an exiting one to extend left side L2VLAN /Broadcast domaine... L3 routing is looking at your answer mandatory. Bummer    ... View more