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

[Teddy Hogeborn]

Erik Logtenberg <erik at logtenberg.eu> writes:

> > Can the client host "see" the server by running this command?
> > 
> > $ avahi-browse --terminate --resolve _mandos._tcp
> > 
> > This is basically what the client does to find the server.  If the
> > server cannot be found with the above command, the client cannot
> > find the server.  If the above command does *not* work, what happens
> > if you run it *on the server*?  I.e. is the server announcing itself
> > as a ZeroConf service at all?
>
> On both the client and the server, the command above gives no output.
[...]
> I do see the mandos and avahi processes on the server though:
>
> _mandos  18060 /usr/bin/python /usr/sbin/mandos --foreground
> _mandos  18065  \_ /usr/bin/python /usr/sbin/mandos --foreground
> avahi    18076 avahi-daemon: running [mandostest.local]
> avahi    18077  \_ avahi-daemon: chroot helper
>
> What else can I do to further debug this?

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).

/Teddy Hogeborn

-- 
The Mandos Project
http://www.recompile.se/mandos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://mail.recompile.se/pipermail/mandos-dev/attachments/20140807/37748ae4/attachment.sig>