Thank you - I will be doing some internal following-up to see if we need to file a bug report about this, because I'm not sure where that errant NBAR classifier is coming from if it's not defined under the previously referenced protocol pack documentation.
We have this issue as well, was blocking RDP traffic and DNS traffic. It flagged it as random things, like P2P. We had to disable most L7 rules for it to go away. Support recommended we upgrade to the latest firmware, but it had no notes about NBAR so we declined.
I would also like to recommend that Meraki add more ways to Whitelist NBAR. It's a real pain to have to create group policies for devices and lose our 2 way MX firewall rules. As a school, we can't realistically turn off Peer to Peer and NBAR blocks too many false positives.
i just went to 16.16 on several networks in an organization and am seeing it misclassify internal and external DNS traffic, and internal Avaya IP Office to IP Office traffic as well. And for good measure, some internet based line of business applications for a health care facility.
Would be great to be able to more knobs related to NBAR. My choices today seem to be able to remove l7 rules for all social media to make dns work. I must be missing some docs
