Likely the manufacturer has their own Camera app installed in place of the native Android one, you'll need to find the package name and create an app blacklist rule. ... View more

Thanks to all for replying, I didn't receive notification of thread replies hence the delay.   It sounds like in my structure, I might be better off having each switch do its own thing (multiple VLANs), since I can't logically break out the areas to have one or two core switches.  ... View more

You should try using it with non-Cisco gear, 1.1.1.1 works extremely well and resolves super fast... except with Cisco/Meraki. Why? Because Cisco has, over the years, improperly treated 1.x.x.x. as fair game for their own uses.   https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-globally/   Who else has been mis-using 1.1.1.1 more than others? Using the RIPE Atlas probes gives excellent visibility into residential and business internet connections, however they’re connected via a cable, so this rules out another use-case, WiFi access points. After very little research we quickly came across Cisco mis-using 1.1.1.1, a quick search for “cisco 1.1.1.1” brought up numerous articles where Cisco are squatting on 1.1.1.1 for their Wireless LAN Controllers (WLC). It’s unclear if Cisco officially regards 1.0.0.0/8 as bogon space, but there are lots of examples that can be found on their community websites giving example bogon lists that include the /8. It mostly seems to be used for captive portal when authenticating to the wireless access point, often found in hotels, cafés and other public WiFi hotspot locations.   ... View more

Don't worry, according to the earlier post they're just 3 or 4 months away!.... from maybe announcing a possible roadmap for future development... maybe.    (Of course, as is the custom, it'll only be in restricted beta firmware for 12-18 months after a year of development) ... View more

Layer 2 isolation is only in bridge mode, not Meraki NAT mode, so there you go.   You could turn on Meraki NAT so everyone gets an isolated subnet to themselves, and then add an ACL to permit traffic to just the printer IP address on the LAN, and then a Deny statement for everything else on the local LAN. That will work.   ... View more

@RH6379 wrote: We're installing 12 MS-120 switches in a remote office and the switches are showing a DNS misconfigured error when we use the IP of the mgmt vlan as the DNS Server.  That is configured on an MX84.  Is your MX84 not configured as a DNS proxy perhaps? If it's not relaying and returning DNS queries and responses for clients, then the switch isn't going to connect either. ... View more

That, plus lack of access to debug logs, are the two main shortcomings of the Meraki MX line in my opinion. As long as you know what you're getting, they're fine, but certainly not perfect.   Oh, and the third thing -- reliance on junky native IPSEC VPN client. Even though customers have begged for Anyconnect since the Cisco acquisition years ago.  ... View more

I like the MX line for what it is, but it's never struck me as even close to real "enterprise" class, despite what the marketing department says. ... View more

None of that is in the Meraki platform. ... View more