diff options
| author | Michael Biebl <biebl@debian.org> | 2020-02-19 23:31:24 +0100 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2020-02-19 23:31:24 +0100 |
| commit | e536d40eaea5dcdc0743b0a5e8e17faa46608a50 (patch) | |
| tree | 0749832d8655215dac973866b4e724f3aea35448 /docs/libnm/html/NMSettingConnection.html | |
| parent | f3c6d0765dff885e168b94f28e06ecc640315a74 (diff) | |
New upstream version 1.22.8 upstream/1.22.8
Diffstat (limited to 'docs/libnm/html/NMSettingConnection.html')
| -rw-r--r-- | docs/libnm/html/NMSettingConnection.html | 25 |
1 files changed, 15 insertions, 10 deletions
diff --git a/docs/libnm/html/NMSettingConnection.html b/docs/libnm/html/NMSettingConnection.html index f9c862eb..ee8a6c6b 100644 --- a/docs/libnm/html/NMSettingConnection.html +++ b/docs/libnm/html/NMSettingConnection.html @@ -2147,11 +2147,13 @@ connection may be applied to the wrong interface.</p> for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.</p> -<p>The permitted values are: yes: register hostname and resolving -for the connection, no: disable LLMNR for the interface, resolve: -do not register hostname but allow resolving of LLMNR host names.</p> -<p>This feature requires a plugin which supports LLMNR. One such -plugin is dns-systemd-resolved.</p> +<p>The permitted values are: "yes" (2) register hostname and resolving +for the connection, "no" (0) disable LLMNR for the interface, "resolve" +(1) do not register hostname but allow resolving of LLMNR host names +If unspecified, "default" ultimately depends on the DNS plugin (which +for systemd-resolved currently means "yes").</p> +<p>This feature requires a plugin which supports LLMNR. Otherwise the +setting has no effect. One such plugin is dns-systemd-resolved.</p> <p>Flags: Read / Write</p> <p>Default value: -1</p> <p class="since">Since: 1.14</p> @@ -2169,11 +2171,14 @@ plugin is dns-systemd-resolved.</p> <a name="NMSettingConnection--mdns"></a><h3>The <code class="literal">“mdns”</code> property</h3> <pre class="programlisting"> “mdns” <a href="https://developer.gnome.org/glib/unstable/glib-Basic-Types.html#gint"><span class="type">gint</span></a></pre> <p>Whether mDNS is enabled for the connection.</p> -<p>The permitted values are: yes: register hostname and resolving -for the connection, no: disable mDNS for the interface, resolve: -do not register hostname but allow resolving of mDNS host names.</p> -<p>This feature requires a plugin which supports mDNS. One such -plugin is dns-systemd-resolved.</p> +<p>The permitted values are: "yes" (2) register hostname and resolving +for the connection, "no" (0) disable mDNS for the interface, "resolve" +(1) do not register hostname but allow resolving of mDNS host names +and "default" (-1) to allow lookup of a global default in NetworkManager.conf. +If unspecified, "default" ultimately depends on the DNS plugin (which +for systemd-resolved currently means "no").</p> +<p>This feature requires a plugin which supports mDNS. Otherwise the +setting has no effect. One such plugin is dns-systemd-resolved.</p> <p>Flags: Read / Write</p> <p>Default value: -1</p> <p class="since">Since: 1.12</p> |