From bbae86d3d2997a853ca0365e8eb7a3ca7489ee09 Mon Sep 17 00:00:00 2001 From: Sebastien Bacher Date: Fri, 25 Jan 2019 11:24:41 +0100 Subject: New upstream version 1.15.2 --- man/NetworkManager.conf.xml | 84 +++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 77 insertions(+), 7 deletions(-) (limited to 'man/NetworkManager.conf.xml') diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 87cf0016..e22aa20a 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -166,6 +166,15 @@ 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. @@ -204,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 + &nmstatedir;/no-auto-default.state to prevent creating the default connection for that device again. See for the syntax how to @@ -262,7 +271,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. @@ -306,8 +315,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, @@ -331,15 +340,23 @@ 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 &nmrundir;/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 &nmrundir;/no-stub-resolv.conf + that contains the original name servers pushed to the DNS plugin. @@ -379,6 +396,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 @@ -641,7 +674,15 @@ ipv6.ip6-privacy=0 (see nm-settings5 for details). A default value is only consulted if the corresponding per-connection value explicitly allows for that. + + + + 802-1x.auth-timeout + + + cdma.mtu + connection.auth-retries If left unspecified, the default value is 3 tries before failing the connection. @@ -676,6 +717,9 @@ ipv6.ip6-privacy=0 ethernet.wake-on-lan + + gsm.mtu + infiniband.mtu If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or the MTU is left unspecified on activation. @@ -695,6 +739,11 @@ ipv6.ip6-privacy=0 If left unspecified, the default value for 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 @@ -714,6 +763,11 @@ ipv6.ip6-privacy=0 If left unspecified, the default value for the interface type is used. + + 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 @@ -770,7 +824,12 @@ ipv6.ip6-privacy=0 If left unspecified, the default value "optional" will be used. + + wifi.wake-on-wlan + + + @@ -1158,6 +1217,8 @@ enable=env:TAG1 be used to negate the match. Note that if one except-predicate matches, the entire configuration will be disabled. In other words, a except predicate always wins over other predicates. + If the setting only consists of "except:" matches and none of the + negative conditions are satisfied, the configuration is still enabled. # enable the configuration either when the environment variable # is present or the version is at least 1.2.0. @@ -1343,11 +1404,20 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16 Optionally, a driver version may be specified separated by '/'. Globbing is supported for the version. + + dhcp-plugin:DHCP + Match the configured DHCP plugin "main.dhcp". + + except:SPEC Negative match of a device. SPEC must be explicitly qualified with a prefix such as interface-name:. A negative match has higher priority then the positive - matches above. + matches above. + If there is a list consisting only of negative matches, the behavior is the same as if there + is also match-all. That means, if none of all the negative matches is satisfied, the overall result is + still a positive match. That means, "except:interface-name:eth0" is the same as + "*,except:interface-name:eth0". SPEC[,;]SPEC -- cgit 1.3.0-6-gf8a5