Hi JorgeB. I’ve have also done some testing and I believe I’ve isolated the source to a scheduled UniFi gateway process. Environment: - Gateway: UCG Fiber - UniFi OS: 6.0.10 - UniFi Network: 10.6.106 - Unraid server: Antharas - Antharas LAN IP: 192.168.1.20 - Antharas also has 192.168.2.20 on the IoT VLAN - UniFi mDNS Proxy was originally set to Auto I first performed the test you suggested and disabled UniFi mDNS Proxy. The Avahi warnings continued at the same approximately once-per-minute interval, so disabling the configurable mDNS Proxy did not stop the queries/warnings. I subsequently restored mDNS Proxy to its original setting. I also temporarily restricted the Unraid Avahi configuration from: allow-interfaces=br0,br2.2 to: allow-interfaces=br0 and restarted Avahi. The warnings still occurred, so having Avahi active on both the LAN and IoT VLAN was not the cause. I restored the original interface configuration afterward. I then captured the traffic directly on the UCG. This showed the gateway sending queries from 192.168.1.1 to 224.0.0.251:5353 using ephemeral UDP source ports and with the QU bit set, requesting unicast replies. The timing is particularly interesting. At xx:xx:06, I captured a gateway query containing exactly: device-info.tcp.local sftp-ssh.tcp.local smb.tcp.local ssh.tcp.local At that same :06 second, Antharas logs the corresponding: not fitting in legacy unicast packet, dropping messages for sftp-ssh and device-info. This behaviour repeats every minute. So the :06 timing of the gateway discovery query and the Unraid Avahi warnings correlates exactly. I initially investigated the UCG's normal avahi-daemon. One of its persistent high UDP ports was involved in a larger discovery query, but I completely terminated the UCG Avahi daemon and confirmed its PID was gone. Antharas still produced the warnings at the next :06. Therefore the UCG's normal Avahi daemon was not required to trigger the issue. I also stopped /usr/bin/uos-discovery-client as a diagnostic test. The warnings continued. Rebooting the UCG Fiber also did not change the behaviour. I then monitored short-lived UDP sockets/processes on the UCG and found a process being launched approximately once per minute: /usr/sbin/ubntmdnsd Example command line: /usr/sbin/ubntmdnsd -t10 -f /tmp/mdns_services.json -c /data/udapi-config/mdns.cache -s -j -b -u -e meshcop,trel I found what launches it: /etc/cron.d/mdns-job contains: * * * * * root /usr/sbin/ubntmdnsd -t10 -f /tmp/mdns_services.json -c /data/udapi-config/mdns.cache -s -j -b -u -e meshcop,trel So the UCG is explicitly launching ubntmdnsd once every minute. I then inspected /tmp/mdns_services.json. It includes, among many other services: device-info.tcp sftp-ssh.tcp smb.tcp ssh.tcp Those are the same four services in the gateway query captured at :06. Finally I performed an A/B test. I temporarily renamed: /etc/cron.d/mdns-job to: /etc/cron.d/mdns-job.disabled I left Unraid Avahi running and made no other changes. The once-per-minute Avahi warnings stopped completely. I then restored /etc/cron.d/mdns-job, since it is a UniFi-managed component and I did not want to leave the gateway modified. So at this point the chain appears to be: UCG Fiber cron (every minute) → ubntmdnsd → QU mDNS discovery query → Antharas Avahi legacy-unicast response → not fitting in legacy unicast packet, dropping warnings at :06. The configurable UniFi mDNS Proxy being Off does not stop ubntmdnsd from performing this discovery. I have also raised this with Ubiquiti support and they have escalated the case, but I have not yet received a response from their escalation team. If useful, I can provide the packet captures showing the gateway query at :06, the corresponding Unraid syslog from the same time, /tmp/mdns_services.json, or repeat a synchronised capture/syslog test.