diff options
Diffstat (limited to 'man/NetworkManager.conf.xml')
| -rw-r--r-- | man/NetworkManager.conf.xml | 94 |
1 files changed, 78 insertions, 16 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 474e7951..46528879 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -167,17 +167,14 @@ plugins-=remove-me </varlistentry> <varlistentry> <term><varname>dhcp</varname></term> - <listitem><para>This key sets up what DHCP client - NetworkManager will use. Allowed values depend on build configuration and - typically include <literal>internal</literal> and <literal>dhcpcd</literal>. - Support for unmaintained <literal>dhclient</literal> client has been deprecated - and disabled by default.</para> + <listitem><para>This key sets up what DHCP client NetworkManager will + use. Allowed values depend on build configuration; this version of + NetworkManager was built with support for the following clients: + &NM_DHCP_CLIENTS_ENABLED_TEXT;.</para> <para>The <literal>internal</literal> client is built-in, while other options may require an external DHCP client to be installed.</para> <para>If this key is missing, <literal>&NM_CONFIG_DEFAULT_MAIN_DHCP;</literal> - is used with a fallback to other suppored clients in this order: - <literal>internal</literal>, <literal>dhcpcd</literal>, - <literal>dhclient</literal>.</para></listitem> + is used with a fallback to other supported clients.</para></listitem> </varlistentry> <varlistentry> <term><varname>no-auto-default</varname></term> @@ -335,20 +332,24 @@ no-auto-default=* <para><literal>systemd-resolved</literal>: NetworkManager will push the DNS configuration to systemd-resolved</para> + <para><literal>dnsconfd</literal>: NetworkManager will + push the DNS configuration to dnsconfd</para> and by default set ipvX.routed-dns to + yes, so servers are contacted through right interfaces. + <para><literal>none</literal>: NetworkManager will not modify resolv.conf. This implies <literal>rc-manager</literal> <literal>unmanaged</literal></para> - <para>Note that the plugins <literal>dnsmasq</literal> and <literal>systemd-resolved</literal> - are caching local nameservers. + <para>Note that the plugins <literal>dnsmasq</literal>,<literal>systemd-resolved</literal> + and <literal>dnsconfd</literal> are caching local nameservers. Hence, when NetworkManager writes <filename>&nmrundir;/resolv.conf</filename> and <filename>/etc/resolv.conf</filename> (according to <literal>rc-manager</literal> setting below), the name server there will be localhost only. NetworkManager also writes a file <filename>&nmrundir;/no-stub-resolv.conf</filename> that contains the original name servers pushed to the DNS plugin.</para> - <para>When using <literal>dnsmasq</literal> and <literal>systemd-resolved</literal>, - per-connection added dns servers will always be queried using + <para>When using <literal>dnsmasq</literal>,<literal>systemd-resolved</literal> and + <literal>dnsconfd</literal> per-connection added dns servers will always be queried using the device the connection has been activated on.</para> </listitem> </varlistentry> @@ -360,7 +361,7 @@ no-auto-default=* management mode. This option is about how NetworkManager writes to <filename>/etc/resolv.conf</filename>, if at all. The default value depends on NetworkManager build - options, and this version of NetworkManager was build with a default of + options, and this version of NetworkManager was built with a default of "<literal>&NM_CONFIG_DEFAULT_MAIN_RC_MANAGER;</literal>". Regardless of this setting, NetworkManager will always write its version of resolv.conf to its runtime state directory @@ -869,6 +870,10 @@ ipv6.ip6-privacy=0 <listitem><para>Whether the connection will be brought down before the system is powered off.</para></listitem> </varlistentry> <varlistentry> + <term><varname>connection.ip-ping-addresses-require-all</varname></term> + <listitem><para>Whether it is sufficient for any ping check to succeed among the list of target addresses, or if all ping checks must succeed for the entire list of target addresses.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>connection.mud-url</varname></term> <listitem><para>If unspecified, MUD URL defaults to <literal>"none"</literal>.</para></listitem> </varlistentry> @@ -938,6 +943,9 @@ ipv6.ip6-privacy=0 <listitem><para>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 a default of 1500.</para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv4.routed-dns</varname></term> + </varlistentry> + <varlistentry> <term><varname>ipv4.dad-timeout</varname></term> </varlistentry> <varlistentry> @@ -951,10 +959,18 @@ ipv6.ip6-privacy=0 <listitem><para>If left unspecified, it defaults to "ifname".</para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv4.dhcp-ipv6-only-preferred</varname></term> + <listitem><para>If left unspecified, the "IPv6-only preferred" DHCPv4 option is disabled.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>ipv4.dhcp-hostname-flags</varname></term> <listitem><para>If left unspecified, the value 3 (fqdn-encoded,fqdn-serv-update) is used.</para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv4.dhcp-send-hostname</varname></term> + <listitem><para>Whether a hostname is sent to the DHCP server when acquiring a lease. When the property is not specified in the connection, the global value from NetworkManager configuration is looked up. If the global value is not set, the value from ipv4.dhcp-send-hostname-deprecated, which defaults to true, is used for backwards compatibility. In the future this will change and, in absence of a global default, it will always fallback to true.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>ipv4.dhcp-send-release</varname></term> <listitem><para>Whether the DHCP client will send RELEASE message when bringing the connection down.</para></listitem> </varlistentry> @@ -990,6 +1006,9 @@ ipv6.ip6-privacy=0 </para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv6.routed-dns</varname></term> + </varlistentry> + <varlistentry> <term><varname>ipv6.addr-gen-mode</varname></term> <listitem><para>If the per-profile setting is either "default" or "default-or-eui64", the global default is used. If the default is unspecified, the fallback value is either "stable-privacy" @@ -1012,6 +1031,10 @@ ipv6.ip6-privacy=0 <listitem><para>If left unspecified, the value 1 (fqdn-serv-update) is used.</para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv6.dhcp-send-hostname</varname></term> + <listitem><para>Whether a hostname is sent to the DHCP server when acquiring a lease. When the property is not specified in the connection, the global value from NetworkManager configuration is looked up. If the global value is not set, the value from ipv6.dhcp-send-hostname-deprecated, which defaults to true, is used for backwards compatibility. In the future this will change and, in absence of a global default, it will always fallback to true.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>ipv6.dhcp-send-release</varname></term> <listitem><para>Whether the DHCP client will send RELEASE message when bringing the connection down.</para></listitem> </varlistentry> @@ -1495,7 +1518,7 @@ managed=1 <listitem><para>If set, controls what body content NetworkManager checks for when requesting the URI for connectivity checking. Note that this only compares - that the HTTP response starts with the specifid text, + that the HTTP response starts with the specified 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". @@ -1528,6 +1551,29 @@ managed=1 </para> </listitem> </varlistentry> + <varlistentry> + <term><varname>resolve-mode</varname></term> + <listitem> + <para> + String indicating how DNS servers retrieved from global configuration and connections + should be used. <literal>backup</literal> - Indicates that they can be freely merged + and used for the same purposes. <literal>prefer</literal> - Forbids DNS servers + retrieved from connections to be used for general queries that are not subdomains of + domains set by connection. <literal>exclusive</literal> - Forbids use of connection + DNS servers for any query. Currently relevant only for Dnsconfd plugin. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><varname>certification-authority</varname></term> + <listitem> + <para> + String specifying absolute path to bundle of CA certificates that must be used for + validation of certificates presented by DNS servers when encrypted DNS is used. + Currently relevant only for Dnsconfd plugin. + </para> + </listitem> + </varlistentry> </variablelist> </para> </refsect1> @@ -1553,8 +1599,24 @@ managed=1 <term><varname>servers</varname></term> <listitem> <para> - A list of addresses of DNS servers to be used for the given domain. - </para> + A list of addresses of DNS servers to be used for the + given domain. Each server can be specified either as a + plain IP address or with a URI syntax. When it is + specified as an URI, the following forms are supported: + </para> + <para> + <simplelist type="horiz" columns="1"> + <member>dns+udp://<varname>ADDRESS</varname>[:<varname>PORT</varname>] : DNS</member> + <member>dns+tls://<varname>ADDRESS</varname>[:<varname>PORT</varname>][#<varname>SERVERNAME]</varname> : DNS over TLS</member> + </simplelist> + </para> + <para> + <varname>ADDRESS</varname> is an IPv4 or IPv6 + address. When it is IPv6, it must be enclosed in square + brackets ('[' and ']'). When it is a IPv6 link-local + address, the address should be followed by a percent + sign ('%') and an interface name. + </para> </listitem> </varlistentry> <varlistentry> |