Update zeroconf to explain how auto detection works (#17546)

This commit is contained in:
J. Nick Koston 2021-04-22 08:41:07 -10:00 committed by GitHub
parent 988c0a3be9
commit 8403fd113c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -30,7 +30,7 @@ zeroconf:
type: map type: map
keys: keys:
default_interface: default_interface:
description: By default, `zeroconf` will broadcast on the default interface. For systems that require broadcasting `mdns` on all interfaces, change this option to `false` if `zeroconf` does not function. description: By default, `zeroconf` will attempt to detect the best value based on available routing information. For systems that require broadcasting mDNS on all interfaces, change this option to `false` if `zeroconf` does not function.
required: false required: false
type: boolean type: boolean
default: true default: true
@ -40,3 +40,12 @@ zeroconf:
type: boolean type: boolean
default: true default: true
{% endconfiguration %} {% endconfiguration %}
## `default_interface` auto detection
If the `default_interface` is unset, the value is auto-detected based on the system routing next hop for the mDNS broadcast address (`224.0.0.251`).
If the next-hop cannot be detected or is a loopback address, `zeroconf` will broadcast on all interfaces. If the next hop is a non-loopback address, `zeroconf` will only broadcast on the default interface.
Setting the `default_interface` to `true` or `false` will override the auto detection.