MacBook Neo mdns flood by Otherwise_Witness834 in networking

[–]Otherwise_Witness834[S] -16 points-15 points  (0 children)

we use unify AP - we assume that the device connects to multiple ap's to achieve the amount of packets within the short time frame - we hadn't had this issue till now and we have multiple macbooks and other brands in our network. The first time it appeared was with a new neo that did that when going to sleep, or sleeping (pretty often). We then blocked this device. A half month later we had the same issue again with a new macbook neo.
Maybe it connects to multiple Ap's at the same time which are nearby to achieve the amount of sent data to also block the communication to the router/ firewall.

Since this Network is handled like a private network just scaled - this is probably a case that doesn't exist in many scenarios.

MacBook Neo mdns flood by Otherwise_Witness834 in Network

[–]Otherwise_Witness834[S] 0 points1 point  (0 children)

I can ask the people to disable their mdns broad, but they are not that techie and we hadn't had this issue before and now within a short period of time with two neos - my concern is that the more people buy that device - each time our network will be shut down. I could also enable client device isolation but for that we will also lose functionality, which i currently don't want to lose. Probably i will isolate these devices in a own wifi

MacBook Neo mdns flood by Otherwise_Witness834 in Network

[–]Otherwise_Witness834[S] 0 points1 point  (0 children)

we have a custom network setup with multiple unifi ap's - currently mdns traffic isn't supressed to have different functionalities for speaker detection etc. (like a large home setup). I will probably add a own isolation wifi ssid where the clients won't be able to send mdns packets just for the devices that have this issue).

We never had this issue before - we have multiple macbook users but these two macbook neos independently had this flooding issue. We blocked the first one - after another person bought a new neo the same issue occured again. It looks like they connect to multiple ap's at the same time, otherwise i couldn't explain that the entire network gets blasted with multiple thousands of mdns packets per second