If you only have specific models in your environment, feel free to pick and choose which sections you include, as they're sorted out by which models use which OUI's
One word of caution though: these have not been tested for collisions with other vendors, so there could be some inadvertent overlaps as a result. I've tried to make the bitmasks as specific as possible, but I'm sure the risk is still there, so be aware of the potential confusion.
Done correctly, you should start seeing Meraki BSSID's showing up like this in Wireshark:
If you have any questions, concerns, or you notice anything wrong, please let me know!
(Edit) Modified the newest OUI to use a Windows-style hardware address for now to avoid it getting turned into an emoticon
Re: Some enhancements to Wireshark for easier troubleshooting
Nope, the OUI is 0C-8D-DB (to use a format our message board platform won't mangle); it shouldn't matter in either case though, because those lines are just comments - Wireshark doesn't process them at all.
Each of these is calculated rather differently depending on the underlying hardware platform, so the bitmasks are going to vary for each. The way the BSSID MAC's changed per-SSID also varies; on the older platforms, we'd increment the low-order bits rather than the high-order bits like we do on the newer platforms, and as a result, there are a lot more mask patterns I had to come up with for them.