avahi-daemon.conf - avahi-daemon configuration file
/etc/avahi/avahi-daemon.conf
avahi-daemon.conf is the configuration file for
avahi-daemon.
- host-name=
Set the host name avahi-daemon tries to register on the LAN. If omited
defaults to the system host name as set with the sethostname() system
call.
- host-name-from-machine-id=
Takes a boolean value ("yes" or "no"). If set to
"yes" avahi-daemon will use the machine-id as name on the
LAN.
- domain-name=
Set the default domain name avahi-daemon tries to register its host name and
services on the LAN in. If omitted defaults to ".local".
- browse-domains=
Set a comma separated list of browsing domains (in addition to the default
one and those announced inside the default browsing domain). Please note
that the user may specify additional browsing domains on the client side,
either by setting $AVAHI_BROWSE_DOMAINS to a list of colon separated domains
or by adding them to the XDG config file
~/.config/avahi/browse-domains (separated by newlines).
- use-ipv4=
Takes a boolean value ("yes" or "no"). If set to
"no" avahi-daemon will not use IPv4 sockets. Default is
"yes".
- use-ipv6=
Takes a boolean value ("yes" or "no"). If set to
"no" avahi-daemon will not use IPv6 sockets. Default is
"yes".
- allow-interfaces=
Set a comma separated list of allowed network interfaces that should be used
by the avahi-daemon. Traffic on other interfaces will be ignored. If set to
an empty list all local interfaces except loopback and point-to-point will
be used.
- deny-interfaces=
Set a comma separated list of network interfaces that should be ignored by
avahi-daemon. Other not specified interfaces will be used, unless
allow-interfaces= is set. This option takes precedence over
allow-interfaces=.
- check-response-ttl=
Takes a boolean value ("yes" or "no"). If set to
"yes", an additional security check is activated: incoming IP
packets will be ignored unless the IP TTL is 255. Earlier mDNS
specifications required this check. Since this feature may be incompatible
with newer implementations of mDNS it defaults to "no". On the
other hand it provides extra security.
- use-iff-running=
Takes a boolean value ("yes" or "no"). If set to
"yes" avahi-daemon monitors the IFF_RUNNING flag bit which is used
by some (modern) network drivers to tell user space if a network cable is
plugged in (in case of copper ethernet), or the network card is associated
with some kind of network (in case of WLAN). If IFF_RUNNING is set
avahi-daemon will automatically announce its services on that network.
Unfortunately far too many network drivers do not support this flag or
support it in a broken way. Therefore this option defaults to
"no".
- enable-dbus=
Takes either "yes", "no" or "warn". If set to
"yes" avahi-daemon connects to D-Bus, offering an object oriented
client API. It is only available if Avahi has been compiled with
--enable-dbus in which case it defaults to "yes".
"warn" behaves like "yes", but the daemon starts up even
when it fails to connect to a D-Bus daemon. In addition, if the connection
to the D-Bus daemon is terminated we try to reconnect. (Unless we are in a
chroot() environment where this definitely will fail.)
- disallow-other-stacks=
Takes a boolean value ("yes" or "no"). If set to
"yes" no other process is allowed to bind to UDP port 5353. This
effectively impedes other mDNS stacks from running on the host. Use this as
a security measure to make sure that only Avahi is responsible for mDNS
traffic. Please note that we do not recommend running multiple mDNS stacks
on the same host simultaneously. This hampers reliability and is a waste of
resources. However, to not annoy people this option defaults to
"no".
- allow-point-to-point=
Takes a boolean value ("yes" or "no"). If set to
"yes" avahi-daemon will make use of interfaces with the
POINTOPOINT flag set. This option defaults to "no" as it might
make mDNS unreliable due to usually large latencies with such links and
opens a potential security hole by allowing mDNS access from Internet
connections. Use with care and YMMV!
- cache-entries-max=
Takes an unsigned integer specifying how many resource records are cached
per interface. Bigger values allow mDNS work correctly in large LANs but
also increase memory consumption.
- clients-max=
Takes an unsigned integer. The maximum number of concurrent D-Bus clients
allowed. If the maximum number is reached further clients will be refused
until at least one existing client disconnects.
- objects-per-client-max=
Takes an unsigned integer. The maximum number of objects (entry groups,
browsers, resolvers) that may be registered per D-Bus client at a time. If
the maximum number is reached further object creation will be refused until
at least one object is freed.
- entries-per-entry-group-max=
Takes an unsigned integer. The maximum number of entries (resource records)
per entry group registered by a D-Bus client at a time. If the maximum
number is reached further resource records may not be added to an entry
group.
- ratelimit-interval-usec=
Takes an unsigned integer. Sets the per-interface packet rate-limiting
interval parameter. Together with ratelimit-burst= this may be used
to control the maximum number of packets Avahi will generated in a specific
period of time on an interface.
- ratelimit-burst=
Takes an unsigned integer. Sets the per-interface packet rate-limiting burst
parameter. Together with ratelimit-interval-usec= this may be used to
control the maximum number of packets Avahi will generated in a specific
period of time on an interface.
The Avahi Developers <avahi (at) lists (dot) freedesktop (dot)
org>; Avahi is available from http://avahi.org/
This man page was written using xml2man(1) by Oliver
Kurth.