3 ms·
By debugging I mean just checking if you have not blocked broadcast packets at the firewall or some similar misconfiguration. I doubt it’s actual bugs when it d
by guntars 6mo ago
By debugging I mean just checking if you have not blocked broadcast packets at the firewall or some similar misconfiguration. I doubt it’s actual bugs when it doesn’t work. On your second point, it’s actually more resilient than DHCP because it works with IPv6 too.
- zadikian 6mo agoIdk, just checked my LAN-connected Mac's arp tables now and none of the hostnames are there, even after I ping the multicast. Haven't messed with any settings.
- guntars 6mo agoDoes anything respond to the multicast ping? If that doesn’t work then mDNS isn’t going to either. Router config is the likely culprit.
- zadikian 6mo agoYeah they respond. `ping mdns.mcast.net`, shows responses from ip addresses I recognize on my LAN, `arp -a`, still no hostnames. Tried all the other suggestions online too. Tried on my Mac and Rpi, same network, just a single ethernet LAN. Router is all default except that I port-forwarded something. Funny enough, it sees the hostnames. I'm guessing it's some problem with both my computers, but no real need to fix this because I memorized the addrs already.