1 <?xml version="1.0"?><!--*-nxml-*-->
2 <!DOCTYPE manpage SYSTEM "xmltoman.dtd">
3 <?xml-stylesheet type="text/xsl" href="xmltoman.xsl" ?>
8 This file is part of avahi.
10 avahi is free software; you can redistribute it and/or modify it
11 under the terms of the GNU Lesser General Public License as
12 published by the Free Software Foundation; either version 2.1 of the
13 License, or (at your option) any later version.
15 avahi is distributed in the hope that it will be useful, but WITHOUT
16 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
17 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General
18 Public License for more details.
20 You should have received a copy of the GNU Lesser General Public
21 License along with avahi; if not, write to the Free Software
22 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
26 <manpage name="avahi-daemon.conf" section="5" desc="avahi-daemon configuration file">
29 <cmd>@pkgsysconfdir@/avahi-daemon.conf</cmd>
33 <p><file>avahi-daemon.conf</file> is the configuration file for avahi-daemon.</p>
36 <section name="Section [Server]">
39 <p><opt>host-name=</opt> Set the host name avahi-daemon tries
40 to register on the LAN. If omited defaults to the system host
41 name as set with the sethostname() system call.</p>
45 <p><opt>domain-name=</opt> Set the default domain name avahi-daemon
46 tries to register its host name and services on the LAN in. If
47 omitted defaults to ".local".</p>
51 <p><opt>browse-domains=</opt> Set a comma seperated list of
52 browsing domains (in addition to the default one and those
53 announced inside the default browsing domain). Please note
54 that the user may specify additional browsing domains on the
55 client side, either by setting $AVAHI_BROWSE_DOMAINS to a list
56 of colon seperated domains or by adding them to the XDG config
57 file <file>~/.config/avahi/browse-domains</file> (seperated by
63 <p><opt>use-ipv4=</opt> Takes a boolean value ("yes" or
64 "no"). If set to "no" avahi-daemon will not use IPv4
65 sockets. Default is "yes".</p>
69 <p><opt>use-ipv6=</opt> Takes a boolean value ("yes" or
70 "no"). If set to "no" avahi-daemon will not use IPv6
71 sockets. Default is "yes".</p>
75 <p><opt>check-response-ttl=</opt> Takes a boolean value ("yes"
76 or "no"). If set to "yes", an additional security check is
77 activated: incoming IP packets will be ignored unless the IP
78 TTL is 255. Earlier mDNS specifications required this
79 check. Since this feature may be incompatible with newer
80 implementations of mDNS it defaults to "no". On the other hand
81 it provides extra security.</p>
85 <p><opt>use-iff-running=</opt> Takes a boolean value ("yes" or
86 "no"). If set to "yes" avahi-daemon monitors the IFF_RUNNING
87 flag bit which is used by some (modern) network drivers to
88 tell user space if a network cable is plugged in (in case of
89 copper ethernet), or the network card is associated with some
90 kind of network (in case of WLAN). If IFF_RUNNING is set
91 avahi-daemon will automatically announce its services on that
92 network. Unfortunately far too many network drivers do not
93 support this flag or support it in a broken way. Therefore
94 this option defaults to "no".</p>
98 <p><opt>enable-dbus=</opt> Takes either "yes", "no" or
99 "warn". If set to "yes" avahi-daemon connects to D-BUS,
100 offering an object oriented client API. It is only available
101 if avahi has been compiled with <opt>--enable-dbus</opt> in
102 which case it defaults to "yes". "warn" behaves like "yes",
103 but the daemon starts up even when it fails to connect to a
108 <p><opt>disallow-other-stacks=</opt> Takes a boolean value
109 ("yes" or "no"). If set to "yes" no other process is allowed
110 to bind to UDP port 5353. This effectively impedes other mDNS
111 stacks from running on the host. Use this as a security
112 measure to make sure that only Avahi is responsible for mDNS
113 traffic. Please note that we do no recommend running multiple
114 mDNS stacks on the same host simultaneously. This hampers
115 reliability and is a waste of resources. However, to not annoy
116 people this option defaults to "no".</p>
120 <p><opt>allow-point-to-point=</opt> Takes a boolean value
121 ("yes" or "no"). If set to "yes" avahi-daemon will make use of
122 interfaces with the POINTOPOINT flag set. This option defaults
123 to "no" as it might make mDNS unreliable due to usually large
124 latencies with such links and opens a potential security hole
125 by allowing mDNS access from Internet connections. Use with
131 <section name="Section [wide-area]">
133 <p><opt>enable-wide-area=</opt> Takes a boolean value
134 ("yes" or "no"). Enable wide-area DNS-SD, aka
135 DNS-SD over unicast DNS. If this is enabled only domains
136 ending in .local will be resolved on mDNS, all other domains
137 are resolved via unicast DNS. If you want to maintain multiple
138 different multicast DNS domains even with this option enabled
139 we encourage you to use subdomains of .local, such as
140 "kitchen.local". This option defaults to "yes".</p>
145 <section name="Section [publish]">
147 <option><p><opt>disable-publishing=</opt> Takes a boolean value
148 ("yes" or "no"). If set to "yes", no record will be published by
149 Avahi, not even address records for the local host. Avahi will
150 be started in a querying-only mode. Use this is a security
151 measure. This option defaults to "no"</p></option>
153 <option><p><opt>disable-user-service-publishing=</opt> Takes a boolean value
154 ("yes" or "no"). If set to "yes", Avahi will still publish
155 address records and suchlike but will not allow user
156 applications to publish services. Use this is a security
157 measure. This option defaults to "no"</p></option>
160 <p><opt>add-service-cookie=</opt> Takes a boolean value ("yes"
161 or "no"). If set to "yes" an implicit TXT entry will be added
162 to all locally registered services, containing a cookie value
163 which is chosen randomly on daemon startup. This can be used
164 to detect if two services on two different
165 interfaces/protocols are actually identical. Defaults to
170 <p><opt>publish-addresses=</opt> Takes a boolean value ("yes"
171 or "no"). If set to "yes" avahi-daemon will register mDNS
172 address records for all local IP addresses. Unless you want to
173 use avahi-daemon exclusively for browsing it's recommended to
174 enable this. If you plan to register local services you need
175 to enable this option. Defaults to "yes".</p>
179 <p><opt>publish-hinfo=</opt> Takes a boolean value ("yes" or
180 "no"). If set to "yes" avahi-daemon will register an mDNS
181 HINFO record on all interfaces which contains information
182 about the local operating system and CPU, which might be
183 useful for administrative purposes. This is recommended by the
184 mDNS specification but not required. For the sake of privacy
185 you might choose to disable this feature. Defaults to
190 <p><opt>publish-workstation=</opt> Takes a boolean value
191 ("yes" or "no"). If set to "yes" avahi-daemon will register a
192 service of type "_workstation._tcp" on the local LAN. This
193 might be useful for administrative purposes (i.e. browse for
194 all PCs on the LAN), but is not required or recommended by any
195 specification. Newer MacOS X releases register a service of
196 this type. Defaults to "yes".</p>
200 <p><opt>publish-domain=</opt> Takes a boolean value ("yes" or
201 "no"). If set to "yes" avahi-daemon will announce the locally
202 used domain name (see above) for browsing by other
203 hosts. Defaults to "yes".</p>
207 <p><opt>publish-dns-servers=</opt> Takes a comma seperated
208 list of IP addresses for unicast DNS servers. You can use this
209 to announce unicast DNS servers via mDNS. When used in
210 conjunction with avahi-dnsconfd on the client
211 side this allows DHCP-like configuration of unicast DNS
216 <p><opt>publish-resolv-conf-dns-servers=</opt> Takes a boolean
217 value ("yes" or "no"). If set to "yes" avahi-daemon will
218 publish the unicast DNS servers specified in
219 <file>/etc/resolv.conf</file> in addition to those specified
220 with <opt>publish-dns-servers</opt>. Send avahi-daemon a
221 SIGHUP to have it reload this file. Defaults to "no".</p>
226 <section name="Section [reflector]">
228 <p><opt>enable-reflector=</opt> Takes a boolean value ("yes"
229 or "no"). If set to "yes" avahi-daemon will reflect incoming
230 mDNS requests to all local network interfaces, effectively
231 allowing clients to browse mDNS/DNS-SD services on all
232 networks connected to the gateway. The gateway is somewhat
233 intelligent and should work with all kinds of mDNS traffic,
234 though some functionality is lost (specifically the unicast
235 reply bit, which is used rarely anyway). Make sure to not run
236 multiple reflectors between the same networks, this might
237 cause them to play Ping Pong with mDNS packets. Defaults to
242 <p><opt>reflect-ipv=</opt> Takes a boolean value ("yes" or
243 "no"). If set to "yes" and <opt>enable-reflector</opt> is
244 enabled, avahi-daemon will forward mDNS traffic between IPv4
245 and IPv6, which is usually not recommended. Defaults to "no".</p>
249 <section name="Section [rlimits]">
250 <p>This section is used to define system resource limits for the
251 daemon. See <manref section="2" name="setrlimit"/> for more
252 information. If any of the options is not specified in the configuration
253 file, avahi-daemon does not change it from the system
258 <p><opt>rlimit-as=</opt> Value in bytes for RLIMIT_AS (maximum size of the process's virtual memory). Sensible values are heavily system dependent.</p>
262 <p><opt>rlimit-core=</opt> Value in bytes for RLIMIT_CORE (maximum core file size). Unless you want to debug avahi-daemon, it is safe to set this to 0.</p>
266 <p><opt>rlimit-data=</opt> Value in bytes for RLIMIT_DATA (maximum size of the process's data segment). Sensible values are heavily system dependent.</p>
270 <p><opt>rlimit-fsize=</opt> Value for RLIMIT_FSIZE (maximum size of files the process may create). Since avahi-daemon shouldn't write any files to disk, it is safe to set this to 0.</p>
274 <p><opt>rlimit-nofile=</opt> Value for RLIMIT_NOFILE (open file descriptors). avahi-daemon shouldn't need more than 15 to 20 open file descriptors concurrently.</p>
278 <p><opt>rlimit-stack=</opt> Value in bytes for RLIMIT_STACK (maximum size of the process stack). Sensible values are heavily system dependent.</p>
282 <p><opt>rlimit-nproc=</opt> Value for RLIMIT_NPROC (number of process of user). Since only a single avahi-daemon process is usually running you can set this safely to 1.</p>
287 <section name="Authors">
288 <p>The avahi developers <@PACKAGE_BUGREPORT@>; avahi is
289 available from <url href="@PACKAGE_URL@"/></p>
292 <section name="See also">
294 <manref name="avahi-daemon" section="8"/>, <manref name="avahi-dnsconfd" section="8"/>
298 <section name="Comments">
299 <p>This man page was written using <manref name="xml2man" section="1"
300 href="http://masqmail.cx/xml2man/"/> by Oliver Kurth.</p>