Something was definitely amiss somewhere in Meraki. The logs were not showing the filtered content for the instances we were referring to (they were correctly showing other events successfully filtered), but restarting all Meraki devices immediately resolved our issue. Pretty darn weird. We had a ticket open with Meraki Support that was very helpful, but their ultimate statement was that it couldn't be Meraki-related because whitelisting specific test devices didn't resolve the issue. That should have superseded any filtering by the device. That being said, restarting the devices took care of it. Just one of those inexplicable device brain farts that requires a reboot I guess!
... View more