I've been investigating this problem further, and I'm finding a pattern: The wirelessly connected laptop is not receiving responses to the multicast DNS queries, but the other machines are actually answering the queries, which are leaving their network interfaces. Look at this dumps:
from astromech (wirelessly connected laptop) to pdsrv (debian machine, used to be called debian), while running avahi-resolve -n pdsrv.local: 20:37:14.347964 IP 192.168.111.102.5353 > 224.0.0.251.5353: 0 [2q] A (QM)? pdsrv.local. AAAA (QM)? pdsrv.local. (35) 20:37:15.351963 IP 192.168.111.102.5353 > 224.0.0.251.5353: 0 [2q] A (QM)? pdsrv.local. AAAA (QM)? pdsrv.local. (35) 20:37:17.355954 IP 192.168.111.102.5353 > 224.0.0.251.5353: 0 [2q] A (QM)? pdsrv.local. AAAA (QM)? pdsrv.local. (35) This is what happens on pdsrv at the same time: 20:36:52.036662 IP 192.168.111.102.5353 > 224.0.0.251.5353: 0 [2q] A? pdsrv.local. AAAA? pdsrv.local. (35) 20:36:52.038962 IP 192.168.111.2.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) A 192.168.111.2 (39) 20:36:53.040740 IP 192.168.111.102.5353 > 224.0.0.251.5353: 0 [2q] A? pdsrv.local. AAAA? pdsrv.local. (35) 20:36:53.041249 IP 192.168.111.2.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) A 192.168.111.2 (39) 20:36:55.044699 IP 192.168.111.102.5353 > 224.0.0.251.5353: 0 [2q] A? pdsrv.local. AAAA? pdsrv.local. (35) 20:36:55.045287 IP 192.168.111.2.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/0 (Cache flush) A 192.168.111.2 (39) Interesting, so pdsrv answers the queries, but astromech don't receive them, don't mater if I restart astromech. only works again if I restart pdsrv. Now, if I run dig -p 5353 @224.0.0.251 pdsrv.local on astromech: 20:42:17.700820 IP 192.168.111.102.32771 > 224.0.0.251.5353: 3163+ A (QM)? pdsrv.local. (29) 20:42:17.702563 IP 192.168.111.2.5353 > 192.168.111.102.32771: 3163*- 1/0/0 A 192.168.111.2 (45) Oh, it works wonderfuly, but I'm receiving answers through unicast. So the problem is that astromech can send multicast, but can't receive unless I restart the machine hosting the bridge. I can be pretty sure of this because if I do avahi-resolve -n astromech.local from within astromech, then it multicasts it's name and address, and pdsrv can resolve it for awhile using avahi-resolve -n astromech.local, until the entry in Avahi's cache expires. -- MDNS not working properly https://bugs.launchpad.net/bugs/162084 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
