- <p><opt>enable-dbus=</opt> Takes a boolean value ("yes" or
- "no"). If set to "yes" avahi-daemon connects to DBUS, to offer
- an object oriented client API. Only available if avahi has
- been compiled with <opt>--enable-dbus</opt> in which case it
- defaults to "yes".</p>
+ <p><opt>enable-dbus=</opt> 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 <opt>--enable-dbus</opt> 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.</p>
+ </option>
+
+ <option>
+ <p><opt>disallow-other-stacks=</opt> 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 no 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".</p>
+ </option>
+
+ <option>
+ <p><opt>allow-point-to-point=</opt> Takes a boolean value
+ ("yes" or "no"). If set to "yes", avahi-daemon will accept
+ interfaces with the POINTOPOINT flag. This option defaults
+ to "no" as it may be unreliable.</p>