i see it.  I had to widen my display   Thanks! ... View more

Hi @PhilipDAth,   That is correct.  ... View more

Try block port 80,443,53 on L3 rules. create group policies name internet access and allow 80,443,53 for the user to access the internet. Group policies override L3 rules. content filtering can be customized here too. ... View more

Hi @nadalfan1984,   As far as I know dynamic public IP can be used if both firewall are Meraki, since they are using the SDWAN technology feature called Auto VPN.   If ever the one of the firewall is a non-Meraki, I typically require that the non-Meraki has the static IP and supports DMVPN (Dynamic Multipoint VPN). Meraki MX can either have dynamic or static IP. Suggested also that the main branch should have a static IP and the branch can by dynamic.     Cheers!   Terry ... View more

Happy Birthday! ... View more

Cool. Let me know how it goes.  ... View more

For info:        It is a very capable device! ... View more

Not using VLAN 1 is pretty much the only suggestion since there is no VTP on Meraki so not to much benifit to staying inside standard VLAN range. But any VLAN you want to reach other side of MX you will need to configure in MX. Any switch you want to have ability to use VLAN will need VLAN configured. Layer3 switches you will also want to configure an interface so they can route packets between VLANS. Be sure not to reassign interface IPs when doing this. ... View more

Thanks, but all I'm really interested in is the individual AP advertising its name in the beacon.  Meraki chose to use the CCX extensions to do this.  Other products use the Vendor Specific information element to do it.  I don't really care, as long as it's advertised.   Having the AP name in the beacon makes it easier for site survey and other monitoring tools to report the name rather than just a MAC address. ... View more

Hahaha!!! That's the best way I guess 😛 ... View more

Hi Lubandw1, Since MX uses port 80 for its local page, try changing the DVR port. ... View more