Friends,
Seeing a lot of UDP traffic (~6 mbps) from my HASSIO setup destined to addresses like 169.254.111.122, 169.254.169.95, and 169.254.22.2, port 50759. Any idea what this is and/or know how I can stop it? It’s been happening for a long time (several months and HA versions at least).
Edit: A reboot stops it for a short time and then it seems to slowly ramp back up to 6 mbps after a few hours.
HassOS 2.12
Home Assistant 0.96.5
Thanks,
Eric
I can’t tell you why it is happening, but all of those IPs are in the autoconfig range. (Devices set for dhcp that do not get a response from a dhcp server will pick one at random to use.)
Agreed, definitely. As to why it would be using this autoconfig address as a destination is a mystery to me still. I could see a hosted container failing to get an address and then it source something from an autoconfig address, but to see this level of blasted out UDP garbage to a destination that is an autoconfig is certainly strange.
Is anyone else seeing this kind of traffic load on their HASSIO setups? I’m betting this is common (because it’s happened even since a rebuild from scratch) but it might not be commonly known because most folks do not monitor their network with as much scrutiny.
I will continue to investigate. Next step may be to build a “DMZ” VLAN behind another router and isolate my IOT network. That will give me a lot more control than I have with my Xfinity router (I wouldn’t even run this piece of crap except my kids need the uPNP to work for their piece of crap Nintendo peer-to-peer… HEY NINTENO, 1990 called and they want their network stack back!)
Anyway, the isolated network will also give me more visibility with netflow and NBAR, so if I find out what the heck is going on I’ll share with you guys and submit a bug report if warranted.