Thanks  ... View more

Changed mx lan port to. "Drop untagged traffic" and now that works fine - THANKS A follow up if you don't mind?  I assume if I map a port on the mr36 to an SSID, traffic that comes in on that port will be tagged in the VLAN associated to the SSID- correct? ... View more

Thanks. I'll give that a try when I get back to my desk later today.  Since I want to run multiple ssids each in a separate VLAN, I assume the first of your two suggestions is the way to go? By the way, just out of curiosity, I'm wondering why the default for the lan port couldn't be the same?  Any going to try later today. Thanks ... View more

I corrected SSID FW issue and MX port issue and returned to “external DHCP” on wireless config (as I want MR clients to get DHCP leases from the MX - which I believe appropriate for running multiple vlans?). Now I get an address / connection to MR – but no internet connection. Advice? ... View more

Physical config:  Client - to MR36 - to MX67 - to Comcast Logical config:  SSID on MR maps to VLAN 1.  Address assignment on MR set to "external" - as I want to use DHCP on MX - not MR.  Fails... If I change to Meraki "AP assigned" - things work - but that's not what I had wanted - as I want to use multiple vlans in the network - which I belive means I need to use DHCP from MX - not from MRs - correct? ... View more

Never mind - Found my answer: MR36H will use a 4-Port profile (same as MR30H), however, port 4 of the profile will not be used since the port does not exist on the AP. For more information about MR36H ports please visit installation guide. ... View more

Dashboard view:       ... View more