Thank you for highlighting this issue—it's clearly affecting a lot of us. There must be hundreds of printers that are not working for customers because of the default "public" SNMP community string being blocked by Snort rule 1-1412 after the January 28, 2026 update. This is a major problem that Meraki needs to address promptly, especially since out-of-the-box printers on separate VLANs will run into the same snag if the rule is enabled, and many admins won't immediately know why printing fails. It's leading to significant time wastage troubleshooting what turns out to be a false positive in legitimate environments. While whitelisting the rule works as a temporary fix, the lack of proactive communication from Meraki has been frustrating. Can we get an update from engineering on the status of a permanent resolution? Also, what steps have been taken so far to inform customers about this—such as alerts, dashboard notifications, or knowledge base articles—to prevent more widespread disruption?
... View more