From 80ec1decc49c72efec2a8b87c06245c92c0ab807 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 11 Feb 2021 18:11:46 +0100 Subject: New upstream version 1.29.90 --- docs/api/html/NetworkManager.conf.html | 77 +++++++++++++++++++++++++++------- 1 file changed, 63 insertions(+), 14 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 6c8f1f8e..05250d17 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -268,18 +268,24 @@ no-auto-default=* this option. An hostname empty or equal to 'localhost', 'localhost6', 'localhost.localdomain' or 'localhost6.localdomain' is considered invalid.

-

default: NetworkManager will update the hostname - with the one provided via DHCP on the main connection (the one with a default - route). If not present, the hostname will be updated to the last one set - outside NetworkManager. If it is not valid, NetworkManager will try to recover - the hostname from the reverse lookup of the IP address of the main connection. - If this fails too, the hostname will be set to 'localhost.localdomain'. +

default: NetworkManager will update the + hostname with the one provided via DHCP or reverse DNS lookup of the + IP address on the connection with the default route or on any + connection with the property hostname.only-from-default set to + 'false'. Connections are considered in order of + increasing value of the hostname.priority + property. In case multiple connections have the same priority, + connections activated earlier are considered first. If no hostname can + be determined in such way, the hostname will be updated to the last + one set outside NetworkManager or to 'localhost.localdomain'.

-

dhcp: NetworkManager will update the transient hostname - only with information coming from DHCP. No fallback nor reverse lookup will be - performed, but when the dhcp connection providing the hostname is deactivated, - the hostname is reset to the last hostname set outside NetworkManager or - 'localhost' if none valid is there. +

dhcp: this is similar to + 'default', with the difference that after trying to + get the DHCP hostname, reverse DNS lookup is not done. Note that + selecting this option is equivalent to setting the property + 'hostname.from-dns-lookup' to + 'false' globally for all connections in + NetworkManager.conf.

none: NetworkManager will not manage the transient hostname and will never set it. @@ -616,6 +622,18 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth connection section

Specify default values for connections.

+

+ Such default values are only consulted if the corresponding per-connection property + explicitly allows for that. That means, all these properties correspond to + a property of the connection profile (for example connection.mud-url). + Only if the per-profile property is set to a special value that indicates to use the + default, the default value from NetworkManager.conf is consulted. It depends on the + property, which is the special value that indicates fallback to the default, but it + usually is something like empty, unset values or special numeric values like 0 or -1. + That means the effectively used value can first always be configured for each profile, + and these default values only matter if the per-profile values explicitly indicates + to use the default from NetworkManager.conf. +

Example:

@@ -626,13 +644,13 @@ ipv6.ip6-privacy=0

-

Supported Properties

+

Supported Properties

Not all properties can be overwritten, only the following properties are supported to have their default values configured (see nm-settings(5) for details). - A default value is only consulted if the corresponding per-connection value - explicitly allows for that. +

+

@@ -700,6 +718,22 @@ ipv6.ip6-privacy=0 +

hostname.from-dhcp

+ + + +

hostname.from-dns-lookup

+ + + +

hostname.only-from-default

+ + + +

hostname.priority

+ + +

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.

@@ -1053,6 +1087,21 @@ managed=1

+

wifi.iwd.autoconnect

+

+ If wifi.backend is iwd, setting this to + false forces IWD's autoconnect mechanism to be disabled for + this device and connections will only be initiated by NetworkManager whether + commaned by a client or automatically. Leaving it true (default) + stops NetworkManager from automatically initiating connections and allows + IWD to use its network ranking and scanning logic to decide the best networks + to autoconnect to next. Connections' autoconnect-priority, + autoconnect-retries settings will be ignored. Other settings + like permissions or multi-connect may interfere + with IWD connection attempts. +

+ +

sriov-num-vfs

Specify the number of virtual functions (VF) to enable -- cgit 1.3.0-6-gf8a5