Avahi not working, apparently

X

Xavier

Hi,
Ran the avahi-daemon on the command line to debug it :
Code: 
[
root@numenor avahi]# avahi-daemon
Found user 'avahi' (UID 558) and group 'avahi' (GID 558).
Successfully dropped root privileges.
avahi-daemon 0.8 starting up.
Loading service file /usr/local/etc/avahi/services/dlna.service.
Loading service file /usr/local/etc/avahi/services/sftp-ssh.service.
Loading service file /usr/local/etc/avahi/services/ssh.service.
Joining mDNS multicast group on interface lo0.IPv6 with address fe80::1.
New relevant interface lo0.IPv6 for mDNS.
Joining mDNS multicast group on interface lo0.IPv4 with address 127.0.0.1.
New relevant interface lo0.IPv4 for mDNS.
Joining mDNS multicast group on interface igb0.IPv6 with address 2a01:e0a:xxxx:xxxx::144.
New relevant interface igb0.IPv6 for mDNS.
Joining mDNS multicast group on interface igb0.IPv4 with address 192.168.100.144.
New relevant interface igb0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::1 on lo0.*.
Registering new address record for ::1 on lo0.*.
Registering new address record for 127.0.0.1 on lo0.IPv4.
Registering new address record for 2a01:e0a:xxxx:xxxx::144 on igb0.*.
Registering new address record for 192.168.100.144 on igb0.IPv4.
Server startup complete. Host name is numenor.groumpf.org. Local service cookie is 2250917044.
Failed to add service 'numenor' of type '_ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/ssh.service): Not supported
Failed to add service 'numenor' of type '_sftp-ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/sftp-ssh.service): Not supported
Failed to add service 'numenor' of type '_dlna._tcp', ignoring service group (/usr/local/etc/avahi/services/dlna.service): Not supported
Failed to add DNS server address: Not supported
Why do not the services load ?
My avahi.conf :
Code: 
[root@numenor avahi]# grep -v "^#" avahi-daemon.conf

[server]
host-name=numenor
domain-name=groumpf.org
use-ipv4=yes
use-ipv6=yes
ratelimit-interval-usec=1000000
ratelimit-burst=1000

[wide-area]
enable-wide-area=yes

[publish]
publish-hinfo=no
publish-workstation=no
publish-domain=yes
publish-dns-servers=192.168.100.144

[reflector]

[rlimits]
and, for example, the dlna.conf service file :
Code: 
<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<!-- See avahi.service(5) for more information about this configuration file -->
<service-group>
  <name replace-wildcards="yes">%h</name>
  <service>
    <type>_dlna._tcp</type>
    <port>8200</port>
  </service>
</service-group>

Thanks for any advice
Regards,
Xavier
 
Good catch on the domain name. For anyone else running into this: Avahi (and mDNS/Bonjour in general) is hardcoded to use the .local TLD. If you configure avahi-daemon.conf with any domain other than "local", it will appear to run but will not respond to mDNS queries from other devices because all mDNS clients query exclusively for .local names.

The relevant setting in /usr/local/etc/avahi/avahi-daemon.conf is:

[server]
domain-name=local

If this is set to anything else (like your actual LAN domain, e.g. "home.lan" or "mynetwork"), Avahi will register services under that domain but no other device will find them via mDNS because the mDNS protocol spec (RFC 6762) reserves only .local for link-local multicast DNS.

If you need service discovery on a custom domain, you would need to use unicast DNS-SD (DNS Service Discovery via regular DNS records) rather than mDNS. Avahi does support publishing DNS-SD records to a unicast DNS server via the avahi-daemon wide-area option, but that is a completely different setup from the simple zero-conf .local browsing.
 
You must log in or register to reply here.
Back
Top