It's the client page in the Meraki Portal ... View more

Try doing a packet capture on port 53 (DNS) and then start it up.  Make a note of the DNS entries it uses (particularly any it might use to login).   Block access to those DNS entries. ... View more

Thank you ... View more

Is that correct?   I've never tested but I always assumed that for group policies applied to a VLAN, the bandwidth limit is just applied to each client in that VLAN, not split between the clients.   I can't find any official doc that explains the expected behaviour, only blogs posts and Reddit articles which have people in both camps 😅 ... View more

Thanks @alemabrahao . I was searching for Application ID filtering like the portals offered by PaloAlto Checkpoint in which we can check applications. ... View more

Thanks @GIdenJoe  ... View more

We are running firmware MX 16.16, the public ip is now reachable now, We had subjected device to a reboot. ... View more

I don't believe there are any such alerts. ... View more

Thank you Brash.   ... View more

Actually i tried via different browser and it worked out, thank you for the suggestion. ... View more

Thanks @BlakeRichardson  ... View more

I am using  Meraki MX 250 appliance with OS as MX 16.16, actually i was planning to block 3rd part VPN from L7 firewall rules. Thank you for the info. ... View more

Sure. You'll find the health status directly on the start page of the Dashboard and also on the device status page. By using live tools, you can also check throughput to the Dashboard: https://documentation.meraki.com/MX/Monitoring_and_Reporting/Appliance_Status   Usage can be found too: https://documentation.meraki.com/MX/Monitoring_and_Reporting/Device_Utilization ... View more