From 9a6dcbf895f9da01768e64b73cec88c16157d91e Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Tue, 26 Mar 2019 23:25:23 +0100 Subject: New upstream version 1.16.0 --- docs/api/html/NetworkManager.conf.html | 97 +++++++++++++++++++++++++++++----- 1 file changed, 85 insertions(+), 12 deletions(-) (limited to 'docs/api/html/NetworkManager.conf.html') diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index 4fbf45e6..0069f1e4 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -146,7 +146,8 @@ plugins-=remove-me

monitor-connection-files

-

Whether the configured settings plugin(s) + +

Whether the configured settings plugin(s) should set up file monitors and immediately pick up changes made to connection files while NetworkManager is running. This is disabled by default; NetworkManager will only read @@ -159,7 +160,19 @@ plugins-=remove-me In some situations, NetworkManager might first delete and add the connection anew, instead of updating the existing one. Also, NetworkManager might pick up incomplete settings while the user is still editing the files. -

+

+

+ Note that neither this setting nor restarting the NetworkManager daemon + is the advised way to reload connection profiles from disk. Instead, after + modifying the files reload them with nmcli connection reload + or nmcli connection load "$FILENAME". Even better, + instead of modifying files directly, use NetworkManager tools like + nmcli, nmtui or the GUI. +

+

+ This setting is deprecated and will have no effect in the future. +

+

auth-polkit

@@ -200,7 +213,7 @@ plugins-=remove-me

When the default wired connection is deleted or saved to a new persistent connection by a plugin, the device is added to a list in the file - /run/NetworkManager/no-auto-default.state + /var/lib/NetworkManager/no-auto-default.state to prevent creating the default connection for that device again.

See the section called “Device List Format” for the syntax how to @@ -254,7 +267,7 @@ no-auto-default=* environments where network setup is more or less static or it is desirable to save process time but still handle some dynamic configurations. When this option is true, - network configuration for WiFi, WWAN, Bluetooth, ADSL, and PPPoE + network configuration for Wi-Fi, WWAN, Bluetooth, ADSL, and PPPoE interfaces cannot be preserved due to their use of external services, and these devices will be deconfigured when NetworkManager quits even though other interface's configuration may be preserved. @@ -297,8 +310,8 @@ no-auto-default=*

dns

-

Set the DNS (resolv.conf) processing mode. - If the key is unspecified, default is used, +

Set the DNS processing mode.

+

If the key is unspecified, default is used, unless /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf, /run/systemd/resolve/resolv.conf, @@ -322,15 +335,22 @@ no-auto-default=* after some time. This behavior can be modified passing the 'all-servers' or 'strict-order' options to dnsmasq (see the manual page for more details).

+

systemd-resolved: NetworkManager will + push the DNS configuration to systemd-resolved

unbound: NetworkManager will talk to unbound and dnssec-triggerd, providing a "split DNS" configuration with DNSSEC support. /etc/resolv.conf will be managed by dnssec-trigger daemon.

-

systemd-resolved: NetworkManager will - push the DNS configuration to systemd-resolved

none: NetworkManager will not modify resolv.conf. This implies rc-manager unmanaged

+

Note that the plugins dnsmasq, systemd-resolved + and unbound are caching local nameservers. + Hence, when NetworkManager writes /var/run/NetworkManager/resolv.conf + and /etc/resolv.conf (according to rc-manager + setting below), the name server there will be localhost only. + NetworkManager also writes a file /var/run/NetworkManager/no-stub-resolv.conf + that contains the original name servers pushed to the DNS plugin.

@@ -370,6 +390,22 @@ no-auto-default=* +

systemd-resolved

+ +

Send the connection DNS configuration to + systemd-resolved. Defaults to "true". +

+

Note that this setting is complementary to the + dns setting. You can keep this enabled while using + dns set to another DNS plugin alongside + systemd-resolved, or dns set to + systemd-resolved to configure the system resolver to use + systemd-resolved.

+

If systemd-resolved is enabled, the connectivity check resolves the + hostname per-device.

+ + +

debug

Comma separated list of options to aid @@ -595,6 +631,8 @@ ipv6.ip6-privacy=0 (see nm-settings(5) for details). A default value is only consulted if the corresponding per-connection value explicitly allows for that. + +

@@ -677,6 +715,11 @@ ipv6.ip6-privacy=0 the interface type is used.

+ + + + @@ -697,6 +740,11 @@ ipv6.ip6-privacy=0 the interface type is used.

+ + + + + + + +

ipv4.dns-priority

If unspecified or zero, use 50 for VPN profiles + and 100 for other profiles.

ipv4.route-metric

ipv6.dns-priority

If unspecified or zero, use 50 for VPN profiles + and 100 for other profiles.

ipv6.ip6-privacy

If ipv6.ip6-privacy is unset, use the content of "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback. @@ -758,9 +806,15 @@ ipv6.ip6-privacy=0

wifi.wake-on-wlan

wireguard.mtu

+ +

@@ -997,6 +1051,20 @@ managed=1 checking functionality. This allows NetworkManager to detect whether or not the system can actually access the internet or whether it is behind a captive portal.

+

Connectivity checking serves two purposes. For one, it exposes + a connectivity state on D-Bus, which other applications may use. For example, + Gnome's portal helper uses this as signal to show a captive portal login + page. + The other use is that default-route of devices without global connectivity + get a penalty of +20000 to the route-metric. This has the purpose to give a + better default-route to devices that have global connectivity. For example, + when being connected to WWAN and to a Wi-Fi network which is behind a captive + portal, WWAN still gets preferred until login.

+

Note that your distribution might set /proc/sys/net/ipv4/conf/*/rp_filter to + strict filtering. That works badly with per-device connectivity checking, + which uses SO_BINDDEVICE to send requests on all devices. A strict rp_filter + setting will reject any response and the connectivity check on all but the + best route will fail.

@@ -1026,10 +1094,15 @@ managed=1 - + connectivity checking. Note that this only compares + that the HTTP response starts with the specifid text, + it does not compare the exact string. This behavior + might change in the future, so avoid relying on it. + If missing, the response defaults to "NetworkManager is online". + If set to empty, the HTTP server is expected to answer with + status code 204 or send no data.

response

If set controls what body content +

If set, controls what body content NetworkManager checks for when requesting the URI for - connectivity checking. If missing, defaults to - "NetworkManager is online"

@@ -1058,7 +1131,7 @@ managed=1

options

- A list of of options to be passed to the hostname resolver. + A list of options to be passed to the hostname resolver.

-- cgit 1.3.0-6-gf8a5