From 494f296a3baab08522617b24b1f126d8f9a17502 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 20 Jan 2016 16:26:51 +0100 Subject: Imported Upstream version 1.1.90 --- man/NetworkManager.conf.xml.in | 295 +++++++++++++++++++++++++++++++++++++---- 1 file changed, 266 insertions(+), 29 deletions(-) (limited to 'man/NetworkManager.conf.xml.in') diff --git a/man/NetworkManager.conf.xml.in b/man/NetworkManager.conf.xml.in index 029db24e..31c1cf8c 100644 --- a/man/NetworkManager.conf.xml.in +++ b/man/NetworkManager.conf.xml.in @@ -27,23 +27,39 @@ Copyright 2010 - 2014 Red Hat, Inc. /etc/NetworkManager/NetworkManager.conf, - /etc/NetworkManager/conf.d/name.conf + /etc/NetworkManager/conf.d/name.conf, + /usr/lib/NetworkManager/conf.d/name.conf, + /var/lib/NetworkManager/NetworkManager-intern.conf Description - This is a configuration file for NetworkManager. It is used + NetworkManager.conf is the configuration file for NetworkManager. It is used to set up various aspects of NetworkManager's behavior. The - location of the file may be changed through use of the - argument for NetworkManager. + location of the main file and configuration directories may be changed + through use of the , , + , and + argument for NetworkManager, respectively. If a default NetworkManager.conf is provided by your distribution's packages, you should not modify it, since your changes may get overwritten by package updates. Instead, you can add additional .conf - files to the conf.d directory. These will be read in order, - with later files overriding earlier ones. + files to the /etc/NetworkManager/conf.d directory. + These will be read in order, with later files overriding earlier ones. + Packages might install further configuration snippets to /usr/lib/NetworkManager/conf.d. + This directory is parsed first, even before NetworkManager.conf. + The loading of a file /usr/lib/NetworkManager/conf.d/name.conf + can be prevented by adding a file /etc/NetworkManager/conf.d/name.conf. + In this case, the file from the etc configuration shadows the file from the + system configuration directory. + + + NetworkManager can overwrite certain user configuration options via D-Bus or other internal + operations. In this case it writes those changes to /var/lib/NetworkManager/NetworkManager-intern.conf. + This file is not intended to be modified by the user, but it is read last and can shadow + user configuration from NetworkManager.conf. @@ -269,6 +285,20 @@ no-auto-default=* + + rc-manager + Set the resolv.conf + management mode. The default value depends on how NetworkManager + was built. + none: NetworkManager will directly + write changes to resolv.conf. + resolvconf: NetworkManager will run + resolvconf to update the DNS configuration. + netconfig: NetworkManager will run + netconfig to update the DNS configuration. + + + debug Comma separated list of options to aid @@ -301,8 +331,19 @@ no-auto-default=* hostname - Set a persistent hostname. + This key is deprecated and has no effect + since the hostname is now stored in /etc/hostname or other + system configuration files according to build options. + + + path + + The location where keyfiles are read and stored. + This defaults to "@NM_CONFIG_KEYFILE_PATH_DEFAULT@". + + + unmanaged-devices Set devices that should be ignored by @@ -363,7 +404,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth level The default logging verbosity level. - One of ERR, + One of OFF, ERR, WARN, INFO, DEBUG, TRACE. The ERR level logs only critical errors. WARN logs warnings that may @@ -381,12 +422,12 @@ 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. + TEAM, CONCHECK, DCB, DISPATCH, AUDIT. In addition, these special domains can be used: NONE, ALL, DEFAULT, DHCP, IP. You can specify per-domain log level overrides by adding a colon and a log level to any domain. E.g., - "WIFI:DEBUG". + "WIFI:DEBUG,WIFI_SCAN:OFF". Domain descriptions: @@ -403,7 +444,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth WIFI_SCAN : Wi-Fi scanning operations IP4 : IPv4-related operations IP6 : IPv6-related operations - AUTOIP4 : AutoIP (avahi) operations + AUTOIP4 : AutoIP operations DNS : Domain Name System related operations VPN : Virtual Private Network connections and operations SHARING : Connection sharing @@ -426,6 +467,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth CONCHECK : Connectivity check DCB : Data Center Bridging (DCB) operations DISPATCH : Dispatcher scripts + AUDIT : Audit records NONE : when given by itself logging is disabled ALL : all log domains @@ -437,6 +479,29 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth + + backend + The logging backend. Supported values + are "debug", "syslog", + "journal" and "journal-syslog-style. + "debug" uses syslog and logs to standard error. + "journal-syslog-style" prints the same message to journal + as it would print for "syslog", containing redundant + fields in the text. + If NetworkManager is started in debug mode (--debug) + this option is ignored and "debug" is always used. + Otherwise, the default is "@NM_CONFIG_LOGGING_BACKEND_DEFAULT_TEXT@". + + + + audit + Whether the audit records are delivered to + auditd, the audit daemon. If false, audit + records will be sent only to the NetworkManager logging + system. If set to true, they will be also + sent to auditd. The default value is @NM_CONFIG_DEFAULT_LOGGING_AUDIT_TEXT@. + + @@ -454,6 +519,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth [connection] ipv6.ip6-privacy=0 connection.autoconnect-slaves=1 +vpn.timeout=120 [connection-wifi-wlan0] match-device=interface-name:wlan0 @@ -513,9 +579,23 @@ ipv6.ip6-privacy=1 The following properties are supported to have their default values configured: + + connection.autoconnect-slaves + + + connection.lldp + + + ethernet.wake-on-lan + ipv4.route-metric + + ipv4.dhcp-timeout + If left unspecified, the default value for + the interface type is used. + ipv6.ip6-privacy If ipv6.ip6-privacy is unset, use the content of @@ -525,13 +605,15 @@ ipv6.ip6-privacy=1 ipv6.route-metric - - connection.autoconnect-slaves - - - ethernet.wake-on-lan - + + vpn.timeout + If left unspecified, default value of 60 seconds is used. + + + wifi.mac-address-randomization + If left unspecified, MAC address randomization is disabled. + @@ -574,6 +656,153 @@ ipv6.ip6-privacy=1 + + <literal>global-dns</literal> section + This section specifies global DNS settings that override + connection-specific configuration. + + + + searches + + + A list of search domains to be used during hostname lookup. + + + + + options + + + A list of of options to be passed to the hostname resolver. + + + + + + + + + <literal>global-dns-domain</literal> sections + Sections with a name starting with the "global-dns-domain-" + prefix allow to define global DNS configuration for specific + domains. The part of section name after "global-dns-domain-" + specifies the domain name a section applies to. More specific + domains have the precedence over less specific ones and the + default domain is represented by the wildcard "*". A default + domain section is mandatory. + + + + + servers + + + A list of addresses of DNS servers to be used for the given domain. + + + + + options + + + A list of domain-specific DNS options. Not used at the moment. + + + + + + + + + <literal>.config</literal> sections + This is a special section that contains options which apply + to the configuration file that contains the option. + + + + + enable + + + Defaults to "true". If "false", + the configuration file will be skipped during loading. + Note that the main configuration file NetworkManager.conf + cannot be disabled. + +# always skip loading the config file +[.config] +enable=false + + + + You can also match against the version of NetworkManager. For example + the following are valid configurations: + +# only load on version 1.0.6 +[.config] +enable=nm-version:1.0.6 + +# load on all versions 1.0.x, but not 1.2.x +[.config] +enable=nm-version:1.0 + +# only load on versions >= 1.1.6. This does not match +# with version 1.2.0 or 1.4.4. Only the last digit is considered. +[.config] +enable=nm-version-min:1.1.6 + +# only load on versions >= 1.2. Contrary to the previous +# example, this also matches with 1.2.0, 1.2.10, 1.4.4, etc. +[.config] +enable=nm-version-min:1.2 + +# Match against the maximum allowed version. The example matches +# versions 1.2.0, 1.2.2, 1.2.4. Again, only the last version digit +# is allowed to be smaller. So this would not match match on 1.1.10. +[.config] +enable=nm-version-max:1.2.6 + + + + You can also match against the value of the environment variable + NM_CONFIG_ENABLE_TAG, like: + +# always skip loading the file when running NetworkManager with +# environment variable "NM_CONFIG_ENABLE_TAG=TAG1" +[.config] +enable=env:TAG1 + + + + More then one match can be specified. The configuration will be + enabled if one of the predicates matches ("or"). The special prefix "except:" can + 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. + +# enable the configuration either when the environment variable +# is present or the version is at least 1.2.0. +[.config] +enable=env:TAG2,nm-version-min:1.2 + +# enable the configuration for version >= 1.2.0, but disable +# it when the environment variable is set to "TAG3" +[.config] +enable=except:env:TAG3,nm-version-min:1.2 + +# enable the configuration on >= 1.3, >= 1.2.6, and >= 1.0.16. +# Useful if a certain feature is only present since those releases. +[.config] +enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16 + + + + + + + + Plugins @@ -592,7 +821,7 @@ ipv6.ip6-privacy=1 The stored connection file may contain passwords and private keys, so it will be made readable only to root, and the plugin will ignore files that are readable or - writeable by any user or group other than root. + writable by any user or group other than root. This plugin is always active, and will automatically be @@ -611,6 +840,9 @@ ipv6.ip6-privacy=1 /etc/sysconfig/network-scripts/ifcfg-* files. It currently supports reading Ethernet, Wi-Fi, InfiniBand, VLAN, Bond, Bridge, and Team connections. + Enabling ifcfg-rh implicitly enables + ibft plugin, if it is available. + This can be disabled by adding no-ibft. @@ -619,12 +851,9 @@ ipv6.ip6-privacy=1 ifcfg-suse - This plugin is only provided for simple backward - compatibility with SUSE and OpenSUSE configuration. Most - setups should be using the keyfile - plugin instead. The ifcfg-suse plugin - supports reading Ethernet and Wi-Fi connections, but does - not support saving any connection types. + This plugin is deprecated and its selection has no effect. + The keyfile plugin should be used + instead. @@ -647,12 +876,16 @@ ipv6.ip6-privacy=1 - ibft + ibft, no-ibft This plugin allows to read iBFT configuration (iSCSI Boot Firmware Table). The configuration is read using /sbin/iscsiadm. Users are expected to configure iBFT connections via the firmware interfaces. + If ibft support is available, it is automatically enabled after + ifcfg-rh. This can be disabled by no-ibft. + You can also explicitly specify ibft to load the + plugin without ifcfg-rh or to change the plugin order. @@ -715,12 +948,16 @@ ipv6.ip6-privacy=1 SPEC[,;]SPEC - Multiple specs can be concatenated with comman or semicolon. The order does not matter as - matches are either positive (inclusive) or negative, with negative matches having higher priority. + Multiple specs can be concatenated with commas or semicolons. The order does not matter as + matches are either inclusive or negative (except:), with negative matches having higher + priority. + Backslash is supported to escape the separators ';' and ',', and to express special characters such as newline ('\n'), tabulator ('\t'), whitespace ('\s') and backslash ('\\'). The globbing of - interface names cannot be escaped. Whitespace is taken literally so usually the specs will be concatenated - without spaces. + interface names cannot be escaped. Whitespace is not a separator but will be trimmed between + two specs (unless escaped as '\s'). + + -- cgit 1.3.0-6-gf8a5