diff options
Diffstat (limited to 'man/NetworkManager.conf.xml')
| -rw-r--r-- | man/NetworkManager.conf.xml | 92 |
1 files changed, 82 insertions, 10 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 94a23fe8..28934247 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. + </para><para> + 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 <command>nmcli connection reload</command> + or <command>nmcli connection load "$FILENAME"</command>. Even better, + instead of modifying files directly, use NetworkManager tools like + <command>nmcli</command>, <command>nmtui</command> or the GUI. + </para><para> + This setting is deprecated and will have no effect in the future. </para></listitem> </varlistentry> <varlistentry> @@ -204,7 +213,7 @@ plugins-=remove-me <para>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 - <filename>/run/NetworkManager/no-auto-default.state</filename> + <filename>&nmstatedir;/no-auto-default.state</filename> to prevent creating the default connection for that device again.</para> <para>See <xref linkend="device-spec"/> 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 <literal>true</literal>, - 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=* </varlistentry> <varlistentry> <term><varname>dns</varname></term> - <listitem><para>Set the DNS (<filename>resolv.conf</filename>) processing mode. - If the key is unspecified, <literal>default</literal> is used, + <listitem><para>Set the DNS processing mode.</para> + <para>If the key is unspecified, <literal>default</literal> is used, unless <filename>/etc/resolv.conf</filename> is a symlink to <filename>/run/systemd/resolve/stub-resolv.conf</filename>, <filename>/run/systemd/resolve/resolv.conf</filename>, @@ -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).</para> + <para><literal>systemd-resolved</literal>: NetworkManager will + push the DNS configuration to systemd-resolved</para> <para><literal>unbound</literal>: NetworkManager will talk to unbound and dnssec-triggerd, providing a "split DNS" configuration with DNSSEC support. <filename>/etc/resolv.conf</filename> will be managed by dnssec-trigger daemon.</para> - <para><literal>systemd-resolved</literal>: NetworkManager will - push the DNS configuration to systemd-resolved</para> <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>, <literal>systemd-resolved</literal> + and <literal>unbound</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> </listitem> </varlistentry> @@ -380,6 +397,22 @@ no-auto-default=* </varlistentry> <varlistentry> + <term><varname>systemd-resolved</varname></term> + <listitem><para>Send the connection DNS configuration to + <literal>systemd-resolved</literal>. Defaults to "<literal>true</literal>". + </para> + <para>Note that this setting is complementary to the + <varname>dns</varname> setting. You can keep this enabled while using + <varname>dns</varname> set to another DNS plugin alongside + <literal>systemd-resolved</literal>, or <varname>dns</varname> set to + <literal>systemd-resolved</literal> to configure the system resolver to use + <literal>systemd-resolved</literal>.</para> + <para>If systemd-resolved is enabled, the connectivity check resolves the + hostname per-device.</para> + </listitem> + </varlistentry> + + <varlistentry> <term><varname>debug</varname></term> <listitem><para>Comma separated list of options to aid debugging. This value will be combined with the environment @@ -641,6 +674,8 @@ ipv6.ip6-privacy=0 (see <link linkend='nm-settings'><citerefentry><refentrytitle>nm-settings</refentrytitle><manvolnum>5</manvolnum></citerefentry></link> for details). A default value is only consulted if the corresponding per-connection value explicitly allows for that. + <!-- The following comment is used by check-config-options.sh, don't remove it. --> + <!-- start connection defaults --> <variablelist> <varlistentry> <term><varname>802-1x.auth-timeout</varname></term> @@ -705,6 +740,11 @@ ipv6.ip6-privacy=0 the interface type is used.</para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv4.dns-priority</varname></term> + <listitem><para>If unspecified or zero, use 50 for VPN profiles + and 100 for other profiles.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>ipv4.route-metric</varname></term> </varlistentry> <varlistentry> @@ -724,6 +764,11 @@ ipv6.ip6-privacy=0 the interface type is used.</para></listitem> </varlistentry> <varlistentry> + <term><varname>ipv6.dns-priority</varname></term> + <listitem><para>If unspecified or zero, use 50 for VPN profiles + and 100 for other profiles.</para></listitem> + </varlistentry> + <varlistentry> <term><varname>ipv6.ip6-privacy</varname></term> <listitem><para>If <literal>ipv6.ip6-privacy</literal> is unset, use the content of "/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback. @@ -782,7 +827,12 @@ ipv6.ip6-privacy=0 <varlistentry> <term><varname>wifi.wake-on-wlan</varname></term> </varlistentry> + <varlistentry> + <term><varname>wireguard.mtu</varname></term> + </varlistentry> </variablelist> + <!-- The following comment is used by check-config-options.sh, don't remove it. --> + <!-- end connection defaults --> </para> </refsect2> @@ -1009,11 +1059,28 @@ managed=1 <refsect1> <title><literal>connectivity</literal> section</title> + <para>This section controls NetworkManager's optional connectivity checking functionality. This allows NetworkManager to detect whether or not the system can actually access the internet or whether it is behind a captive portal.</para> + <para>Connectivity checking serves two purposes. For one, it exposes + a connectivity state on D-Bus, which other applications may use. For example, + Gnome's portal helper uses this as signal to show a captive portal login + page. + The other use is that default-route of devices without global connectivity + get a penalty of +20000 to the route-metric. This has the purpose to give a + better default-route to devices that have global connectivity. For example, + when being connected to WWAN and to a Wi-Fi network which is behind a captive + portal, WWAN still gets preferred until login.</para> + + <para>Note that your distribution might set <literal>/proc/sys/net/ipv4/conf/*/rp_filter</literal> to + strict filtering. That works badly with per-device connectivity checking, + which uses SO_BINDDEVICE to send requests on all devices. A strict rp_filter + setting will reject any response and the connectivity check on all but the + best route will fail.</para> + <para> <variablelist> <varlistentry> @@ -1037,10 +1104,15 @@ managed=1 </varlistentry> <varlistentry> <term><varname>response</varname></term> - <listitem><para>If set controls what body content + <listitem><para>If set, controls what body content NetworkManager checks for when requesting the URI for - connectivity checking. If missing, defaults to - "NetworkManager is online" </para></listitem> + connectivity checking. Note that this only compares + that the HTTP response starts with the specifid 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". + If set to empty, the HTTP server is expected to answer with + status code 204 or send no data.</para></listitem> </varlistentry> </variablelist> </para> @@ -1064,7 +1136,7 @@ managed=1 <term><varname>options</varname></term> <listitem> <para> - A list of of options to be passed to the hostname resolver. + A list of options to be passed to the hostname resolver. </para> </listitem> </varlistentry> |