From 7514efc2f38c9ace4557d4e69d68e7d380389030 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 26 Aug 2016 02:18:32 +0200 Subject: Imported Upstream version 1.4.0 --- man/NetworkManager.conf.xml | 188 ++++++++++++++++++++++++++++++++++---------- 1 file changed, 148 insertions(+), 40 deletions(-) (limited to 'man/NetworkManager.conf.xml') diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index ea0573fa..db381f07 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -224,30 +224,12 @@ no-auto-default=* ignore-carrier - Specify devices for which NetworkManager will (partially) - ignore the carrier state. Normally, for - device types that support carrier-detect, such as Ethernet - and InfiniBand, NetworkManager will only allow a - connection to be activated on the device if carrier is - present (ie, a cable is plugged in), and it will - deactivate the device if carrier drops for more than a few - seconds. - - - Listing a device here will allow activating connections on - that device even when it does not have carrier, provided - that the connection uses only statically-configured IP - addresses. Additionally, it will allow any active - connection (whether static or dynamic) to remain active on - the device when carrier is lost. - - - Note that the "carrier" property of NMDevices and device D-Bus - interfaces will still reflect the actual device state; it's just - that NetworkManager will not make use of that information. - - See for the syntax how to - specify a device. + This setting is deprecated for the per-device setting + ignore-carrier which overwrites this setting + if specified (See ). + Otherwise, it is a list of matches to specify for which device + carrier should be ignored. See for the + syntax how to specify a device. @@ -307,8 +289,8 @@ no-auto-default=* configuration with DNSSEC support. The /etc/resolv.conf will be managed by dnssec-trigger daemon. none: NetworkManager will not - modify resolv.conf. This implies rc-manager - unmanaged + modify resolv.conf. This implies + rc-manager unmanaged @@ -322,7 +304,12 @@ no-auto-default=* always write resolv.conf to its runtime state directory. symlink: NetworkManager will symlink /etc/resolv.conf to its private - resolv.conf file in the runtime state directory. + resolv.conf file in the runtime state directory. If + /etc/resolv.conf + already is a symlink pointing to a different location, the file + will not be modified. This allows the user to disable managing + by pointing the link /etc/resolv.conf to + somewhere else. file: NetworkManager will write /etc/resolv.conf as file. If it finds a symlink, it will follow the symlink and update the target @@ -332,7 +319,7 @@ no-auto-default=* netconfig: NetworkManager will run netconfig to update the DNS configuration. unmanaged: don't touch - resolv.conf. + /etc/resolv.conf. none: deprecated alias for symlink. @@ -461,7 +448,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth WIFI_SCAN, IP4, IP6, AUTOIP4, DNS, VPN, SHARING, SUPPLICANT, AGENTS, SETTINGS, SUSPEND, CORE, DEVICE, OLPC, WIMAX, INFINIBAND, FIREWALL, ADSL, BOND, VLAN, BRIDGE, DBUS_PROPS, - TEAM, CONCHECK, DCB, DISPATCH, AUDIT. + TEAM, CONCHECK, DCB, DISPATCH, AUDIT, SYSTEMD, VPN_PLUGIN. In addition, these special domains can be used: NONE, ALL, DEFAULT, DHCP, IP. You can specify per-domain log level overrides by @@ -507,6 +494,8 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth DCB : Data Center Bridging (DCB) operations DISPATCH : Dispatcher scripts AUDIT : Audit records + SYSTEMD : Messages from internal libsystemd + VPN_PLUGIN : logging messages from VPN plugins NONE : when given by itself logging is disabled ALL : all log domains @@ -517,6 +506,14 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth HW : deprecated alias for "PLATFORM" + + In general, the logfile should not contain passwords or private data. However, + you are always advised to check the file before posting it online or attaching + to a bug report. VPN_PLUGIN is special as it might reveal + private information of the VPN plugins with verbose levels. Therefore this domain + will be excluded when setting ALL or DEFAULT + to more verbose levels then INFO. + backend @@ -558,7 +555,7 @@ ipv6.ip6-privacy=0 Not all properties can be overwritten, only the following properties are supported to have their default values configured - (see nm-settings5 for details). + (see nm-settings5 for details). A default value is only consulted if the corresponding per-connection value explicitly allows for that. @@ -568,6 +565,13 @@ ipv6.ip6-privacy=0 connection.lldp + + ethernet.cloned-mac-address + If left unspecified, it defaults to "permanent". + + + ethernet.generate-mac-address-mask + ethernet.wake-on-lan @@ -595,9 +599,18 @@ ipv6.ip6-privacy=0 vpn.timeout If left unspecified, default value of 60 seconds is used. + + wifi.cloned-mac-address + If left unspecified, it defaults to "permanent". + + + wifi.generate-mac-address-mask + wifi.mac-address-randomization - If left unspecified, MAC address randomization is disabled. + If left unspecified, MAC address randomization is disabled. + This setting is deprecated for wifi.cloned-mac-address. + wifi.powersave @@ -608,7 +621,7 @@ ipv6.ip6-privacy=0 - + Sections You can configure multiple connection @@ -681,6 +694,100 @@ ipv6.ip6-privacy=1 + + <literal>device</literal> section + Contains per-device persistent configuration. + + + Example: + +[device] +match-device=interface-name:eth3 +unmanaged=1 + + + + Supported Properties + + The following properties can be configured per-device. + + + ignore-carrier + + + Specify devices for which NetworkManager will (partially) + ignore the carrier state. Normally, for + device types that support carrier-detect, such as Ethernet + and InfiniBand, NetworkManager will only allow a + connection to be activated on the device if carrier is + present (ie, a cable is plugged in), and it will + deactivate the device if carrier drops for more than a few + seconds. + + + A device with carrier ignored will allow activating connections on + that device even when it does not have carrier, provided + that the connection uses only statically-configured IP + addresses. Additionally, it will allow any active + connection (whether static or dynamic) to remain active on + the device when carrier is lost. + + + Note that the "carrier" property of NMDevices and device D-Bus + interfaces will still reflect the actual device state; it's just + that NetworkManager will not make use of that information. + + + This setting overwrites the deprecated main.ignore-carrier + setting above. + + + + + wifi.scan-rand-mac-address + + + Configures MAC address randomization of a Wi-Fi device during + scanning. This defaults to yes in which case + a random, locally-administered MAC address will be used. + The setting wifi.scan-generate-mac-address-mask + allows to influence the generated MAC address to use certain vendor + OUIs. + If disabled, the MAC address during scanning is left unchanged to + whatever is configured. + For the configured MAC address while the device is associated, see instead + the per-connection setting wifi.cloned-mac-address. + + + + + wifi.scan-generate-mac-address-mask + + + Like the per-connection settings ethernet.generate-mac-address-mask + and wifi.generate-mac-address-mask, this allows to configure the + generated MAC addresses during scanning. See nm-settings5 + for details. + + + + + + + + + Sections + + The [device] section works the same as the [connection] section. + That is, multiple sections that all start with the prefix "device" can be specified. + The settings "match-device" and "stop-match" are available to match a device section + on a device. The order of multiple sections is also top-down within the file and + later files overwrite previous settings. See + for details. + + + + <literal>connectivity</literal> section This section controls NetworkManager's optional connectivity @@ -963,7 +1070,8 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16 Device List Format The configuration options main.no-auto-default, main.ignore-carrier, - and keyfile.unmanaged-devices select devices based on a list of matchings. + keyfile.unmanaged-devices, connection*.match-device and + device*.match-device select devices based on a list of matchings. Devices can be specified using the following format: @@ -978,7 +1086,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16 HWADDR - Match the MAC address of the device. Globbing is not supported + Match the permanent MAC address of the device. Globbing is not supported interface-name:IFNAME @@ -993,7 +1101,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16 mac:HWADDR - Match the MAC address of the device. Globbing is not supported + Match the permanent MAC address of the device. Globbing is not supported s390-subchannels:HWADDR @@ -1040,11 +1148,11 @@ interface-name:vboxnet*,except:interface-name:vboxnet2 See Also - NetworkManager8, - nmcli1, - nmcli-examples7, - nm-online1, - nm-settings5, + NetworkManager8, + nmcli1, + nmcli-examples7, + nm-online1, + nm-settings5, nm-applet1, nm-connection-editor1 -- cgit 1.3.0-6-gf8a5