2502 2012-05-25 14:27:24 +0000 mDNS resolving is very slow 2013-01-03 13:07:24 +0000 1 1 7 Build System, Metadata & Runtime OE-Core connectivity unspecified All Multiple VERIFIED FIXED 36d4dcfe6a3ad937caaae299923ae79b918520e1 Medium normal 1.4 1 ross.burton constantinx.musca alexandru.damian alexandrux.palalau corneliux.stoicescu meta.mr.watcher meta.watcher richard.purdie sgw song.liu --- --- --- oldest_to_newest 21620 0 ross.burton 2012-05-25 14:27:24 +0000 nsswitch.conf says: hosts: files dns mdns4 This means that for a .local lookup it does a DNS lookup *first*. Which will fail. Urgh. The recommended solution is to use nss_mdns >= 0.8 (released 2006) and: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 (see http://0pointer.de/lennart/projects/nss-mdns/) 21648 1 ross.burton 2012-05-27 20:22:51 +0000 Prior art: Fedora does http://pkgs.fedoraproject.org/gitweb/?p=nss-mdns.git;a=blob;f=nss-mdns.spec Debian's postinst is in http://packages.debian.org/sid/libnss-mdns 21878 2 cristian.iorga 2012-06-06 08:25:00 +0000 libnss_mdns has been updated to 0.10. Bug still to be fixed for R1.3. Regards, Cristian 21881 3 cristian.iorga 2012-06-06 09:30:48 +0000 Hi Ross, Can you please provide a way to test case for this bug? Thanks, Cristian 21882 4 ross.burton 2012-06-06 10:02:03 +0000 $ ping somehost.local Where somehost is the hostname of another machine on your network. avahi-browse -a will list all the local ones. On my Debian desktop with working mDNS the resolution happens in a fraction of a second: $ time ping -c 1 base.local PING base.local (192.168.1.3) 56(84) bytes of data. 64 bytes from base.local (192.168.1.3): icmp_req=1 ttl=64 time=2.37 ms --- base.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.374/2.374/2.374/0.000 ms real 0m0.108s user 0m0.000s sys 0m0.000s (that's the first run, subsequent runs are ~0.01s real time because the lookup has been cached) On my Yocto machine, the first resolution takes several seconds whilst the DNS is queried for a name that isn't in it. 22747 5 cristian.iorga 2012-07-03 08:50:52 +0000 QA will give an ETA for testing this issue during WW27. Regards, Cristian 23060 6 alexandrux.palalau 2012-07-12 14:55:16 +0000 Tested with 1.3 on a FRI2 Core-image-sato-sdk Behavior reporduces with the mentioned changes in /etc/nsswitch.conf. Subsequent calls return the same result as the first call. 23062 7 cristian.iorga 2012-07-12 14:58:23 +0000 Investigation ongoing. Proposed solution is not sufficient. 26710 8 richard.purdie 2012-10-18 11:48:24 +0000 Fix applied in master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=36d4dcfe6a3ad937caaae299923ae79b918520e1 27266 9 corneliux.stoicescu 2012-11-06 16:53:43 +0000 1) The patch is applied in master but not in danny. Tested on jasperforest and sugarbay. " nsswitch.conf says: hosts: files dns mdns4 " 2) RP: I tried your suggested test plan on a master build with the patch applied and these are my results: " root@qemuppc:~# time ping -c 1 NODE1.local PING NODE1.local (192.168.7.1): 56 data bytes 64 bytes from 192.168.7.1: seq=0 ttl=64 time=4.335 ms --- NODE1.local ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 4.335/4.335/4.335 ms real 0m0.081s user 0m0.036s sys 0m0.036s root@qemuppc:~# time ping -c 1 NODE1.local PING NODE1.local (192.168.7.1): 56 data bytes 64 bytes from 192.168.7.1: seq=0 ttl=64 time=0.568 ms --- NODE1.local ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 0.568/0.568/0.568 ms real 0m0.045s user 0m0.004s sys 0m0.032s root@qemuppc:~# time ping -c 1 NODE1.local PING NODE1.local (192.168.7.1): 56 data bytes 64 bytes from 192.168.7.1: seq=0 ttl=64 time=0.521 ms --- NODE1.local ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 0.521/0.521/0.521 ms real 0m0.036s user 0m0.004s sys 0m0.020s " It would seem a dns lookup is done judging by the ping timers. 3) Ignoring the ping timers, the ping itself is successful on both danny (with no patch) and master (with patch). The hostname resolution is done using mdns as dns does not know of NODE1.local . 28517 10 constantinx.musca 2013-01-03 12:59:23 +0000 The problem has been fixed in commit 36d4dcfe6a3ad937caaae299923ae79b918520e1. Cheers, Constantin 28520 11 corneliux.stoicescu 2013-01-03 13:07:24 +0000 Verified in master: 36d4dcfe6a3ad937caaae299923ae79b918520e1 . Will open a new one for danny.