Mandos-client doesn't discover server, only explicit connection works

[Erik Logtenberg]

> Stop the Mandos server by running "service mandos stop" and run the
> server manually in debug mode by running "mandos --debug" (both commands
> as root).  See what is going on with the registration of the Zeroconf
> service (using Avahi).


[root at mandostest ~]# mandos --debug
2014-08-08 09:42:53,198 root [25639]: DEBUG: Creating client 'mandostest'
2014-08-08 09:42:53,199 root [25639]: DEBUG:   Fingerprint:
0A08A9089716DCEB32FC806087A40E2C6CE5FCA8
2014-08-08 09:42:53,209 root [25639]: INFO: Starting checker u'fping -q
-- 192\\.168\\.4\\.168' for mandostest
2014-08-08 09:42:53,213 root [25639]: INFO: Now listening on address
'::', port 36941, flowinfo 0, scope_id 0
2014-08-08 09:42:53,217 root [25639]: DEBUG: Avahi server state change: 2
2014-08-08 09:42:53,220 root [25639]: DEBUG: Adding Zeroconf service
'Mandos' of type '_mandos._tcp' ...
2014-08-08 09:42:53,223 root [25639]: DEBUG: Starting main loop
2014-08-08 09:42:53,225 root [25639]: DEBUG: Avahi entry group state
change: 1
2014-08-08 09:42:53,226 root [25639]: DEBUG: Avahi entry group state
change: 2
2014-08-08 09:42:53,226 root [25639]: DEBUG: Zeroconf service established.
2014-08-08 09:42:53,228 root [25639]: INFO: Checker for mandostest succeeded

Still, avahi-browse on the same machine (in a separate terminal) doesn't
see the service.

[root at mandostest ~]# avahi-browse --all
+   eth0 IPv4 mandostest [52:54:00:5c:d2:65]                Workstation
         local


Erik.