Mandos-client doesn't discover server, only explicit connection works
Erik Logtenberg
erik at logtenberg.eu
Fri Aug 8 11:27:59 CEST 2014
>
> That *is* odd. How about publishing the service manually, using this
> command:
>
> avahi-publish --service Mandos _mandos._tcp 36941
>
> (Adjust the port number to match the port number in the debug output.
> If a "Local name collision" occurs, change the service name from
> "Mandos" to "Mandos#2" or something.)
>
Avahi-publish works on the server:
[root at mandostest ~]# avahi-publish --service Mandos _mandos._tcp 57019
Established under name 'Mandos'
And avahi-browse, also on the server in a separate terminal, detects it:
[root at mandostest ~]# avahi-browse --all --terminate
+ eth0 IPv4 Mandos _mandos._tcp
local
+ eth0 IPv4 mandosclient [52:54:00:a6:98:55] Workstation
local
+ eth0 IPv4 mandostest [52:54:00:5c:d2:65] Workstation
local
However, on the client avahi-browse still doesn't see it:
[root at mandosclient ~]# avahi-browse --all
+ eth0 IPv4 mandosclient [52:54:00:a6:98:55] Workstation
local
And thus also mandos-client stays the same.
Erik.
More information about the Mandos-Dev
mailing list