NetworkManager/clients
Thomas Haller 3d07708f59 doc: clarify default values for ipv4.mdns and ipv4.llmnr settings
LLMNR and mDNS settings can have their global default value configured
in "NetworkManager.conf".

Global default values should work the way that all regular values of the property
can be configured explicitly in the connection profile. The special "default" value
only indicates to allow lookup of the global default, but it should not have a
meaning of its own.

Note that if mDNS/LLMNR settings are left unspecified, we will set the
argument to SetLinkMulticastDNS() and SetLinkLLMNR() functions to "",
which means that systemd-resolved decides on a default. Also, depending
on the DNS plugin, the default value differs. This is all fine however.
In this case, the ultimate default value depends on other things (like
the DNS plugin), but each possible value is in fact explicitly
configurable. We also do that for "ipv6.ip6-privacy".

Anyway, cleanup the documentation a bit and try to better explain what
the default is.
2019-12-10 16:49:23 +01:00
..
cli cli: don't fetch permissions for NMClient in nmcli unless required 2019-12-10 09:17:17 +01:00
cloud-setup cloud-setup: don't fetch permissions for NMClient in nm-cloud-setup 2019-12-10 09:17:17 +01:00
common doc: clarify default values for ipv4.mdns and ipv4.llmnr settings 2019-12-10 16:49:23 +01:00
tests cli: sort permission in output of nmcli general permissions 2019-12-10 07:53:25 +01:00
tui tui: don't fetch permissions for NMClient in nmtui 2019-12-10 09:17:17 +01:00
meson.build nm-online: use nmc_client_new_async() instead of nm_client_new_async() 2019-12-10 09:17:17 +01:00
nm-online.c nm-online: don't fetch permissions for NMClient in nm-online 2019-12-10 09:17:17 +01:00