# Tracked down a Fire TV Stick flooding the LAN with ~300 mDNS pkt/s, killing all Wi-Fi. Root cause, an NSEC responder, and on-device removal — retained record

> Retained reddit record from reddit:homelab.

Canonical: https://highsignal.app/data/records/31f238d7be584b08

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:homelab)  published 2026-09-29 16:41 ingested 2026-09-30 02:42

[original source ↗](https://www.reddit.com/r/homelab/comments/1wtf4vk/tracked_down_a_fire_tv_stick_flooding_the_lan/)

## retained text



```
This one took me a while so I figured I'd write it up. Every AP in the house died at once, 46 to 60% packet loss on wireless, while wired gigabit didn't blink. So airtime, not bandwidth.

Ran a tcpdump on port 5353:

sudo tcpdump -i <iface> -nn -e -c 3000 port 5353

One Fire TV Stick was firing AAAA queries at \~180/sec, which lands as \~300 pps of multicast on the segment. Multicast goes out at the lowest common rate to everyone, so it eats 2.4GHz airtime for the whole network.

Turns out the Stick keeps asking for the AAAA of a \*.fritz.box name, and the FRITZ!Box answers with an empty packet, 0 questions 0 records. Fire OS doesn't count that as an answer or as silence, so it never backs off and just retries forever. Amazon knows about it, it was reported 2026-07-28 and it's still open.  
What each fix did. At baseline it was \~300 pps and 46 to 60% loss. Killing the offending device brought it to \~1 pps and 0% loss. With the NSEC responder running it sat at \~0.1 pps and 0% loss.

The responder is a little stdlib-only Python thing. It answers the query with a proper negative reply (NSEC, "this name has no AAAA") plus the A record on the end, so the Stick negative-caches it (120s TTL) and shuts up. 12 replies killed 881 queries. Runs as a systemd unit, or procd on OpenWrt.

If you'd rather fix it at the source: temporary root with a build-pinned kernel exploit (CVE-2026-43499, no bootloader unlock, gone after a reboot), then pm uninstall the three WhisperLink packages that do the querying. The removal sticks across reboots even though root doesn't. After that: 3 mDNS packets in 15s, none from the Fire TV.

Full write-up with the whole script, the systemd unit, the stuff that didn't work, the kara vs karat codename gotcha, and the minimal fix I sent Amazon:

[https://nicologiuliani.site/blog/firetv-mdns-storm/](https://nicologiuliani.site/blog/firetv-mdns-storm/)
```



document fetched 2026-09-30 00:39 · canonical https://reddit.com/r/homelab/comments/1wtf4vk/tracked_down_a_fire_tv_stick_flooding_the_lan
