#jimz011 Multiple VLANs creates big mDNS
1 messages · Page 1 of 1 (latest)
wrong, there is NO mdns reflector available that can do IPv6 mdns forwarding properly. Some of them even flood the network with duplicated packets. Stay away from mdns forwarders, they have been crap for years and it will only get worse. Either seperate your network properly or dont do it at all. If there is a reason for forwarding mdns traffic at all, it means you are overcomplicating your setup.
There are only 2 good practices:
-
Flatten your network, if routing is needed between VLAN's you must ask yourself where to stop. Routing traffic that is supposed to be local (like mdns/neighbour discovery packets) these devices should be on the same (v)LAN, period.
-
Just add all devices to your IoT network and add HA also in the IoT network. Opening a TCP port to access HA is way easier (and failsafe) than mdns reflectors.
-
There is no 3 - remove that mdns reflector righht away if you want to prevent issues with chromecast groups, airplay devices and Matter and Thread.
Just to be clear, I wasn't using the mDNS reflector. All of my stuff is on a single LAN. But good to know the Firewalla mDNS reflector should not be used if one did have a more complicated LAN setup.
Some people have a flat network and still have that option enabled in their router console "just because it can be enabled"... 🙂 Hence my never ending quest to keep people from hitting that checkbox haha
I'm working up a blog post on Matter ...more of just an informational post on how to dig through some of the networking details like how you get the IPv6 address of a device out of home assistant, etc. I'll be sure to include a note about NOT using any mDNS reflectors.
and I want to check out the HAOS container routing tables and provide steps how to do that...given the info you guys provided here
it's not about troubleshooting per say..just more of FYI here's a way to find out some details about the network
Yeah, atm this is a little bit adventurous with debugging, hence I'm motivating less technical/experienced people to keep away from the DIY Thread router with the SkyConnect/Yellow until we finished our UI/UX flow with some actual helpful diagnostic info and clear guide to commission devices.