From ab0efddcdb48d800e2f938da54cfe3074640792e Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 26 Aug 2022 20:36:29 +0200 Subject: New upstream version 1.40.0 --- NEWS | 11 ++- configure | 28 +++---- configure.ac | 4 +- docs/api/html/NetworkManager.conf.html | 2 +- docs/api/html/NetworkManager.devhelp2 | 13 ++-- docs/api/html/index.html | 2 +- docs/api/html/nm-dbus-types.html | 23 +++++- docs/api/html/nm-settings-dbus.html | 18 +++-- docs/api/html/nm-settings-nmcli.html | 17 ++-- docs/api/version.xml | 2 +- docs/libnm/html/NMRemoteConnection.html | 11 +-- docs/libnm/html/NMVpnConnection.html | 8 +- docs/libnm/html/NMVpnPluginOld.html | 12 +-- docs/libnm/html/NMVpnServicePlugin.html | 6 +- docs/libnm/html/api-index-full.html | 8 +- docs/libnm/html/index.html | 2 +- docs/libnm/html/libnm-nm-dbus-interface.html | 35 +++++++-- docs/libnm/html/libnm.devhelp2 | 5 +- docs/libnm/html/object-tree.html | 8 +- docs/libnm/html/usage.html | 2 +- docs/libnm/version.xml | 2 +- man/NetworkManager-dispatcher.8 | 4 +- man/NetworkManager-wait-online.service.8 | 4 +- man/NetworkManager.8 | 6 +- man/NetworkManager.conf.5 | 11 +-- man/NetworkManager.conf.xml | 2 +- man/nm-cloud-setup.8 | 6 +- man/nm-initrd-generator.8 | 6 +- man/nm-online.1 | 6 +- man/nm-openvswitch.7 | 6 +- man/nm-settings-dbus.5 | 24 +++--- man/nm-settings-dbus.xml | 20 ++--- man/nm-settings-docs-dbus.xml | 24 +++--- man/nm-settings-docs-nmcli.xml | 4 +- man/nm-settings-ifcfg-rh.5 | 6 +- man/nm-settings-ifcfg-rh.xml | 2 +- man/nm-settings-keyfile.5 | 6 +- man/nm-settings-keyfile.xml | 2 +- man/nm-settings-nmcli.5 | 24 +++--- man/nm-settings-nmcli.xml | 8 +- man/nmcli-examples.7 | 6 +- man/nmcli.1 | 6 +- man/nmtui.1 | 6 +- meson.build | 2 +- po/NetworkManager.pot | 88 +++++++++++---------- po/as.po | 86 ++++++++++---------- po/be@latin.po | 86 ++++++++++---------- po/bg.po | 86 ++++++++++---------- po/bn_IN.po | 86 ++++++++++---------- po/bs.po | 86 ++++++++++---------- po/ca.po | 86 ++++++++++---------- po/cs.po | 86 ++++++++++---------- po/da.po | 86 ++++++++++---------- po/de.po | 86 ++++++++++---------- po/dz.po | 86 ++++++++++---------- po/el.po | 86 ++++++++++---------- po/en_CA.po | 86 ++++++++++---------- po/en_GB.po | 86 ++++++++++---------- po/eo.po | 86 ++++++++++---------- po/es.po | 86 ++++++++++---------- po/et.po | 86 ++++++++++---------- po/eu.po | 86 ++++++++++---------- po/fi.po | 86 ++++++++++---------- po/fr.gmo | Bin 383733 -> 382745 bytes po/fr.po | 95 +++++++++++++---------- po/gd.po | 86 ++++++++++---------- po/gl.po | 86 ++++++++++---------- po/gu.po | 86 ++++++++++---------- po/he.po | 86 ++++++++++---------- po/hi.po | 86 ++++++++++---------- po/hr.gmo | Bin 365685 -> 364800 bytes po/hr.po | 95 +++++++++++++---------- po/hu.po | 86 ++++++++++---------- po/id.po | 86 ++++++++++---------- po/it.po | 86 ++++++++++---------- po/ja.gmo | Bin 410188 -> 409135 bytes po/ja.po | 95 +++++++++++++---------- po/ka.po | 86 ++++++++++---------- po/kn.po | 86 ++++++++++---------- po/ko.gmo | Bin 394637 -> 393690 bytes po/ko.po | 95 +++++++++++++---------- po/ku.po | 86 ++++++++++---------- po/lt.po | 86 ++++++++++---------- po/lv.po | 86 ++++++++++---------- po/mk.po | 86 ++++++++++---------- po/ml.po | 86 ++++++++++---------- po/mr.po | 86 ++++++++++---------- po/nb.po | 86 ++++++++++---------- po/ne.po | 86 ++++++++++---------- po/nl.po | 86 ++++++++++---------- po/oc.po | 86 ++++++++++---------- po/or.po | 86 ++++++++++---------- po/pa.po | 86 ++++++++++---------- po/pl.po | 86 ++++++++++---------- po/pt.po | 86 ++++++++++---------- po/pt_BR.po | 86 ++++++++++---------- po/ro.po | 86 ++++++++++---------- po/ru.gmo | Bin 544988 -> 543682 bytes po/ru.po | 95 +++++++++++++---------- po/rw.po | 86 ++++++++++---------- po/sk.po | 86 ++++++++++---------- po/sl.po | 86 ++++++++++---------- po/sq.po | 86 ++++++++++---------- po/sr.po | 86 ++++++++++---------- po/sr@latin.po | 86 ++++++++++---------- po/sv.po | 86 ++++++++++---------- po/ta.po | 86 ++++++++++---------- po/te.po | 86 ++++++++++---------- po/th.po | 86 ++++++++++---------- po/tr.po | 86 ++++++++++---------- po/uk.gmo | Bin 620351 -> 619135 bytes po/uk.po | 95 +++++++++++++---------- po/vi.po | 86 ++++++++++---------- po/wa.po | 86 ++++++++++---------- po/zh_CN.gmo | Bin 370426 -> 369599 bytes po/zh_CN.po | 95 +++++++++++++---------- po/zh_HK.po | 86 ++++++++++---------- po/zh_TW.po | 86 ++++++++++---------- src/core/devices/nm-device-bond.c | 2 +- src/core/devices/nm-device-ethernet.c | 2 +- src/core/devices/nm-device.c | 80 +++++++++++-------- src/core/devices/nm-device.h | 2 +- src/core/devices/wifi/nm-device-wifi.c | 4 +- src/core/nm-l3cfg.c | 8 +- src/core/nm-manager.c | 2 +- src/libnm-client-impl/nm-remote-connection.c | 6 +- src/libnm-client-impl/nm-settings-docs-gir.xml | 20 ++--- src/libnm-client-public/nm-remote-connection.h | 1 - src/libnm-core-aux-intern/nm-libnm-core-utils.c | 12 +-- src/libnm-core-aux-intern/nm-libnm-core-utils.h | 12 +-- src/libnm-core-impl/nm-setting-connection.c | 47 +++++------ src/libnm-core-impl/nm-setting-ip-config.c | 12 +-- src/libnm-core-impl/tests/test-general.c | 6 ++ src/libnm-core-public/nm-dbus-interface.h | 27 +++++-- src/libnm-core-public/nm-dbus-types.xml | 13 +++- src/libnm-core-public/nm-version-macros.h | 4 +- src/libnm-glib-aux/nm-enum-utils.c | 6 +- src/libnmc-setting/settings-docs-input.xml | 24 +++--- src/libnmc-setting/settings-docs.h | 6 +- src/libnmc-setting/settings-docs.h.in | 6 +- src/nmcli/generate-docs-nm-settings-nmcli.xml | 6 +- src/nmcli/generate-docs-nm-settings-nmcli.xml.in | 6 +- src/tests/client/test-client.py | 43 +++++++--- 143 files changed, 3451 insertions(+), 3143 deletions(-) diff --git a/NEWS b/NEWS index 70feb554..8282b0fe 100644 --- a/NEWS +++ b/NEWS @@ -3,11 +3,6 @@ NetworkManager-1.40 Overview of changes since NetworkManager-1.38 ============================================= -This is a snapshot of NetworkManager development. The API is -subject to change and not guaranteed to be compatible with -the later release. -USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE! - * Drop unused, internal systemd DHCPv4 client. This is long replaced by nettools' n-dhcp4 implementation. * The nmcli command now supports --offline argument with "add" and @@ -44,6 +39,9 @@ USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE! * Improve the reapply of non-bridge properties. * Honor adding a Bluetooth NAP connection with all available methods. * Improve carrier detection. +* During the build, stop relying on intltool for i18n and use gettext only. +* Undeprecate nm_remote_connection_get_secrets() in libnm. +* NetworkManager now will restart DHCP if the MAC changes on a device. * Several internal improvements. The following changes were backported to 1.38.x releases between 1.38.0 @@ -51,8 +49,9 @@ and 1.38.4 are also present in NetworkManager-1.40: - 1.38.4 +* Fix DAD for DHCPv6 addresses. * Wi-Fi: improvements for OWE networks. -* Support EC private keys +* Support EC private keys. * Fix nmcli tab completion support for embedded quote characters. * Fix reapply for lldp/mdns/llmnr/dns-over-tls settings. * Various bugfixes. diff --git a/configure b/configure index 88cce407..fe690381 100755 --- a/configure +++ b/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.71 for NetworkManager 1.39.90. +# Generated by GNU Autoconf 2.71 for NetworkManager 1.40.0. # # Report bugs to . # @@ -622,8 +622,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='NetworkManager' PACKAGE_TARNAME='NetworkManager' -PACKAGE_VERSION='1.39.90' -PACKAGE_STRING='NetworkManager 1.39.90' +PACKAGE_VERSION='1.40.0' +PACKAGE_STRING='NetworkManager 1.40.0' PACKAGE_BUGREPORT='http://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager' PACKAGE_URL='' @@ -1744,7 +1744,7 @@ if test "$ac_init_help" = "long"; then # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures NetworkManager 1.39.90 to adapt to many kinds of systems. +\`configure' configures NetworkManager 1.40.0 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1816,7 +1816,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of NetworkManager 1.39.90:";; + short | recursive ) echo "Configuration of NetworkManager 1.40.0:";; esac cat <<\_ACEOF @@ -2171,7 +2171,7 @@ fi test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -NetworkManager configure 1.39.90 +NetworkManager configure 1.40.0 generated by GNU Autoconf 2.71 Copyright (C) 2021 Free Software Foundation, Inc. @@ -2892,7 +2892,7 @@ cat >config.log <<_ACEOF This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by NetworkManager $as_me 1.39.90, which was +It was created by NetworkManager $as_me 1.40.0, which was generated by GNU Autoconf 2.71. Invocation command line was $ $0$ac_configure_args_raw @@ -4388,7 +4388,7 @@ fi # Define the identity of the package. PACKAGE='NetworkManager' - VERSION='1.39.90' + VERSION='1.40.0' printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h @@ -19327,9 +19327,9 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu NM_MAJOR_VERSION=1 -NM_MINOR_VERSION=39 -NM_MICRO_VERSION=90 -NM_VERSION=1.39.90 +NM_MINOR_VERSION=40 +NM_MICRO_VERSION=0 +NM_VERSION=1.40.0 @@ -19337,7 +19337,7 @@ NM_VERSION=1.39.90 -NM_GIT_SHA=b2a6b9fcc74f94bf3bbef7c382d6b85f0442f288 +NM_GIT_SHA=5d4802f7d869e2a91192dc75bf33cff892a3facf if test """" != "no-config-h" ; then @@ -32768,7 +32768,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1 # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by NetworkManager $as_me 1.39.90, which was +This file was extended by NetworkManager $as_me 1.40.0, which was generated by GNU Autoconf 2.71. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -32836,7 +32836,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_config='$ac_cs_config_escaped' ac_cs_version="\\ -NetworkManager config.status 1.39.90 +NetworkManager config.status 1.40.0 configured by $0, generated by GNU Autoconf 2.71, with options \\"\$ac_cs_config\\" diff --git a/configure.ac b/configure.ac index 3bf27261..91548ed1 100644 --- a/configure.ac +++ b/configure.ac @@ -7,8 +7,8 @@ dnl - add corresponding NM_VERSION_x_y_z macros in dnl "shared/nm-version-macros.h.in" dnl - update number in meson.build m4_define([nm_major_version], [1]) -m4_define([nm_minor_version], [39]) -m4_define([nm_micro_version], [90]) +m4_define([nm_minor_version], [40]) +m4_define([nm_micro_version], [0]) m4_define([nm_version], [nm_major_version.nm_minor_version.nm_micro_version]) diff --git a/docs/api/html/NetworkManager.conf.html b/docs/api/html/NetworkManager.conf.html index e2bd8c54..34063973 100644 --- a/docs/api/html/NetworkManager.conf.html +++ b/docs/api/html/NetworkManager.conf.html @@ -818,7 +818,7 @@ ipv6.ip6-privacy=0

connection.mptcp-flags

-

If unspecified, the fallback is either 0 ("disabled") or 0x22 ("enabled-on-global-iface,subflow"), depending on /proc/sys/net/mptcp/enabled.

+

If unspecified, the fallback is 0x22 ("enabled,subflow"). Note that if sysctl /proc/sys/net/mptcp/enabled is disabled, NetworkManager will still not configure endpoints.

connection.dns-over-tls

diff --git a/docs/api/html/NetworkManager.devhelp2 b/docs/api/html/NetworkManager.devhelp2 index 7fd00dea..257f6bde 100644 --- a/docs/api/html/NetworkManager.devhelp2 +++ b/docs/api/html/NetworkManager.devhelp2 @@ -852,12 +852,13 @@ - - - - - - + + + + + + + diff --git a/docs/api/html/index.html b/docs/api/html/index.html index 89e8f738..e753eef1 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@

- for NetworkManager 1.39.90 + for NetworkManager 1.40.0 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/api/latest/. diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 9935f48c..46152667 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -5366,7 +5366,7 @@ -

NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE

+

NM_MPTCP_FLAGS_ENABLED

@@ -5374,14 +5374,14 @@

-

MPTCP handling is enabled or disabled depending on whether a /0 default route (either IPv4 or IPv6) is configured in the main routing table.

+

MPTCP is enabled and endpoints will be configured. This flag is implied if any of the other flags indicate that MPTCP is enabled and therefore in most cases unnecessary. Note that if "/proc/sys/net/mptcp/enabled" sysctl is disabled, MPTCP handling is disabled despite this flag. This can be overruled with the "also-without-sysctl" flag. Note that by default interfaces that don't have a default route are excluded from having MPTCP endpoints configured. This can be overruled with the "also-without-default-route" and this affects endpoints per address family.

  -

NM_MPTCP_FLAGS_ENABLED

+

NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL

@@ -5389,7 +5389,22 @@

-

MPTCP is enabled and endpoints will be configured. This flag is implied if any of the other flags indicate that MPTCP is enabled and therefore in most cases unnecessary.

+

even if MPTCP handling is enabled via the "enabled" flag, it is ignored unless "/proc/sys/net/mptcp/enabled" is on. With this flag, MPTCP endpoints will be configured regardless of the sysctl setting.

+

+ +  + + + +

NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE

+

+ + +

= 0x8

+

+ + +

even if MPTCP handling is enabled via the "enabled" flag, it is ignored per-address family unless NetworkManager configures a default route. With this flag, NetworkManager will also configure MPTCP endpoints if there is no default route. This takes effect per-address family.

  diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index f0aed252..0903c329 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -245,13 +245,15 @@ If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. + The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + + If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. @@ -1805,9 +1807,9 @@   The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". @@ -2099,9 +2101,9 @@   The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index 672f9e43..6968e035 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -217,10 +217,11 @@

Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.

If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.

-

The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured.

-

The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags.

-

If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.

-

If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled".

+

The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.

+

Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.

+

Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.

+

When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.

+

If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.

NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.

Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).

@@ -2156,8 +2157,8 @@

Alias: gw4

The gateway associated with this configuration. This is only meaningful if "addresses" is also set.

-

The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default.

-

As an alternative to set the gateway, configure a static default route with /0 as prefix length.

+

Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.

+

Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".

Format: string

@@ -2453,8 +2454,8 @@ Example: priority 5 from 192.167.4.0/24 table 45

Alias: gw6

The gateway associated with this configuration. This is only meaningful if "addresses" is also set.

-

The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default.

-

As an alternative to set the gateway, configure a static default route with /0 as prefix length.

+

Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.

+

Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".

Format: string

diff --git a/docs/api/version.xml b/docs/api/version.xml index d3781d71..32b7211c 100644 --- a/docs/api/version.xml +++ b/docs/api/version.xml @@ -1 +1 @@ -1.39.90 +1.40.0 diff --git a/docs/libnm/html/NMRemoteConnection.html b/docs/libnm/html/NMRemoteConnection.html index fbb6a70b..dedf951f 100644 --- a/docs/libnm/html/NMRemoteConnection.html +++ b/docs/libnm/html/NMRemoteConnection.html @@ -803,10 +803,6 @@ nm_remote_connection_get_secrets (const char *setting_name, GCancellable *cancellable, GError **error); -
-

nm_remote_connection_get_secrets has been deprecated since version 1.22 and should not be used in newly-written code.

-

Use nm_remote_connection_get_secrets_async() or GDBusConnection.

-

Request the connection's secrets. Note that this is a blocking D-Bus call, not a simple property accessor.

@@ -845,7 +841,12 @@ not a simple property accessor.

Returns

a GVariant of type NM_VARIANT_TYPE_CONNECTION containing connection -'s secrets, or NULL on error.

+'s secrets, or NULL on error.

+

Warning: NMClient contains a cache of objects on D-Bus. This cache gets updated +with D-Bus signals when iterating the GMainContext. This function performs a +(pseudo) blocking D-Bus call. Aside blocking, the result will not be in sync +and not be ordered with the content of the NMClient cache. +This function used to be deprecated between 1.22 and 1.38 releases.

[transfer full]

diff --git a/docs/libnm/html/NMVpnConnection.html b/docs/libnm/html/NMVpnConnection.html index 6dfe6f8b..1aeca777 100644 --- a/docs/libnm/html/NMVpnConnection.html +++ b/docs/libnm/html/NMVpnConnection.html @@ -44,7 +44,7 @@ -NMVpnConnectionState +NMVpnConnectionState nm_vpn_connection_get_vpn_state () @@ -76,7 +76,7 @@ Read -NMVpnConnectionState +NMVpnConnectionState vpn-state Read @@ -136,7 +136,7 @@

Functions

nm_vpn_connection_get_vpn_state ()

-
NMVpnConnectionState
+
NMVpnConnectionState
 nm_vpn_connection_get_vpn_state (NMVpnConnection *vpn);

 
Gets the current NMVpnConnection state.

 

@@ -219,7 +219,7 @@ string used by the connection, and must not be modified.

 

 

 
The “vpn-state” property

-
  “vpn-state”                NMVpnConnectionState

+
  “vpn-state”                NMVpnConnectionState

 
The VPN state of the active VPN connection.

 
Owner: NMVpnConnection

 
Flags: Read

diff --git a/docs/libnm/html/NMVpnPluginOld.html b/docs/libnm/html/NMVpnPluginOld.html
index 4d623fe2..bf6a322c 100644
--- a/docs/libnm/html/NMVpnPluginOld.html
+++ b/docs/libnm/html/NMVpnPluginOld.html
@@ -53,7 +53,7 @@
 
 
 
-NMVpnServiceState
+NMVpnServiceState
 
 
 nm_vpn_plugin_old_get_state ()
@@ -158,7 +158,7 @@
 Read / Write / Construct Only
 
 
-NMVpnServiceState
+NMVpnServiceState
 state
 Read / Write
 
@@ -274,7 +274,7 @@ nm_vpn_plugin_old_get_connection (
 

 
nm_vpn_plugin_old_get_state ()

-
NMVpnServiceState
+
NMVpnServiceState
 nm_vpn_plugin_old_get_state (NMVpnPluginOld *plugin);

 

 
nm_vpn_plugin_old_get_state has been deprecated since version 1.2 and should not be used in newly-written code.

@@ -286,7 +286,7 @@ nm_vpn_plugin_old_get_state (
nm_vpn_plugin_old_set_state ()

 
void
 nm_vpn_plugin_old_set_state (NMVpnPluginOld *plugin,
-                             NMVpnServiceState state);

+                             NMVpnServiceState state);

 

 
nm_vpn_plugin_old_set_state has been deprecated since version 1.2 and should not be used in newly-written code.

 
Replaced by NMVpnServicePlugin.

@@ -352,7 +352,7 @@ nm_vpn_plugin_old_set_login_banner (
nm_vpn_plugin_old_failure ()

 
void
 nm_vpn_plugin_old_failure (NMVpnPluginOld *plugin,
-                           NMVpnPluginFailure reason);

+                           NMVpnPluginFailure reason);

nm_vpn_plugin_old_failure has been deprecated since version 1.2 and should not be used in newly-written code.

Replaced by NMVpnServicePlugin.

@@ -535,7 +535,7 @@ to flags,

The “state” property

-
  “state”                    NMVpnServiceState
+
  “state”                    NMVpnServiceState

The state of the plugin.

NMVpnPluginOld:state has been deprecated since version 1.2 and should not be used in newly-written code.

diff --git a/docs/libnm/html/NMVpnServicePlugin.html b/docs/libnm/html/NMVpnServicePlugin.html index cd038c2e..965727a3 100644 --- a/docs/libnm/html/NMVpnServicePlugin.html +++ b/docs/libnm/html/NMVpnServicePlugin.html @@ -150,7 +150,7 @@ Read / Write / Construct Only -NMVpnServiceState +NMVpnServiceState state Read / Write @@ -324,7 +324,7 @@ nm_vpn_service_plugin_set_login_banner

nm_vpn_service_plugin_failure ()

void
 nm_vpn_service_plugin_failure (NMVpnServicePlugin *plugin,
-                               NMVpnPluginFailure reason);
+ NMVpnPluginFailure reason);
@@ -515,7 +515,7 @@ to flags,

The “state” property

-
  “state”                    NMVpnServiceState
+
  “state”                    NMVpnServiceState

The state of the plugin.

Owner: NMVpnServicePlugin

Flags: Read / Write

diff --git a/docs/libnm/html/api-index-full.html b/docs/libnm/html/api-index-full.html index a1c2086d..7a730e98 100644 --- a/docs/libnm/html/api-index-full.html +++ b/docs/libnm/html/api-index-full.html @@ -3761,11 +3761,11 @@ NMUtilsPredicateStr, user_function in NMSettingOvs
-NMVpnConnectionState, enum in nm-vpn-dbus-interface +NMVpnConnectionState, enum in nm-vpn-dbus-interface
-NMVpnConnectionStateReason, enum in nm-vpn-dbus-interface +NMVpnConnectionStateReason, enum in nm-vpn-dbus-interface
@@ -3817,7 +3817,7 @@ NMVpnConnectionStateReason, enum in nm-vpn-dbus-interface
-NMVpnPluginFailure, enum in nm-vpn-dbus-interface +NMVpnPluginFailure, enum in nm-vpn-dbus-interface
@@ -3929,7 +3929,7 @@ NMVpnPluginFailure, enum in nm-vpn-dbus-interface
-NMVpnServiceState, enum in nm-vpn-dbus-interface +NMVpnServiceState, enum in nm-vpn-dbus-interface
diff --git a/docs/libnm/html/index.html b/docs/libnm/html/index.html index 73821288..f9ea840b 100644 --- a/docs/libnm/html/index.html +++ b/docs/libnm/html/index.html @@ -15,7 +15,7 @@

- for libnm 1.39.90 + for libnm 1.40.0 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/libnm/latest/. diff --git a/docs/libnm/html/libnm-nm-dbus-interface.html b/docs/libnm/html/libnm-nm-dbus-interface.html index 1585ca83..36eb69f8 100644 --- a/docs/libnm/html/libnm-nm-dbus-interface.html +++ b/docs/libnm/html/libnm-nm-dbus-interface.html @@ -4116,20 +4116,39 @@ is detected in the system.

  -

NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE

+

NM_MPTCP_FLAGS_ENABLED

-

MPTCP handling is enabled -or disabled depending on whether a /0 default route (either IPv4 or IPv6) is -configured in the main routing table.

+

MPTCP is enabled and endpoints will be configured. +This flag is implied if any of the other flags indicate that +MPTCP is enabled and therefore in most cases unnecessary. +Note that if "/proc/sys/net/mptcp/enabled" sysctl is disabled, MPTCP +handling is disabled despite this flag. This can be overruled with the +"also-without-sysctl" flag. +Note that by default interfaces that don't have a default route are +excluded from having MPTCP endpoints configured. This can be overruled +with the "also-without-default-route" and this affects endpoints +per address family.

  -

NM_MPTCP_FLAGS_ENABLED

+

NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL

-

MPTCP is enabled and endpoints will be configured. -This flag is implied if any of the other flags indicate that -MPTCP is enabled and therefore in most cases unnecessary.

+

even if MPTCP handling is enabled +via the "enabled" flag, it is ignored unless "/proc/sys/net/mptcp/enabled" +is on. With this flag, MPTCP endpoints will be configured regardless +of the sysctl setting.

+ +  + + +

NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE

+ +

even if MPTCP handling is enabled +via the "enabled" flag, it is ignored per-address family unless NetworkManager +configures a default route. With this flag, NetworkManager will also configure +MPTCP endpoints if there is no default route. This takes effect per-address +family.

  diff --git a/docs/libnm/html/libnm.devhelp2 b/docs/libnm/html/libnm.devhelp2 index b245c127..18e1826c 100644 --- a/docs/libnm/html/libnm.devhelp2 +++ b/docs/libnm/html/libnm.devhelp2 @@ -589,7 +589,7 @@ - + @@ -3529,8 +3529,9 @@ - + + diff --git a/docs/libnm/html/object-tree.html b/docs/libnm/html/object-tree.html index 04306fd0..ebc3205c 100644 --- a/docs/libnm/html/object-tree.html +++ b/docs/libnm/html/object-tree.html @@ -214,10 +214,10 @@ ├── NMTernary ├── NMUtilsSecurityType ├── NMVlanPriorityMap - ├── NMVpnConnectionState - ├── NMVpnConnectionStateReason - ├── NMVpnPluginFailure - ├── NMVpnServiceState + ├── NMVpnConnectionState + ├── NMVpnConnectionStateReason + ├── NMVpnPluginFailure + ├── NMVpnServiceState ├── NMWepKeyType ╰── NMWimaxNspNetworkType GBoxed diff --git a/docs/libnm/html/usage.html b/docs/libnm/html/usage.html index cc2062d0..5b5fb9ab 100644 --- a/docs/libnm/html/usage.html +++ b/docs/libnm/html/usage.html @@ -96,7 +96,7 @@ 

$ cc $(pkg-config --libs --cflags libnm) -o hello-nm hello-nm.c
   $ ./hello-nm
-  NetworkManager version: 1.39.90
+  NetworkManager version: 1.40.0
 
   $

diff --git a/docs/libnm/version.xml b/docs/libnm/version.xml index d3781d71..32b7211c 100644 --- a/docs/libnm/version.xml +++ b/docs/libnm/version.xml @@ -1 +1 @@ -1.39.90 +1.40.0 diff --git a/man/NetworkManager-dispatcher.8 b/man/NetworkManager-dispatcher.8 index 7aa79a6d..f196603c 100644 --- a/man/NetworkManager-dispatcher.8 +++ b/man/NetworkManager-dispatcher.8 @@ -2,9 +2,9 @@ .\" Title: NetworkManager-dispatcher .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Network management daemons -.\" Source: NetworkManager-dispatcher 1.39.90 +.\" Source: NetworkManager-dispatcher 1.40.0 .\" Language: English .\" .TH "NETWORKMANAGER\-DISPATCHER" "8" "" "NetworkManager\-dispatcher 1\&" "Network management daemons" diff --git a/man/NetworkManager-wait-online.service.8 b/man/NetworkManager-wait-online.service.8 index 902ff3e0..6d448854 100644 --- a/man/NetworkManager-wait-online.service.8 +++ b/man/NetworkManager-wait-online.service.8 @@ -2,9 +2,9 @@ .\" Title: NetworkManager-wait-online.service .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Network management daemons -.\" Source: NetworkManager-wait-online.service 1.39.90 +.\" Source: NetworkManager-wait-online.service 1.40.0 .\" Language: English .\" .TH "NETWORKMANAGER\-WAIT\-ONLINE\&" "8" "" "NetworkManager\-wait\-online\&" "Network management daemons" diff --git a/man/NetworkManager.8 b/man/NetworkManager.8 index 1e43a1a7..8570a569 100644 --- a/man/NetworkManager.8 +++ b/man/NetworkManager.8 @@ -2,12 +2,12 @@ .\" Title: NetworkManager .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Network management daemons -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NETWORKMANAGER" "8" "" "NetworkManager 1\&.39\&.90" "Network management daemons" +.TH "NETWORKMANAGER" "8" "" "NetworkManager 1\&.40\&.0" "Network management daemons" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/NetworkManager.conf.5 b/man/NetworkManager.conf.5 index c64c01a1..2adc374a 100644 --- a/man/NetworkManager.conf.5 +++ b/man/NetworkManager.conf.5 @@ -2,12 +2,12 @@ .\" Title: NetworkManager.conf .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Configuration -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NETWORKMANAGER\&.CONF" "5" "" "NetworkManager 1\&.39\&.90" "Configuration" +.TH "NETWORKMANAGER\&.CONF" "5" "" "NetworkManager 1\&.40\&.0" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -810,8 +810,9 @@ If unspecified, the ultimate default values depends on the DNS plugin\&. With sy .PP \fIconnection\&.mptcp\-flags\fR .RS 4 -If unspecified, the fallback is either 0 ("disabled") or 0x22 ("enabled\-on\-global\-iface,subflow"), depending on -/proc/sys/net/mptcp/enabled\&. +If unspecified, the fallback is 0x22 ("enabled,subflow")\&. Note that if sysctl +/proc/sys/net/mptcp/enabled +is disabled, NetworkManager will still not configure endpoints\&. .RE .PP \fIconnection\&.dns\-over\-tls\fR diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 6a0fd7b1..301172e4 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -868,7 +868,7 @@ ipv6.ip6-privacy=0 connection.mptcp-flags - If unspecified, the fallback is either 0 ("disabled") or 0x22 ("enabled-on-global-iface,subflow"), depending on /proc/sys/net/mptcp/enabled. + If unspecified, the fallback is 0x22 ("enabled,subflow"). Note that if sysctl /proc/sys/net/mptcp/enabled is disabled, NetworkManager will still not configure endpoints. connection.dns-over-tls diff --git a/man/nm-cloud-setup.8 b/man/nm-cloud-setup.8 index 60759986..0d5a6c3e 100644 --- a/man/nm-cloud-setup.8 +++ b/man/nm-cloud-setup.8 @@ -2,12 +2,12 @@ .\" Title: nm-cloud-setup .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Automatic Network Configuration in Cloud with NetworkManager -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-CLOUD\-SETUP" "8" "" "NetworkManager 1\&.39\&.90" "Automatic Network Configuratio" +.TH "NM\-CLOUD\-SETUP" "8" "" "NetworkManager 1\&.40\&.0" "Automatic Network Configuratio" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nm-initrd-generator.8 b/man/nm-initrd-generator.8 index 1afde3e1..7ec3ecf7 100644 --- a/man/nm-initrd-generator.8 +++ b/man/nm-initrd-generator.8 @@ -2,12 +2,12 @@ .\" Title: nm-initrd-generator .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: System Administration -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-INITRD\-GENERATOR" "8" "" "NetworkManager 1\&.39\&.90" "System Administration" +.TH "NM\-INITRD\-GENERATOR" "8" "" "NetworkManager 1\&.40\&.0" "System Administration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nm-online.1 b/man/nm-online.1 index 6087558a..cf0dc253 100644 --- a/man/nm-online.1 +++ b/man/nm-online.1 @@ -2,12 +2,12 @@ .\" Title: nm-online .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: General Commands Manual -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-ONLINE" "1" "" "NetworkManager 1\&.39\&.90" "General Commands Manual" +.TH "NM\-ONLINE" "1" "" "NetworkManager 1\&.40\&.0" "General Commands Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nm-openvswitch.7 b/man/nm-openvswitch.7 index b9d9aa3d..4d43136e 100644 --- a/man/nm-openvswitch.7 +++ b/man/nm-openvswitch.7 @@ -2,12 +2,12 @@ .\" Title: nm-openvswitch .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Open vSwitch support overview -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-OPENVSWITCH" "7" "" "NetworkManager 1\&.39\&.90" "Open vSwitch support overview" +.TH "NM\-OPENVSWITCH" "7" "" "NetworkManager 1\&.40\&.0" "Open vSwitch support overview" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nm-settings-dbus.5 b/man/nm-settings-dbus.5 index df827802..38b29ab1 100644 --- a/man/nm-settings-dbus.5 +++ b/man/nm-settings-dbus.5 @@ -2,12 +2,12 @@ .\" Title: nm-settings-dbus .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Configuration -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-SETTINGS\-DBUS" "5" "" "NetworkManager 1\&.39\&.90" "Configuration" +.TH "NM\-SETTINGS\-DBUS" "5" "" "NetworkManager 1\&.40\&.0" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -267,13 +267,15 @@ Whether to configure MPTCP endpoints and the address flags\&. If MPTCP is enable If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered\&. - The flag "enabled\-on\-global\-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table\&. This choice is per\-address family, for example if there is an IPv4 default route 0\&.0\&.0\&.0/0, IPv4 endpoints are configured\&. + The "enabled" (0x2) flag means that MPTCP handling is enabled\&. This flag can also be implied from the presence of other flags\&. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled\&. This flag can also be implied from the presence of other flags\&. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on\&. NetworkManager does not change the sysctl and this is up to the administrator or distribution\&. To configure endpoints even if the sysctl is disabled, "also\-without\-sysctl" (0x4) flag can be used\&. In that case, NetworkManager doesn\*(Aqt look at the sysctl and configures endpoints regardless\&. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80)\&. See ip\-mptcp(8) manual for additional information about the flags\&. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0\&.0\&.0\&.0/0 or ::/0) in the main routing table\&. The flag "also\-without\-default\-route" (0x8) can override that\&. - If the flags are zero, the global connection default from NetworkManager\&.conf is honored\&. If still unspecified, the fallback is either "disabled" or "enabled\-on\-global\-iface,subflow" depending on "/proc/sys/net/mptcp/enabled"\&. + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80)\&. See ip\-mptcp(8) manual for additional information about the flags\&. + + If the flags are zero (0x0), the global connection default from NetworkManager\&.conf is honored\&. If still unspecified, the fallback is "enabled,subflow"\&. Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl\&. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled"\&. That is a host configuration which the admin can change via sysctl and ip\-mptcp\&. @@ -2268,9 +2270,9 @@ T}:T{ T}:T{ The gateway associated with this configuration\&. This is only meaningful if "addresses" is also set\&. - The gateway\*(Aqs main purpose is to control the next hop of the standard default route on the device\&. Hence, the gateway property conflicts with "never\-default" and will be automatically dropped if the IP configuration is set to never\-default\&. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop\&. This is ignored if "never\-default" is set\&. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length\&. - As an alternative to set the gateway, configure a static default route with /0 as prefix length\&. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case\&. See "ip4\-auto\-default\-route"\&. T} T{ ignore\-auto\-dns @@ -2643,9 +2645,9 @@ T}:T{ T}:T{ The gateway associated with this configuration\&. This is only meaningful if "addresses" is also set\&. - The gateway\*(Aqs main purpose is to control the next hop of the standard default route on the device\&. Hence, the gateway property conflicts with "never\-default" and will be automatically dropped if the IP configuration is set to never\-default\&. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop\&. This is ignored if "never\-default" is set\&. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length\&. - As an alternative to set the gateway, configure a static default route with /0 as prefix length\&. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case\&. See "ip4\-auto\-default\-route"\&. T} T{ ignore\-auto\-dns diff --git a/man/nm-settings-dbus.xml b/man/nm-settings-dbus.xml index 72b8969d..801989ab 100644 --- a/man/nm-settings-dbus.xml +++ b/man/nm-settings-dbus.xml @@ -1,6 +1,6 @@ -nm-settings-dbusNetworkManager developersnm-settings-dbus5NetworkManagerConfiguration1.39.90nm-settings-dbusDescription of settings and properties of NetworkManager connection profiles on the D-Bus APIDescription +nm-settings-dbusNetworkManager developersnm-settings-dbus5NetworkManagerConfiguration1.40.0nm-settings-dbusDescription of settings and properties of NetworkManager connection profiles on the D-Bus APIDescription NetworkManager is based on a concept of connection profiles, sometimes referred to as connections only. These connection profiles contain a network configuration. When NetworkManager activates a connection profile on a network device the configuration will @@ -64,13 +64,15 @@ If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. + The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + + If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. @@ -194,9 +196,9 @@ When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).gatewaystring The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length.ignore-auto-dnsbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.ignore-auto-routesbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.link-localint320 Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".ignore-auto-dnsbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.ignore-auto-routesbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.link-localint320 Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". @@ -278,9 +280,9 @@ When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).gatewaystring The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length.ignore-auto-dnsbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.ignore-auto-routesbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.ip6-privacyNMSettingIP6ConfigPrivacy (int32) Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".ignore-auto-dnsbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.ignore-auto-routesbooleanFALSE When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.ip6-privacyNMSettingIP6ConfigPrivacy (int32) Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". diff --git a/man/nm-settings-docs-dbus.xml b/man/nm-settings-docs-dbus.xml index 8de0b6cf..c474005b 100644 --- a/man/nm-settings-docs-dbus.xml +++ b/man/nm-settings-docs-dbus.xml @@ -26,17 +26,19 @@ This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately. Whether the connection is metered. - When updating this property on a currently activated connection, the change takes effect immediately. Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. + When updating this property on a currently activated connection, the change takes effect immediately. Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. + The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + + If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. @@ -158,11 +160,11 @@ When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. - When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. The gateway associated with this configuration. This is only meaningful if "addresses" is also set. + When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". @@ -242,11 +244,11 @@ When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. - When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. The gateway associated with this configuration. This is only meaningful if "addresses" is also set. + When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". diff --git a/man/nm-settings-docs-nmcli.xml b/man/nm-settings-docs-nmcli.xml index 6822fdc9..41ca76a5 100644 --- a/man/nm-settings-docs-nmcli.xml +++ b/man/nm-settings-docs-nmcli.xml @@ -1,4 +1,4 @@ - The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication.The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication. Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined. Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined. Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times. The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen. The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again. Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0. Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping. A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G". The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface. Whether LLDP is enabled for the connection.Whether LLDP is enabled for the connection. Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Interface name of the master device or UUID of the master connection.Interface name of the master device or UUID of the master connection. Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately. Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none". Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect. An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8. FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified. List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported. Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave. This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection. The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved). Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc). A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-"). Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time. Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time. The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately. If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created. List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed. Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS. A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds. Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory. The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "ca-cert-password" property.Flags indicating how to handle the "ca-cert-password" property. UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored. Contains the client certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.Contains the client certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "client-cert-password" property.Flags indicating how to handle the "client-cert-password" property. Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list. Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list. The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations. Identity string for EAP authentication methods. Often the user's user or login name.Identity string for EAP authentication methods. Often the user's user or login name. Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication. UTF-8 encoded file path containing PAC for EAP-FAST.UTF-8 encoded file path containing PAC for EAP-FAST. UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred. Flags indicating how to handle the "password-raw" property.Flags indicating how to handle the "password-raw" property. Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details. Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details. Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details. Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version. List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed. Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified. Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory. The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "phase2-ca-cert-password" property.Flags indicating how to handle the "phase2-ca-cert-password" property. UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored. Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "phase2-client-cert-password" property.Flags indicating how to handle the "phase2-client-cert-password" property. Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list. Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list. Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key. Flags indicating how to handle the "phase2-private-key-password" property.Flags indicating how to handle the "phase2-private-key-password" property. Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match. PIN used for EAP authentication methods.PIN used for EAP authentication methods. Flags indicating how to handle the "pin" property.Flags indicating how to handle the "pin" property. Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data. The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key. Flags indicating how to handle the "private-key-password" property.Flags indicating how to handle the "private-key-password" property. Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match. When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant). Encapsulation of ADSL connection. Can be "vcmux" or "llc".Encapsulation of ADSL connection. Can be "vcmux" or "llc". Password used to authenticate with the ADSL service.Password used to authenticate with the ADSL service. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm". Username used to authenticate with the ADSL service.Username used to authenticate with the ADSL service. VCI of ADSL connectionVCI of ADSL connection VPI of ADSL connectionVPI of ADSL connection The Bluetooth address of the device.The Bluetooth address of the device. Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile. Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). The Ethernet MAC address aging time, in seconds.The Ethernet MAC address aging time, in seconds. The Spanning Tree Protocol (STP) forwarding delay, in seconds.The Spanning Tree Protocol (STP) forwarding delay, in seconds. If specified, The MAC address of the multicast group this bridge uses for STP. The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.If specified, The MAC address of the multicast group this bridge uses for STP. The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00. A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP. The Spanning Tree Protocol (STP) hello time, in seconds.The Spanning Tree Protocol (STP) hello time, in seconds. If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1 The Spanning Tree Protocol (STP) maximum message age, in seconds.The Spanning Tree Protocol (STP) maximum message age, in seconds. Set maximum size of multicast hash table (value must be a power of 2).Set maximum size of multicast hash table (value must be a power of 2). Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received. Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received. Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received. Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled. If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries. Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase. Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge. If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used. Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1). Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved. Set the number of IGMP queries to send during startup phase.Set the number of IGMP queries to send during startup phase. Sets the time (in deciseconds) between queries sent out at startup to determine membership information.Sets the time (in deciseconds) between queries sent out at startup to determine membership information. Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge. Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.Controls whether Spanning Tree Protocol (STP) is enabled for this bridge. The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames. Control whether VLAN filtering is enabled on the bridge.Control whether VLAN filtering is enabled on the bridge. If specified, the protocol used for VLAN filtering. Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.If specified, the protocol used for VLAN filtering. Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'. Controls whether per-VLAN stats accounting is enabled.Controls whether per-VLAN stats accounting is enabled. Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash. Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on. The Spanning Tree Protocol (STP) port cost for destinations via this port.The Spanning Tree Protocol (STP) port cost for destinations via this port. The Spanning Tree Protocol (STP) priority of this bridge port.The Spanning Tree Protocol (STP) priority of this bridge port. Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash. If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames. The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required. The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here. Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric". The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag. Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag. Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag. An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents. An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause. Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents. Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group. An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group. An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.Whether to automatically negotiate on pause frame of flow control mechanism defined by IEEE 802.3x standard.Whether RX pause should be enabled. Only valid when automatic negotiation is disabledWhether TX pause should be enabled. Only valid when automatic negotiation is disabled The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9. When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database. The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device. When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made. If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames. The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible. Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1 The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device. Flags indicating how to handle the "pin" property.Flags indicating how to handle the "pin" property. The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier. A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator. The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here. If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing). If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames. The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key. The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address". The IP-over-InfiniBand transport mode. Either "datagram" or "connected".The IP-over-InfiniBand transport mode. Either "datagram" or "connected". Array of IP addresses.A list of IPv4 addresses and their prefix length. Multiple addresses can be separated by comma. For example "192.168.1.5/24, 10.1.0.5/24". The addresses are listed in decreasing priority, meaning the first address will be the primary address. Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4. A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin. If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time. If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time. Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests. A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address. Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). This property is currently not implemented for DHCPv6.Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). This property is currently not implemented for DHCPv6. If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent. A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity. The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server. Since 1.28The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server. Since 1.28 Array of IP addresses of DNS servers.Array of IP addresses of DNS servers. Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added. DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured. List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully. IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared. If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager. The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero). The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric. Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager. + The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication.The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection. Currently, this only applies to 802-1x authentication. Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined. Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection. Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile. Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles. If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined. Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times. The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen. The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again. Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0. Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic. The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting. This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping. A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G". The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface. Whether LLDP is enabled for the connection.Whether LLDP is enabled for the connection. Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes"). This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Interface name of the master device or UUID of the master connection.Interface name of the master device or UUID of the master connection. Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately. Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none". Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect. An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8. FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified. List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported. Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave. This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid]. Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity. The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates. If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection. The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved). Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc). A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-"). Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time. Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed. The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time. The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately. If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created. List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed. Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS. A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds. Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory. The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "ca-cert-password" property.Flags indicating how to handle the "ca-cert-password" property. UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored. Contains the client certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.Contains the client certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "client-cert-password" property.Flags indicating how to handle the "client-cert-password" property. Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list. Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list. The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations. Identity string for EAP authentication methods. Often the user's user or login name.Identity string for EAP authentication methods. Often the user's user or login name. Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication. UTF-8 encoded file path containing PAC for EAP-FAST.UTF-8 encoded file path containing PAC for EAP-FAST. UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred. Flags indicating how to handle the "password-raw" property.Flags indicating how to handle the "password-raw" property. Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details. Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details. Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details. Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version. List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed. Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified. Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory. The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "phase2-ca-cert-password" property.Flags indicating how to handle the "phase2-ca-cert-password" property. UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored. Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login. Flags indicating how to handle the "phase2-client-cert-password" property.Flags indicating how to handle the "phase2-client-cert-password" property. Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list. Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list. Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key. Flags indicating how to handle the "phase2-private-key-password" property.Flags indicating how to handle the "phase2-private-key-password" property. Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match. PIN used for EAP authentication methods.PIN used for EAP authentication methods. Flags indicating how to handle the "pin" property.Flags indicating how to handle the "pin" property. Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data. The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key. Flags indicating how to handle the "private-key-password" property.Flags indicating how to handle the "private-key-password" property. Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match. When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant). Encapsulation of ADSL connection. Can be "vcmux" or "llc".Encapsulation of ADSL connection. Can be "vcmux" or "llc". Password used to authenticate with the ADSL service.Password used to authenticate with the ADSL service. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm". Username used to authenticate with the ADSL service.Username used to authenticate with the ADSL service. VCI of ADSL connectionVCI of ADSL connection VPI of ADSL connectionVPI of ADSL connection The Bluetooth address of the device.The Bluetooth address of the device. Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile. Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]). The Ethernet MAC address aging time, in seconds.The Ethernet MAC address aging time, in seconds. The Spanning Tree Protocol (STP) forwarding delay, in seconds.The Spanning Tree Protocol (STP) forwarding delay, in seconds. If specified, The MAC address of the multicast group this bridge uses for STP. The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.If specified, The MAC address of the multicast group this bridge uses for STP. The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00. A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP. The Spanning Tree Protocol (STP) hello time, in seconds.The Spanning Tree Protocol (STP) hello time, in seconds. If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set. If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1 The Spanning Tree Protocol (STP) maximum message age, in seconds.The Spanning Tree Protocol (STP) maximum message age, in seconds. Set maximum size of multicast hash table (value must be a power of 2).Set maximum size of multicast hash table (value must be a power of 2). Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received. Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received. Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received. Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled. If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries. Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase. Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge. If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used. Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work. Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1). Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved. Set the number of IGMP queries to send during startup phase.Set the number of IGMP queries to send during startup phase. Sets the time (in deciseconds) between queries sent out at startup to determine membership information.Sets the time (in deciseconds) between queries sent out at startup to determine membership information. Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge. Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.Controls whether Spanning Tree Protocol (STP) is enabled for this bridge. The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames. Control whether VLAN filtering is enabled on the bridge.Control whether VLAN filtering is enabled on the bridge. If specified, the protocol used for VLAN filtering. Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.If specified, the protocol used for VLAN filtering. Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'. Controls whether per-VLAN stats accounting is enabled.Controls whether per-VLAN stats accounting is enabled. Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash. Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on. The Spanning Tree Protocol (STP) port cost for destinations via this port.The Spanning Tree Protocol (STP) port cost for destinations via this port. The Spanning Tree Protocol (STP) priority of this bridge port.The Spanning Tree Protocol (STP) priority of this bridge port. Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property. In nmcli the VLAN list can be specified with the following syntax: $vid [pvid] [untagged] [, $vid [pvid] [untagged]]... where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash. If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames. The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required. The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here. Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".The FCoE controller mode; either "fabric" or "vn2vn". Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric". The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag. Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag. Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag. An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents. An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause. Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents. Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4). An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group. An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group. An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.Whether to automatically negotiate on pause frame of flow control mechanism defined by IEEE 802.3x standard.Whether RX pause should be enabled. Only valid when automatic negotiation is disabledWhether TX pause should be enabled. Only valid when automatic negotiation is disabled The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9. When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database. The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device. When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made. If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames. The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible. Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1 The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here. Flags indicating how to handle the "password" property.Flags indicating how to handle the "password" property. If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device. Flags indicating how to handle the "pin" property.Flags indicating how to handle the "pin" property. The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier. A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator. The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here. If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing). If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames. The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key. The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address". The IP-over-InfiniBand transport mode. Either "datagram" or "connected".The IP-over-InfiniBand transport mode. Either "datagram" or "connected". Array of IP addresses.A list of IPv4 addresses and their prefix length. Multiple addresses can be separated by comma. For example "192.168.1.5/24, 10.1.0.5/24". The addresses are listed in decreasing priority, meaning the first address will be the primary address. Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4. A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0. The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links. The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset. The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id. The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key. If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin. If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time. If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time. Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests. A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address. Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). This property is currently not implemented for DHCPv6.Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers. For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24"). This property is currently not implemented for DHCPv6. If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent. A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity. The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server. Since 1.28The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server. Since 1.28 Array of IP addresses of DNS servers.Array of IP addresses of DNS servers. Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added. DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured. List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully. IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared. If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager. The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero). The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric. Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager. A list of IPv4 destination addresses, prefix length, optional IPv4 next hop addresses, optional route metric, optional attribute. The valid syntax is: @@ -84,7 +84,7 @@ fixed priority. Example: priority 5 from 192.167.4.0/24 table 45 -A comma separated list of routing rules for policy routing. Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively. For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions. Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively. For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions. Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option. Array of IP addresses.A list of IPv6 addresses and their prefix length. Multiple addresses can be separated by comma. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64". The addresses are listed in decreasing priority, meaning the first address will be the primary address. This can make a difference with IPv6 source address selection (RFC 6724, section 5). A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed. If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time. Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests. A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address. If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent. A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity. Array of IP addresses of DNS servers.Array of IP addresses of DNS servers. Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added. DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured. List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully. IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared. Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect. If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager. A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. Set to 2147483647 (MAXINT32) for infinity.A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. Set to 2147483647 (MAXINT32) for infinity. The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero). The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric. Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager. +A comma separated list of routing rules for policy routing. Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively. For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions. Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option.Configure method for creating the address for use with RFC4862 IPv6 Stateless Address Autoconfiguration. The permitted values are: NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_EUI64 (0), NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_STABLE_PRIVACY (1). NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT_OR_EUI64 (2) or NM_SETTING_IP6_CONFIG_ADDR_GEN_MODE_DEFAULT (3). If the property is set to EUI64, the addresses will be generated using the interface tokens derived from hardware address. This makes the host part of the address to stay constant, making it possible to track host's presence when it changes networks. The address changes when the interface hardware is replaced. The value of stable-privacy enables use of cryptographically secure hash of a secret host-specific key along with the connection's stable-id and the network address as specified by RFC7217. This makes it impossible to use the address track host's presence, and makes the address stable when the network interface hardware is replaced. The special values "default" and "default-or-eui64" will fallback to the global connection default in as documented in NetworkManager.conf(5) manual. If the global default is not specified, the fallback value is "stable-privacy" or "eui64", respectively. For libnm, the property defaults to "default" since 1.40. Previously it defaulted to "stable-privacy". On D-Bus, the absence of an addr-gen-mode setting equals "default". For keyfile plugin, the absence of the setting on disk means "default-or-eui64" so that the property doesn't change on upgrade from older versions. Note that this setting is distinct from the Privacy Extensions as configured by "ip6-privacy" property and it does not affect the temporary addresses configured with this option. Array of IP addresses.A list of IPv6 addresses and their prefix length. Multiple addresses can be separated by comma. For example "2001:db8:85a3::8a2e:370:7334/64, 2001:db8:85a3::5/64". The addresses are listed in decreasing priority, meaning the first address will be the primary address. This can make a difference with IPv6 source address selection (RFC 6724, section 5). A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed.A string containing the DHCPv6 Unique Identifier (DUID) used by the dhcp client to identify itself to DHCPv6 servers (RFC 3315). The DUID is carried in the Client Identifier option. If the property is a hex string ('aa:bb:cc') it is interpreted as a binary DUID and filled as an opaque value in the Client Identifier option. The special value "lease" will retrieve the DUID previously used from the lease file belonging to the connection. If no DUID is found and "dhclient" is the configured dhcp client, the DUID is searched in the system-wide dhclient lease file. If still no DUID is found, or another dhcp client is used, a global and permanent DUID-UUID (RFC 6355) will be generated based on the machine-id. The special values "llt" and "ll" will generate a DUID of type LLT or LL (see RFC 3315) based on the current MAC address of the device. In order to try providing a stable DUID-LLT, the time field will contain a constant timestamp that is used globally (for all profiles) and persisted to disk. The special values "stable-llt", "stable-ll" and "stable-uuid" will generate a DUID of the corresponding type, derived from the connection's stable-id and a per-host unique key. You may want to include the "${DEVICE}" or "${MAC}" specifier in the stable-id, in case this profile gets activated on multiple devices. So, the link-layer address of "stable-ll" and "stable-llt" will be a generated address derived from the stable id. The DUID-LLT time value in the "stable-llt" option will be picked among a static timespan of three years (the upper bound of the interval is the same constant timestamp used in "llt"). When the property is unset, the global value provided for "ipv6.dhcp-duid" is used. If no global value is provided, the default "lease" value is assumed. If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time. Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.Flags for the DHCP hostname and FQDN. Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests. A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address. If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent. A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity.A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds). Set to 2147483647 (MAXINT32) for infinity. Array of IP addresses of DNS servers.Array of IP addresses of DNS servers. Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc". The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added. DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured. List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses.Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully. IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.IP configuration method. NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values. In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior. For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty. For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared. Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect.Maximum transmission unit size, in bytes. If zero (the default), the MTU is set automatically from router advertisements or is left equal to the link-layer MTU. If greater than the link-layer MTU, or greater than zero but less than the minimum IPv6 MTU of 1280, this value has no effect. If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager. A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. Set to 2147483647 (MAXINT32) for infinity.A timeout for waiting Router Advertisements in seconds. If zero (the default), a globally configured default is used. If still unspecified, the timeout depends on the sysctl settings of the device. Set to 2147483647 (MAXINT32) for infinity. The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds. This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active. Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout. A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero). The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric. Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.Enable policy routing (source routing) and set the routing table used when adding routes. This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table. If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection. Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager. A list of IPv6 destination addresses, prefix length, optional IPv6 next hop addresses, optional route metric, optional attribute. The valid syntax is: diff --git a/man/nm-settings-ifcfg-rh.5 b/man/nm-settings-ifcfg-rh.5 index f88f0ccb..0d18d751 100644 --- a/man/nm-settings-ifcfg-rh.5 +++ b/man/nm-settings-ifcfg-rh.5 @@ -2,12 +2,12 @@ .\" Title: nm-settings-ifcfg-rh .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Configuration -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-SETTINGS\-IFCFG\-RH" "5" "" "NetworkManager 1\&.39\&.90" "Configuration" +.TH "NM\-SETTINGS\-IFCFG\-RH" "5" "" "NetworkManager 1\&.40\&.0" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nm-settings-ifcfg-rh.xml b/man/nm-settings-ifcfg-rh.xml index cc225bb6..e90f042b 100644 --- a/man/nm-settings-ifcfg-rh.xml +++ b/man/nm-settings-ifcfg-rh.xml @@ -1,6 +1,6 @@ -nm-settings-ifcfg-rhNetworkManager developersnm-settings-ifcfg-rh5NetworkManagerConfiguration1.39.90nm-settings-ifcfg-rhDescription of ifcfg-rh settings pluginDescription +nm-settings-ifcfg-rhNetworkManager developersnm-settings-ifcfg-rh5NetworkManagerConfiguration1.40.0nm-settings-ifcfg-rhDescription of ifcfg-rh settings pluginDescription NetworkManager is based on the concept of connection profiles that contain network configuration (see nm-settings5 for details). The profiles can be stored in various formats. NetworkManager uses plugins for reading and writing diff --git a/man/nm-settings-keyfile.5 b/man/nm-settings-keyfile.5 index 8d33a3b9..d606f22b 100644 --- a/man/nm-settings-keyfile.5 +++ b/man/nm-settings-keyfile.5 @@ -2,12 +2,12 @@ .\" Title: nm-settings-keyfile .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Configuration -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-SETTINGS\-KEYFILE" "5" "" "NetworkManager 1\&.39\&.90" "Configuration" +.TH "NM\-SETTINGS\-KEYFILE" "5" "" "NetworkManager 1\&.40\&.0" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nm-settings-keyfile.xml b/man/nm-settings-keyfile.xml index c3f76982..9805649e 100644 --- a/man/nm-settings-keyfile.xml +++ b/man/nm-settings-keyfile.xml @@ -1,6 +1,6 @@ -nm-settings-keyfileNetworkManager developersnm-settings-keyfile5NetworkManagerConfiguration1.39.90nm-settings-keyfileDescription of keyfile settings pluginDescription +nm-settings-keyfileNetworkManager developersnm-settings-keyfile5NetworkManagerConfiguration1.40.0nm-settings-keyfileDescription of keyfile settings pluginDescription NetworkManager is based on the concept of connection profiles that contain network configuration (see nm-settings5 for details). The profiles can be stored in various formats. NetworkManager uses plugins for reading and writing diff --git a/man/nm-settings-nmcli.5 b/man/nm-settings-nmcli.5 index 31109f3a..be46876f 100644 --- a/man/nm-settings-nmcli.5 +++ b/man/nm-settings-nmcli.5 @@ -2,12 +2,12 @@ .\" Title: nm-settings-nmcli .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Configuration -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.39\&.90" "Configuration" +.TH "NM\-SETTINGS\-NMCLI" "5" "" "NetworkManager 1\&.40\&.0" "Configuration" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -208,13 +208,15 @@ Whether to configure MPTCP endpoints and the address flags\&. If MPTCP is enable .sp If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered\&. .sp -The flag "enabled\-on\-global\-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table\&. This choice is per\-address family, for example if there is an IPv4 default route 0\&.0\&.0\&.0/0, IPv4 endpoints are configured\&. +The "enabled" (0x2) flag means that MPTCP handling is enabled\&. This flag can also be implied from the presence of other flags\&. .sp -The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled\&. This flag can also be implied from the presence of other flags\&. +Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on\&. NetworkManager does not change the sysctl and this is up to the administrator or distribution\&. To configure endpoints even if the sysctl is disabled, "also\-without\-sysctl" (0x4) flag can be used\&. In that case, NetworkManager doesn\*(Aqt look at the sysctl and configures endpoints regardless\&. .sp -If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80)\&. See ip\-mptcp(8) manual for additional information about the flags\&. +Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0\&.0\&.0\&.0/0 or ::/0) in the main routing table\&. The flag "also\-without\-default\-route" (0x8) can override that\&. .sp -If the flags are zero, the global connection default from NetworkManager\&.conf is honored\&. If still unspecified, the fallback is either "disabled" or "enabled\-on\-global\-iface,subflow" depending on "/proc/sys/net/mptcp/enabled"\&. +When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80)\&. See ip\-mptcp(8) manual for additional information about the flags\&. +.sp +If the flags are zero (0x0), the global connection default from NetworkManager\&.conf is honored\&. If still unspecified, the fallback is "enabled,subflow"\&. Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl\&. .sp NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled"\&. That is a host configuration which the admin can change via sysctl and ip\-mptcp\&. .sp @@ -1916,9 +1918,9 @@ Alias: gw4 .sp The gateway associated with this configuration\&. This is only meaningful if "addresses" is also set\&. .sp -The gateway\*(Aqs main purpose is to control the next hop of the standard default route on the device\&. Hence, the gateway property conflicts with "never\-default" and will be automatically dropped if the IP configuration is set to never\-default\&. +Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop\&. This is ignored if "never\-default" is set\&. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length\&. .sp -As an alternative to set the gateway, configure a static default route with /0 as prefix length\&. +Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case\&. See "ip4\-auto\-default\-route"\&. .sp Format: string .RE @@ -2427,9 +2429,9 @@ Alias: gw6 .sp The gateway associated with this configuration\&. This is only meaningful if "addresses" is also set\&. .sp -The gateway\*(Aqs main purpose is to control the next hop of the standard default route on the device\&. Hence, the gateway property conflicts with "never\-default" and will be automatically dropped if the IP configuration is set to never\-default\&. +Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop\&. This is ignored if "never\-default" is set\&. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length\&. .sp -As an alternative to set the gateway, configure a static default route with /0 as prefix length\&. +Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case\&. See "ip4\-auto\-default\-route"\&. .sp Format: string .RE diff --git a/man/nm-settings-nmcli.xml b/man/nm-settings-nmcli.xml index 5ed71123..4af75f0b 100644 --- a/man/nm-settings-nmcli.xml +++ b/man/nm-settings-nmcli.xml @@ -1,6 +1,6 @@ -nm-settings-nmcliNetworkManager developersnm-settings-nmcli5NetworkManagerConfiguration1.39.90nm-settings-nmcliDescription of settings and properties of NetworkManager connection profiles for nmcliDescription +nm-settings-nmcliNetworkManager developersnm-settings-nmcli5NetworkManagerConfiguration1.40.0nm-settings-nmcliDescription of settings and properties of NetworkManager connection profiles for nmcliDescription NetworkManager is based on a concept of connection profiles, sometimes referred to as connections only. These connection profiles contain a network configuration. When NetworkManager activates a connection profile on a network device the configuration will @@ -51,7 +51,7 @@ Alias: master Interface name of the master device or UUID of the master connection. Format: string Whether mDNS is enabled for the connection. The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Format: int32 Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately. - Format: NMMetered (int32) Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). + Format: NMMetered (int32) Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Format: uint32 If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none". Format: string Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect. Format: int32 An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8. @@ -267,7 +267,7 @@ Format: array of string DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured. Format: int32 List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). Format: array of string - Alias: gw4 The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. + Alias: gw4 The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". Format: string When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. Format: boolean When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Format: boolean Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 @@ -376,7 +376,7 @@ Example: priority 5 from 192.167.4.0/24 table 45 Format: array of string DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured. Format: int32 List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). Format: array of string - Alias: gw6 The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. + Alias: gw6 The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". Format: string When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. Format: boolean When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Format: boolean Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. diff --git a/man/nmcli-examples.7 b/man/nmcli-examples.7 index bb86c9cb..85808e98 100644 --- a/man/nmcli-examples.7 +++ b/man/nmcli-examples.7 @@ -2,12 +2,12 @@ .\" Title: nmcli-examples .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: Examples -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NMCLI\-EXAMPLES" "7" "" "NetworkManager 1\&.39\&.90" "Examples" +.TH "NMCLI\-EXAMPLES" "7" "" "NetworkManager 1\&.40\&.0" "Examples" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nmcli.1 b/man/nmcli.1 index b94576af..4a4661c8 100644 --- a/man/nmcli.1 +++ b/man/nmcli.1 @@ -2,12 +2,12 @@ .\" Title: nmcli .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: General Commands Manual -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NMCLI" "1" "" "NetworkManager 1\&.39\&.90" "General Commands Manual" +.TH "NMCLI" "1" "" "NetworkManager 1\&.40\&.0" "General Commands Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/man/nmtui.1 b/man/nmtui.1 index 558854f1..96bb5ec4 100644 --- a/man/nmtui.1 +++ b/man/nmtui.1 @@ -2,12 +2,12 @@ .\" Title: nmtui .\" Author: .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 08/15/2022 +.\" Date: 08/26/2022 .\" Manual: General Commands Manual -.\" Source: NetworkManager 1.39.90 +.\" Source: NetworkManager 1.40.0 .\" Language: English .\" -.TH "NMTUI" "1" "" "NetworkManager 1\&.39\&.90" "General Commands Manual" +.TH "NMTUI" "1" "" "NetworkManager 1\&.40\&.0" "General Commands Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff --git a/meson.build b/meson.build index 300e7131..996617f4 100644 --- a/meson.build +++ b/meson.build @@ -6,7 +6,7 @@ project( # - add corresponding NM_VERSION_x_y_z macros in # "src/libnm-core-public/nm-version-macros.h.in" # - update number in configure.ac - version: '1.39.90', + version: '1.40.0', license: 'GPL2+', default_options: [ 'buildtype=debugoptimized', diff --git a/po/NetworkManager.pot b/po/NetworkManager.pot index faa06074..bb133641 100644 --- a/po/NetworkManager.pot +++ b/po/NetworkManager.pot @@ -6,10 +6,10 @@ #, fuzzy msgid "" msgstr "" -"Project-Id-Version: NetworkManager 1.39.90\n" +"Project-Id-Version: NetworkManager 1.40.0\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1134,7 +1134,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1475,7 +1475,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1756,7 +1756,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1765,54 +1765,50 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5672,25 +5668,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6924,11 +6924,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/as.po b/po/as.po index db92a5fa..5ed0f2c3 100644 --- a/po/as.po +++ b/po/as.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:06-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Assamese \n" @@ -1237,7 +1237,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1587,7 +1587,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1875,7 +1875,7 @@ msgstr "মান '%s' এটা বৈধ UUID নহয়" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "মান '%s' এটা বৈধ UUID নহয়" @@ -1884,56 +1884,52 @@ msgstr "মান '%s' এটা বৈধ UUID নহয়" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' বৈধ নহয়; [%s] অথবা [%s] ব্যৱহাৰ কৰক" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "সূচী '%s' বৈধ নহয়" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "অবৈধ IPv4 পথ '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "বৈশিষ্ট্য ধৰণ '%s' লৈ সংহতি কৰিব লাগিব" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type '%s' ৰ সংযোগত এটা '%s' সংহতিৰ প্ৰয়োজন" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' অথবা '%s' সংহতিৰ প্ৰয়োজন" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6098,25 +6094,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7350,11 +7350,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/be@latin.po b/po/be@latin.po index f4a1f2e5..15151904 100644 --- a/po/be@latin.po +++ b/po/be@latin.po @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2008-03-29 21:43+0200\n" "Last-Translator: Ihar Hrachyshka \n" "Language-Team: Belarusian Latin \n" @@ -1134,7 +1134,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1475,7 +1475,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1756,7 +1756,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1765,54 +1765,50 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5674,25 +5670,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6926,11 +6926,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/bg.po b/po/bg.po index 7d5a1184..71accb23 100644 --- a/po/bg.po +++ b/po/bg.po @@ -11,7 +11,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:07-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Bulgarian \n" @@ -1228,7 +1228,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1574,7 +1574,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1860,7 +1860,7 @@ msgstr "Ограничението на времето „%s“ не е прав #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Ограничението на времето „%s“ не е правилно." @@ -1869,56 +1869,52 @@ msgstr "Ограничението на времето „%s“ не е прав msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Ограничението на времето „%s“ не е правилно." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Грешка: „%s“ не е правилна команда за „nm“." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "грешно поле „%s“" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5942,25 +5938,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7194,11 +7194,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/bn_IN.po b/po/bn_IN.po index 1b9956d5..f0571150 100644 --- a/po/bn_IN.po +++ b/po/bn_IN.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:09-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Bengali (India) \n" @@ -1256,7 +1256,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1606,7 +1606,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1898,7 +1898,7 @@ msgstr "মান '%s' একটি বৈধ UUID নয়" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "মান '%s' একটি বৈধ UUID নয়" @@ -1907,56 +1907,52 @@ msgstr "মান '%s' একটি বৈধ UUID নয়" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' বৈধ নয়; ব্যবহার করুন [%s] বা [%s]" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "সূচি '%s' বৈধ নয়" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "অবৈধ IPv4 রাউট '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "বিশিষ্টতা ধরন '%s' এ সেট করা উচিত" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "স্লেভ-ধরন '%s' -এর সংযোগে একটি '%s' সেটিং -এর প্রয়োজন" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' বা '%s' সেটিং এর প্রয়োজন" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6128,25 +6124,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7380,11 +7380,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/bs.po b/po/bs.po index e06ec926..306fd6da 100644 --- a/po/bs.po +++ b/po/bs.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:12-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Bosnian \n" @@ -1170,7 +1170,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1511,7 +1511,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1792,7 +1792,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1801,54 +1801,50 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5734,25 +5730,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6986,11 +6986,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ca.po b/po/ca.po index a82b61db..389cba24 100644 --- a/po/ca.po +++ b/po/ca.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:12-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Catalan \n" @@ -1242,7 +1242,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1590,7 +1590,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1881,7 +1881,7 @@ msgstr "el valor %d mesurat no és vàlid" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "el valor %d mesurat no és vàlid" @@ -1890,45 +1890,41 @@ msgstr "el valor %d mesurat no és vàlid" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "Les etiquetes «%u» no són vàlides; useu una combinació de %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "file:// URI no és UTF-8 vàlida" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ruta no vàlida: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "el tipus de propietat s'hauria d'establir a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "el tipus d'esclava «%s» requereix un paràmetre «%s» a la connexió" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1937,14 +1933,14 @@ msgstr "" "Detecta una connexió esclava amb «%s» establert i un tipus de port «%s». " "«%s» hauria d'establir-se a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Detecta una connexió esclava amb «%s» establert i un tipus de port «%s». " "«%s» hauria d'establir-se a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6195,25 +6191,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7447,11 +7447,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/cs.po b/po/cs.po index 8c24df2c..6542fb29 100644 --- a/po/cs.po +++ b/po/cs.po @@ -17,7 +17,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2018-09-30 14:02+0200\n" "Last-Translator: Daniel Rusek \n" "Language-Team: Czech \n" @@ -1200,7 +1200,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1545,7 +1545,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1832,7 +1832,7 @@ msgstr "Chyba: hodnota časového limitu „%s“ není platná." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Chyba: hodnota časového limitu „%s“ není platná." @@ -1841,56 +1841,52 @@ msgstr "Chyba: hodnota časového limitu „%s“ není platná." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Chyba: hodnota časového limitu „%s“ není platná." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Chyba: příkaz „%s“ není pro „nm“ platný." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "neplatné pole „%s“" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5897,25 +5893,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7149,11 +7149,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/da.po b/po/da.po index bd1aba64..5053e486 100644 --- a/po/da.po +++ b/po/da.po @@ -13,7 +13,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-12-30 00:00+0200\n" "Last-Translator: scootergrisen\n" "Language-Team: Danish\n" @@ -1212,7 +1212,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1558,7 +1558,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1845,7 +1845,7 @@ msgstr "Fejl: Værdi for tidsudløb “%s” er ikke korrekt." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Fejl: Værdi for tidsudløb “%s” er ikke korrekt." @@ -1854,56 +1854,52 @@ msgstr "Fejl: Værdi for tidsudløb “%s” er ikke korrekt." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Fejl: Værdi for tidsudløb “%s” er ikke korrekt." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Fejl: “nm”-kommando “%s” er ikke gyldig." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ugyldigt felt “%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5882,25 +5878,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7134,11 +7134,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/de.po b/po/de.po index a8e9e529..202144c2 100644 --- a/po/de.po +++ b/po/de.po @@ -24,7 +24,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2018-07-15 17:31+0200\n" "Last-Translator: Mario Blättermann \n" "Language-Team: Deutsch \n" @@ -1257,7 +1257,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1603,7 +1603,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1895,7 +1895,7 @@ msgstr "Der gemessene Wert %d ist ungültig" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Der mdns-Wert %d ist ungültig" @@ -1904,48 +1904,44 @@ msgstr "Der mdns-Wert %d ist ungültig" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "Flags »%u« sind ungültig. Verwenden Sie eine Kombination von %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "Schnittstellenname ist länger als 15 Zeichen" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Die Adresse ist kein gültiges UTF-8" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ungültiger Runner »%s«" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "Der Eigenschaftentyp sollte auf »%s« eingestellt sein" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" "Der Slave-Typ »%s« erfordert das Vorhandensein der Einstellung »%s« in der " "Verbindung" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1954,14 +1950,14 @@ msgstr "" "Eine Slave-Verbindung mit gesetztem »%s« und dem Port-Typ »%s« erkennen. " "»%s« sollte auf »%s« gesetzt werden." -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Eine Slave-Verbindung mit gesetztem »%s« für »%s« darf nicht die Einstellung " "»%s« haben" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6258,25 +6254,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -8084,11 +8084,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/dz.po b/po/dz.po index a78619c0..eb12a219 100644 --- a/po/dz.po +++ b/po/dz.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2007-03-20 10:17+0530\n" "Last-Translator: sonam pelden \n" "Language-Team: Dzongkha \n" @@ -1172,7 +1172,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1515,7 +1515,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1798,7 +1798,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1807,56 +1807,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "ཝི་པི་ཨེན་མཐུད་ལམ་འདི་ཁ་སྐོང་བརྐྱབ་མ་ཚུགས་" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ཝི་པི་ཨེན་མཐུད་ལམ་'%s'སླར་འདྲེན་འབདཝ་ད་འཛོལ་བ་" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5797,25 +5793,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7051,11 +7051,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/el.po b/po/el.po index cb3f803f..f43e7bca 100644 --- a/po/el.po +++ b/po/el.po @@ -15,7 +15,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-05-29 11:19-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: team@lists.gnome.gr\n" @@ -1279,7 +1279,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1629,7 +1629,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1917,7 +1917,7 @@ msgstr "η τιμή '%s' δεν είναι έγκυρο UUID" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "η τιμή '%s' δεν είναι έγκυρο UUID" @@ -1926,56 +1926,52 @@ msgstr "η τιμή '%s' δεν είναι έγκυρο UUID" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "το '%s' δεν είναι έγκυρο· χρησιμοποιήστε [%s] ή [%s]" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "ο δείκτης '%s' δεν είναι έγκυρος" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "άκυρη επιλογή '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, fuzzy, c-format msgid "property type should be set to '%s'" msgstr "αυτή η ιδιότητα δεν μπορεί να είναι κενή για '%s=%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "απαιτεί την παρουσία της ρύθμισης '%s' στη σύνδεση" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "απαιτεί '%s' ή ρύθμιση '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6156,25 +6152,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7408,11 +7408,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/en_CA.po b/po/en_CA.po index 8595a9a4..f693e3b5 100644 --- a/po/en_CA.po +++ b/po/en_CA.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2005-09-06 14:52-0400\n" "Last-Translator: Adam Weinberger \n" "Language-Team: Canadian English \n" @@ -1198,7 +1198,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1541,7 +1541,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1825,7 +1825,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "VPN connection '%s' said:" @@ -1834,56 +1834,52 @@ msgstr "VPN connection '%s' said:" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Error displaying connection information:" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "IP Address:" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "IP Address:" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5891,25 +5887,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7146,11 +7146,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/en_GB.po b/po/en_GB.po index 480c4cbe..a12c6545 100644 --- a/po/en_GB.po +++ b/po/en_GB.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:17-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Sugar Labs\n" @@ -1230,7 +1230,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1577,7 +1577,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1864,7 +1864,7 @@ msgstr "Error: timeout value '%s' is not valid." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Error: timeout value '%s' is not valid." @@ -1873,56 +1873,52 @@ msgstr "Error: timeout value '%s' is not valid." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Error: timeout value '%s' is not valid." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Error: 'nm' command '%s' is not valid." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "invalid field '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5932,25 +5928,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7184,11 +7184,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/eo.po b/po/eo.po index 8c5d3d62..0db41ea4 100644 --- a/po/eo.po +++ b/po/eo.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-01-12 14:16+0100\n" "Last-Translator: Carmen Bianca BAKKER \n" "Language-Team: Esperanto \n" @@ -1187,7 +1187,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1531,7 +1531,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1818,7 +1818,7 @@ msgstr "Eraro: eltempiĝa valoro '%s' ne validas" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "valoro %d ne validas" @@ -1827,56 +1827,52 @@ msgstr "valoro %d ne validas" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Eraro: eltempiĝa valoro '%s' ne validas" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Eraro: 'nm'-komando '%s' ne validas" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "nevalida kampo \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5822,25 +5818,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7074,11 +7074,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/es.po b/po/es.po index a17de8f6..60b5b7bf 100644 --- a/po/es.po +++ b/po/es.po @@ -24,7 +24,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-05-03 09:09+0200\n" "Last-Translator: Daniel Mustieles \n" "Language-Team: es \n" @@ -1238,7 +1238,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1583,7 +1583,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1875,7 +1875,7 @@ msgstr "El valor medido %d no es válido" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "el valor %d no es válido" @@ -1884,46 +1884,42 @@ msgstr "el valor %d no es válido" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "Los indicadores «%u» no son válidos; use una combinación de %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "el nombre de interfaz es mayor que 15 caracteres" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "El URI no es un UTF-8 válido" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "permiso no válido «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "El tipo de propiedad debe establecerse a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "El tipo de esclavo «%s» requiere un parámetro «%s» en la conexión" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1932,14 +1928,14 @@ msgstr "" "Detecta una conexión esclava con «%s» establecido y un tipo de puerto «%s». " "«%s» se debe establecer a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Una conexión esclava con «%s» establecido a «%s» no puede tener un parámetro " "«%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6227,25 +6223,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -8012,11 +8012,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/et.po b/po/et.po index ba2e3aaf..c17ce568 100644 --- a/po/et.po +++ b/po/et.po @@ -15,7 +15,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:05-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Estonian \n" @@ -1155,7 +1155,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1497,7 +1497,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1779,7 +1779,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1788,56 +1788,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Privaatvõtit ei saa dešifreerida." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "Sertifikaadi andmete lähtestamine nurjus: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5732,25 +5728,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6984,11 +6984,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/eu.po b/po/eu.po index 7bf9b9bd..ddf61216 100644 --- a/po/eu.po +++ b/po/eu.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:06-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Basque \n" @@ -1208,7 +1208,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1552,7 +1552,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1837,7 +1837,7 @@ msgstr "Errorea: denbora-mugaren '%s' balioa ez da baliozkoa." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Errorea: denbora-mugaren '%s' balioa ez da baliozkoa." @@ -1846,56 +1846,52 @@ msgstr "Errorea: denbora-mugaren '%s' balioa ez da baliozkoa." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Errorea: denbora-mugaren '%s' balioa ez da baliozkoa." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Errorea: 'nm' komandoko '%s' ez da baliozkoa." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "VPNren ezkutukoak baliogabeak" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5894,25 +5890,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7146,11 +7146,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/fi.po b/po/fi.po index 71aae9ca..8a7315ac 100644 --- a/po/fi.po +++ b/po/fi.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:18-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Finnish \n" @@ -1208,7 +1208,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1554,7 +1554,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1838,7 +1838,7 @@ msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen" @@ -1847,56 +1847,52 @@ msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "Virhe: annettu parametri on virheellinen." -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5875,25 +5871,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7127,11 +7127,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/fr.gmo b/po/fr.gmo index 974ec4b1..d74bf1a7 100644 Binary files a/po/fr.gmo and b/po/fr.gmo differ diff --git a/po/fr.po b/po/fr.po index a32218b1..02568e99 100644 --- a/po/fr.po +++ b/po/fr.po @@ -16,7 +16,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-08-15 10:06+0000\n" "Last-Translator: ljanda \n" "Language-Team: French \n" @@ -1241,7 +1241,7 @@ msgstr "uuid inattendu %s au lieu de %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1590,7 +1590,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1878,7 +1878,7 @@ msgstr "valeur contrôlée %d non valide" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "la valeur %d n’est pas valide" @@ -1887,47 +1887,43 @@ msgstr "la valeur %d n’est pas valide" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "" "les marqueurs « %u » ne sont pas valides ; utilisez une combinaison de %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "L'option DHCP ne peut pas comporter plus de 255 caractères" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "L'URL MUD n'est pas une URL valide" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "permission non valide \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "le type de propriété doit être défini sur « %s »" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" "le type d'esclave « %s » requiert la présence du paramètre « %s » dans la " "connexion" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1936,14 +1932,14 @@ msgstr "" "Détecte une connexion esclave avec « %s » défini et un type de port « %s ». " "« %s » doit être défini sur « %s »" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Une connexion esclave avec « %s » définie à « %s » ne peut pas avoir un " "paramètre « %s »" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6249,25 +6245,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -8167,13 +8167,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "La passerelle associée à cette configuration. Cela n'a de sens que si des " "\"adresses\" sont également définies. Le but principal de la passerelle est " diff --git a/po/gd.po b/po/gd.po index 214895ba..e8f83997 100644 --- a/po/gd.po +++ b/po/gd.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2016-01-29 11:29+0100\n" "Last-Translator: GunChleoc \n" "Language-Team: Fòram na Gàidhlig\n" @@ -1193,7 +1193,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1541,7 +1541,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1828,7 +1828,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "chan eil \"%s\" 'na luach dligheach airson na buaidh" @@ -1837,56 +1837,52 @@ msgstr "chan eil \"%s\" 'na luach dligheach airson na buaidh" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "chan eil \"%s\" na rèiteachadh sgioba no ainm faidhle dligheach." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "chan eil \"%s\" 'na luach dligheach airson na buaidh" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "geata \"%s\" mì-dhligheach" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, fuzzy, c-format msgid "property type should be set to '%s'" msgstr "chan fhaod a' bhuadh seo a bhith falamh airson \"%s=%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5897,25 +5893,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7152,11 +7152,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/gl.po b/po/gl.po index c5dc8419..c16841fa 100644 --- a/po/gl.po +++ b/po/gl.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:08-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: gnome-l10n-gl@gnome.org\n" @@ -1246,7 +1246,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1590,7 +1590,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1877,7 +1877,7 @@ msgstr "Erro: O valor do tempo de espera máximo «%s» non é válido." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Erro: O valor do tempo de espera máximo «%s» non é válido." @@ -1886,56 +1886,52 @@ msgstr "Erro: O valor do tempo de espera máximo «%s» non é válido." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Erro: O valor do tempo de espera máximo «%s» non é válido." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Erro: «nm» a orde «%s» non é válida." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ruta non válida: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5959,25 +5955,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7211,11 +7211,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/gu.po b/po/gu.po index 6ce2d6af..a497efe1 100644 --- a/po/gu.po +++ b/po/gu.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:23-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: American English \n" @@ -1246,7 +1246,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1596,7 +1596,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1884,7 +1884,7 @@ msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી" @@ -1893,56 +1893,52 @@ msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' યોગ્ય નથી; [%s] અથવા [%s] વાપરો" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "અયોગ્ય IPv4 માર્ગ '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "જોડાણમાં '%s' સુયોજનની હાજરીની જરૂરિયાત છે" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' અથવા '%s' સુયોજનની જરૂરિયાત છે" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6075,25 +6071,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7327,11 +7327,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/he.po b/po/he.po index eac04676..bc5e5351 100644 --- a/po/he.po +++ b/po/he.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2016-04-16 05:26-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: he\n" @@ -1134,7 +1134,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1475,7 +1475,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1756,7 +1756,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1765,54 +1765,50 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5672,25 +5668,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6924,11 +6924,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/hi.po b/po/hi.po index 95d5745f..7fc01380 100644 --- a/po/hi.po +++ b/po/hi.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:25-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Hindi \n" @@ -1227,7 +1227,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1577,7 +1577,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1865,7 +1865,7 @@ msgstr "मान '%s' एक वैध UUID नहीं है" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "मान '%s' एक वैध UUID नहीं है" @@ -1874,56 +1874,52 @@ msgstr "मान '%s' एक वैध UUID नहीं है" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' वैध नहीं है; [%s] या [%s] उपयोग करें" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "सूची '%s' वैध नहीं है" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "अवैध IPv4 रूट '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "विशेषता किस्म को '%s' पर सेट होना चाहिए" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type '%s' के लिए एक '%s' सेटिंग कनेक्शन में चाहिए" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' या '%s' सेटिंग की जरूरत है" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6080,25 +6076,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7332,11 +7332,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/hr.gmo b/po/hr.gmo index d12372d7..d787df4a 100644 Binary files a/po/hr.gmo and b/po/hr.gmo differ diff --git a/po/hr.po b/po/hr.po index d34c50f4..5ff85504 100644 --- a/po/hr.po +++ b/po/hr.po @@ -11,7 +11,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2022-03-31 20:12+0200\n" "Last-Translator: gogo \n" "Language-Team: Croatian \n" @@ -1178,7 +1178,7 @@ msgstr "neočekivani uuid %s umjesto %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1519,7 +1519,7 @@ msgstr "lozinka nije podržana kada vjerodajnica nije PKCS#11 token" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1804,7 +1804,7 @@ msgstr "vrijednost ograničenja podataka %d nije valjana" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "vrijednost %d nije valjana" @@ -1813,43 +1813,39 @@ msgstr "vrijednost %d nije valjana" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%u' oznaka nije valjana; koristite kombinaciju %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "DHCP mogućnost ne može sadržavati više od 255 znakova" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD (Opis upotrebe proizvođača) URL nije valjani URL" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "nevaljane dozvole nisu u obliku \"user:$UNAME[:]\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "vrsta svojstva treba postaviti na '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type '%s' zahtijeva '%s' postavku u povezivanju" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1858,14 +1854,14 @@ msgstr "" "Otkriveno pričuvno povezivanje s '%s' postavkom i ulazom vrste '%s'. '%s' " "treba postaviti na '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Pričuvno povezivanje sa '%s' postavljeno na '%s' ne može sadržavati '%s' " "postavku" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "UUID treba normalizaciju" @@ -6044,25 +6040,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7916,13 +7916,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "Pristupnik pridružen ovom podešavanju. Ovo ima smisla ako je \"addresses\" " "postavljena. Glavna svrha pristupnika je upravljanje sljedećim skokom " diff --git a/po/hu.po b/po/hu.po index 42deb0e1..61c53ba9 100644 --- a/po/hu.po +++ b/po/hu.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:27-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Hungarian \n" @@ -1259,7 +1259,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1608,7 +1608,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1896,7 +1896,7 @@ msgstr "Hiba: a(z) „%s” időkorlát érvénytelen." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Hiba: a(z) „%s” időkorlát érvénytelen." @@ -1905,56 +1905,52 @@ msgstr "Hiba: a(z) „%s” időkorlát érvénytelen." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "„%s=%s” nem érvényes beállítás ehhez: „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "„%s” nem érvényes UUID" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "érvénytelen mező: „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "megköveteli a(z) „%s” beállítás jelenlétét a kapcsolatban" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "a(z) „%s” vagy „%s” beállítás szükséges" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5972,25 +5968,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7224,11 +7224,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/id.po b/po/id.po index 73ac190d..8b84d420 100644 --- a/po/id.po +++ b/po/id.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-12-31 15:54+0700\n" "Last-Translator: Andika Triwidada \n" "Language-Team: GNOME Indonesian Translation Team \n" @@ -1180,7 +1180,7 @@ msgstr "uuid yang tidak diduga %s alih-alih %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1527,7 +1527,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1818,7 +1818,7 @@ msgstr "nilai terukur %d tidak valid" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "nilai %d tidak valid" @@ -1827,46 +1827,42 @@ msgstr "nilai %d tidak valid" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "flag '%u' tidak valid; gunakan kombinasi dari %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "nama antar muka lebih dari 15 karakter" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "URI bukan UTF-8 yang valid" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "izin tak valid \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "tipe properti mesti ditata ke '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type '%s' memerlukan keberadaan pengaturan '%s' dalam koneksi" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1875,14 +1871,14 @@ msgstr "" "Mendeteksi sebuah koneksi slave dengan '%s' ditata dan tipe port '%s'. '%s' " "mesti ditata menjadi '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Sebuah koneksi slave dengan '%s' ditata ke '%s' tidak boleh memiliki setelan " "'%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6076,25 +6072,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7885,11 +7885,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/it.po b/po/it.po index 55aa6c7b..0cbc6847 100644 --- a/po/it.po +++ b/po/it.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-03-21 14:53+0100\n" "Last-Translator: Milo Casagrande \n" "Language-Team: Italian \n" @@ -1227,7 +1227,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1575,7 +1575,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1867,7 +1867,7 @@ msgstr "il valore di limite %d non è valido" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "il valore %d non è valido" @@ -1876,46 +1876,42 @@ msgstr "il valore %d non è valido" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "«%u» flag non sono validi, usare una combinazione di %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "il nome dell'interfaccia è più lungo di 15 caratteri" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "l'URI non è UTF-8 valido" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "esecutore «%s» non valido" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "il tipo della proprietà dovrebbe essere impostato a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type «%s» richiede un'impostazione «%s» nella connessione" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1924,14 +1920,14 @@ msgstr "" "Rilevata una connessione slave con «%s» impostato e un tipo di porta «%s». " "«%s» dovrebbe essere impostato a «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Una connessione slave con «%s» impostato a «%s» non può avere " "un'impostazione «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6156,25 +6152,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7920,11 +7920,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ja.gmo b/po/ja.gmo index bb62b388..46fba2b2 100644 Binary files a/po/ja.gmo and b/po/ja.gmo differ diff --git a/po/ja.po b/po/ja.po index 983491cf..fde30024 100644 --- a/po/ja.po +++ b/po/ja.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-08-15 04:44+0000\n" "Last-Translator: kemorigu \n" "Language-Team: Japanese \n" @@ -1178,7 +1178,7 @@ msgstr "%s ではなく、予期せぬ uuid %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1520,7 +1520,7 @@ msgstr "証明書が PKCS#11 トークンにない場合は、パスワードは #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1810,7 +1810,7 @@ msgstr "測定値 %d は無効です" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "値 %d は無効です" @@ -1819,44 +1819,40 @@ msgstr "値 %d は無効です" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%u' フラグは有効ではありません。%s の組み合わせを使用してください" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "DHCP オプションは 255 文字より長くすることはできません。" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD の URL は有効な URL ではありません" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "無効なパーミッション \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "プロパティータイプは '%s' に設定する必要があります" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "スレーブタイプ '%s' の接続には '%s' 設定が必要です" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1865,12 +1861,12 @@ msgstr "" "'%s' が設定され、ポートタイプが '%s' のスレーブ接続を検出します。'%s' は " "'%s' に設定する必要があります" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' に設定されている '%s' とのスレーブ接続には、'%s' 設定ができません" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6057,25 +6053,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7869,13 +7869,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "この設定に関連付けられたゲートウェイ。これは \"address\" も設定されている場合" "にのみ意味があります。ゲートウェイの主な目的は、デバイス上の標準デフォルト" diff --git a/po/ka.po b/po/ka.po index 4ceaf5a9..36f5c891 100644 --- a/po/ka.po +++ b/po/ka.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2022-07-16 18:47+0200\n" "Last-Translator: Temuri Doghonadze \n" "Language-Team: Georgian \n" "Language-Team: Kannada \n" @@ -1234,7 +1234,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1581,7 +1581,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1873,7 +1873,7 @@ msgstr "'%s' ಮೌಲ್ಯವು ಒಂದು ಸರಿಯಾದ UUID ಆಗ #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "'%s' ಮೌಲ್ಯವು ಒಂದು ಸರಿಯಾದ UUID ಆಗಿಲ್ಲ" @@ -1882,56 +1882,52 @@ msgstr "'%s' ಮೌಲ್ಯವು ಒಂದು ಸರಿಯಾದ UUID ಆಗ msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' ಮಾನ್ಯವಾದುದಲ್ಲ; [%s] ಅಥವ [%s] ಅನ್ನು ಬಳಸಿ" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s\" ಯು ಒಂದು ಮಾನ್ಯವಾದ UUID ಆಗಿಲ್ಲ" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ಅಮಾನ್ಯವಾದ IPv4 ರೌಟ್ '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "ಗುಣದ ಬಗೆಯನ್ನು '%s' ಗೆ ಹೊಂದಿಸಬೇಕು" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "ಸ್ಲೇವ್‌-ಬಗೆ '%s' ಗಾಗಿ ಸಂಪರ್ಕದಲ್ಲಿ '%s' ಸಿದ್ಧತೆಯ ಅಗತ್ಯವಿರುತ್ತದೆ" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' ಅಥವ '%s' ಸಿದ್ಧತೆಯ ಅಗತ್ಯವಿದೆ" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6099,25 +6095,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7351,11 +7351,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ko.gmo b/po/ko.gmo index 3596e50d..f000dd35 100644 Binary files a/po/ko.gmo and b/po/ko.gmo differ diff --git a/po/ko.po b/po/ko.po index 44a5b50b..a97ae2d0 100644 --- a/po/ko.po +++ b/po/ko.po @@ -33,7 +33,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-08-23 16:31+0900\n" "Last-Translator: Changwoo Ryu \n" "Language-Team: GNOME Korea \n" @@ -1181,7 +1181,7 @@ msgstr "예기치 않은 UUID %s, 기대한 값은 %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1524,7 +1524,7 @@ msgstr "인증서가 PKCS#11 토큰에 없는 경우 암호가 지원되지 않 #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1811,7 +1811,7 @@ msgstr "사용량 값 %d이(가) 유효하지 않습니다" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "%d 값은 유효하지 않습니다" @@ -1820,44 +1820,40 @@ msgstr "%d 값은 유효하지 않습니다" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%u' 플래그가 유효하지 않습니다. %s의 조합을 사용하십시오" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "DHCP 옵션은 255자를 초과할 수 없습니다" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD URL이 유효한 URL이 아닙니다" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "잘못된 권한 \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "속성 유형을 '%s'(으)로 설정해야 합니다" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "연결에서 slave-type '%s'에는 '%s' 설정이 필요합니다." -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1866,13 +1862,13 @@ msgstr "" "'%s'(으)로 설정되고 포트 유형이 '%s'인 슬레이브 연결을 감지합니다. '%s'은" "(는) '%s'(으)로 설정해야 합니다" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "'%s'이(가) '%s'(으)로 설정된 슬레이브 연결에는 '%s' 설정이 있으면 안 됩니다." -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6020,25 +6016,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7759,13 +7759,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "이 구성과 연관된 게이트웨이. \"addresses\"도 설정한 경우에만 의미가 있습니" "다. 게이트웨이의 주요 목적은 장치에서 표준 기본 경로의 다음 홉을 제어하는 것" diff --git a/po/ku.po b/po/ku.po index dc6766f4..c66a0827 100644 --- a/po/ku.po +++ b/po/ku.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2007-01-02 21:47+0000\n" "Last-Translator: Erdal Ronahi \n" "Language-Team: Kurdish \n" @@ -1178,7 +1178,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1521,7 +1521,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1805,7 +1805,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Navnîşana IP:" @@ -1814,56 +1814,52 @@ msgstr "Navnîşana IP:" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Girêdanên çalak tune!" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Navnîşana IP:" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "Navnîşana IP:" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5821,25 +5817,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7075,11 +7075,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/lt.po b/po/lt.po index 9f105867..92bb6516 100644 --- a/po/lt.po +++ b/po/lt.po @@ -13,7 +13,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:10-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Lietuvių \n" @@ -1237,7 +1237,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1583,7 +1583,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1871,7 +1871,7 @@ msgstr "indeksas „%s“ yra netinkamas" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "indeksas „%s“ yra netinkamas" @@ -1880,56 +1880,52 @@ msgstr "indeksas „%s“ yra netinkamas" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "„%s“ yra netinkamas; naudokite [%s] arba [%s]" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "„%s“ nėra tinkamas UUID" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "netinkamas IPv4 kelias „%s“" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "reikalauja „%s“ nustatymo ryšyje" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "reikalauja nustatymo „%s“ arba „%s“" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6041,25 +6037,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7293,11 +7293,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/lv.po b/po/lv.po index 2bfd5be1..a9f8fafa 100644 --- a/po/lv.po +++ b/po/lv.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:39-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Latvian \n" @@ -1200,7 +1200,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1542,7 +1542,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1826,7 +1826,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1835,56 +1835,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "IP adrese:" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "IP adrese:" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5827,25 +5823,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7079,11 +7079,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/mk.po b/po/mk.po index 71cd4ad9..74817c92 100644 --- a/po/mk.po +++ b/po/mk.po @@ -13,7 +13,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2016-04-16 12:56-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Macedonian \n" @@ -1140,7 +1140,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1481,7 +1481,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1762,7 +1762,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1771,54 +1771,50 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5678,25 +5674,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6930,11 +6930,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ml.po b/po/ml.po index ca052dfe..b233cdd0 100644 --- a/po/ml.po +++ b/po/ml.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:41-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Malayalam \n" @@ -1248,7 +1248,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1595,7 +1595,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1883,7 +1883,7 @@ msgstr "'%s' സൂചിക ശരിയല്ല" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "'%s' സൂചിക ശരിയല്ല" @@ -1892,56 +1892,52 @@ msgstr "'%s' സൂചിക ശരിയല്ല" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' ശരിയല്ല; [%s] അല്ലെങ്കില്‍ [%s] ഉപയോഗിയ്ക്കുക" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' ശരിയായ യുയുഐഡിയല്ല" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "തെറ്റായ IPv4 റൂട്ട് '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "കണക്ഷനില്‍ '%s' സജ്ജീകരണം ആവശ്യമുണ്ടു്" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' അല്ലെങ്കില്‍ '%s' സജ്ജീകരണം ആവശ്യമുണ്ടു്" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6064,25 +6060,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7316,11 +7316,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/mr.po b/po/mr.po index 09559493..8cd05e70 100644 --- a/po/mr.po +++ b/po/mr.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:43-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Marathi \n" @@ -1223,7 +1223,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1570,7 +1570,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1858,7 +1858,7 @@ msgstr "मूल्य '%s' वैध UUID नाही" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "मूल्य '%s' वैध UUID नाही" @@ -1867,56 +1867,52 @@ msgstr "मूल्य '%s' वैध UUID नाही" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' वैध नाही; [%s] किंवा [%s] याचा वापर करा" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' वैध UUID नाही" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "अवैध IPv4 राउट '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "गुणधर्म प्रकार '%s' करिता सेट केले पाहिजे" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type '%s' ला जोडणी अंतर्गत '%s' सेटिंग आवश्यक" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' किंवा '%s' सेटिंग आवश्यक" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6062,25 +6058,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7314,11 +7314,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/nb.po b/po/nb.po index 23e2ca84..c990c33a 100644 --- a/po/nb.po +++ b/po/nb.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:43-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Norwegian Bokmål \n" @@ -1141,7 +1141,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1482,7 +1482,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1764,7 +1764,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1773,55 +1773,51 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Kunne ikke dekode privat nøkkel." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5698,25 +5694,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6950,11 +6950,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ne.po b/po/ne.po index 641faade..6e92ab67 100644 --- a/po/ne.po +++ b/po/ne.po @@ -13,7 +13,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:26-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Nepali \n" @@ -1175,7 +1175,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1516,7 +1516,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1799,7 +1799,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1808,56 +1808,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "भीपीएन जडान थप गर्न सकिँदैन" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "भीपीएन जडान पुन: प्राप्ति गर्दा त्रुटि '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5758,25 +5754,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7010,11 +7010,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/nl.po b/po/nl.po index 9c4e2b5e..c5d82a35 100644 --- a/po/nl.po +++ b/po/nl.po @@ -19,7 +19,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2022-03-27 21:08+0200\n" "Last-Translator: Nathan Follens \n" "Language-Team: Dutch \n" @@ -1222,7 +1222,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1564,7 +1564,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1851,7 +1851,7 @@ msgstr "Fout: time-out-waarde '%s' is niet geldig." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "waarde %d is ongeldig" @@ -1860,54 +1860,50 @@ msgstr "waarde %d is ongeldig" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Fout: time-out-waarde '%s' is niet geldig." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "DHCP-optie kan niet langer zijn dan 255 tekens" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD-URL is geen geldige URL" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5914,25 +5910,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7167,11 +7167,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/oc.po b/po/oc.po index 37998958..bd00fcab 100644 --- a/po/oc.po +++ b/po/oc.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2021-05-18 21:37+0200\n" "Last-Translator: Quentin PAGÈS\n" "Language-Team: Tot en òc (totenoc.eu)\n" @@ -1217,7 +1217,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1559,7 +1559,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1844,7 +1844,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "camp '%s' invalid" @@ -1853,56 +1853,52 @@ msgstr "camp '%s' invalid" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Error : %s - connexion introbabla." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "camp '%s' invalid" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "camp '%s' invalid" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5905,25 +5901,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7160,11 +7160,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/or.po b/po/or.po index 509836e9..c18b9647 100644 --- a/po/or.po +++ b/po/or.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:45-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Oriya \n" @@ -1236,7 +1236,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1583,7 +1583,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1871,7 +1871,7 @@ msgstr "ଅନୁକ୍ରମଣିକା '%s' ଟି ବୈଧ ନୁହଁ" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "ଅନୁକ୍ରମଣିକା '%s' ଟି ବୈଧ ନୁହଁ" @@ -1880,56 +1880,52 @@ msgstr "ଅନୁକ୍ରମଣିକା '%s' ଟି ବୈଧ ନୁହଁ" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' ଟି ବୈଧ ନୁହଁ; [%s] କିମ୍ବା [%s] କୁ ବ୍ୟବହାର କରନ୍ତୁ" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' ଟି ଗୋଟିଏ ବୈଧ UUID ନୁହଁ" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ଅବୈଧ IPv4 ପଥ '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "ସଂଯୋଗରେ '%s' ବ୍ୟବସ୍ଥାର ଉପସ୍ଥିତି ଆବଶ୍ୟକ" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' କିମ୍ବା '%s' ସଂରଚନା ଆବଶ୍ୟକ" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6050,25 +6046,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7302,11 +7302,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/pa.po b/po/pa.po index 0791d658..da8b7e67 100644 --- a/po/pa.po +++ b/po/pa.po @@ -13,7 +13,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-04-19 10:17-0500\n" "Last-Translator: A S Alam \n" "Language-Team: Punjabi \n" @@ -1184,7 +1184,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1528,7 +1528,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1815,7 +1815,7 @@ msgstr "ਇੰਡੈਕਸ '%s' ਢੁਕਵਾਂ ਨਹੀਂ ਹੈ" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "ਇੰਡੈਕਸ '%s' ਢੁਕਵਾਂ ਨਹੀਂ ਹੈ" @@ -1824,56 +1824,52 @@ msgstr "ਇੰਡੈਕਸ '%s' ਢੁਕਵਾਂ ਨਹੀਂ ਹੈ" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' ਢੁਕਵਾਂ ਨਹੀਂ; [%s] ਜਾਂ [%s] ਵਰਤੋ" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' ਢੁਕਵਾਂ UUID ਨਹੀਂ ਹੈ" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ਅਢੁਕਵਾਂ IPv4 ਰੂਟ '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, fuzzy, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "ਨੂੰ ਸੰਪਰਕ ਵਿੱਚ '%s' ਸੈਟਿੰਗ ਦੀ ਮੌਜੂਦਗੀ ਲੋੜੀਂਦੀ ਹੈ" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "ਸੈਟਿੰਗ '%s' ਜਾਂ '%s' ਲੋੜੀਂਦੀ ਹੈ" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5931,25 +5927,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7183,11 +7183,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/pl.po b/po/pl.po index 861b57d0..f029a455 100644 --- a/po/pl.po +++ b/po/pl.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-04-12 11:20+0200\n" "Last-Translator: Piotr Drąg \n" "Language-Team: Polish \n" @@ -1196,7 +1196,7 @@ msgstr "nieoczekiwany UUID %s zamiast %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1543,7 +1543,7 @@ msgstr "hasło nie jest obsługiwane, kiedy certyfikat nie jest tokenem PKCS#11" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1831,7 +1831,7 @@ msgstr "mierzona wartość %d jest nieprawidłowa" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "wartość %d jest nieprawidłowa" @@ -1840,46 +1840,42 @@ msgstr "wartość %d jest nieprawidłowa" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "flagi „%u” są nieprawidłowe; należy użyć połączenia %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "nazwa interfejsu jest dłuższa niż 15 znaków" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "adres URI nie jest prawidłowym tekstem UTF-8" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "nieprawidłowe uprawnienie „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "typ właściwości musi zostać ustawiony na „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type „%s” wymaga ustawienia „%s” w połączeniu" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1888,13 +1884,13 @@ msgstr "" "Wykryto połączenie podrzędne z ustawionym „%s” i typem portu „%s”. „%s” musi " "zostać ustawione na „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Połączenie podrzędne z „%s” ustawionym na „%s” nie może mieć ustawienia „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6046,25 +6042,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7306,11 +7306,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/pt.po b/po/pt.po index 9c00362c..4bfa5cdf 100644 --- a/po/pt.po +++ b/po/pt.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-10-11 21:09+0100\n" "Last-Translator: Juliano de Souza Camargo \n" "Language-Team: Portuguese < >\n" @@ -1171,7 +1171,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1514,7 +1514,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1797,7 +1797,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1806,56 +1806,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Incapaz de adicionar uma ligação VPN" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "Erro ao obter a ligação VPN '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5793,25 +5789,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7047,11 +7047,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/pt_BR.po b/po/pt_BR.po index f5e525fa..255a5f78 100644 --- a/po/pt_BR.po +++ b/po/pt_BR.po @@ -21,7 +21,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2020-03-10 04:12-0300\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Brazilian Portuguese \n" @@ -1210,7 +1210,7 @@ msgstr "uuid %s inesperado em vez de %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1556,7 +1556,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1847,7 +1847,7 @@ msgstr "valor metrado %d não é válido" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "valor %d não é válido" @@ -1856,46 +1856,42 @@ msgstr "valor %d não é válido" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "“%u” não são sinalizadores válidos; use a combinação de %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "o nome da interface é maior que 15 caracteres" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "URI não é um UTF-8 válido" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "permissão inválida “%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "tipo de propriedade deveria ser definida para “%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "tipo escravo “%s” requer uma definição “%s” na conexão" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1904,14 +1900,14 @@ msgstr "" "Detecta uma conexão escrava com “%s” definido e um tipo de porta “%s”. “%s” " "deveria ser definida para “%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Uma conexão escrava com “%s” definido com “%s” não pode ter uma definição " "“%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6137,25 +6133,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7968,11 +7968,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ro.po b/po/ro.po index 33b2dc7e..245e8866 100644 --- a/po/ro.po +++ b/po/ro.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2022-03-14 13:23+0000\n" "Last-Translator: Sergiu Bivol \n" "Language-Team: Romanian \n" @@ -1176,7 +1176,7 @@ msgstr "UUID neașteptat %s în loc de %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1517,7 +1517,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1798,7 +1798,7 @@ msgstr "valoarea contorizată %d nu e validă" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "valoarea %d nu e validă" @@ -1807,55 +1807,51 @@ msgstr "valoarea %d nu e validă" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "value is not a valid token" msgid "value %u is not a valid combination of MPTCP flags" msgstr "valoarea nu e un jeton valid" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "Opțiunea DHCP nu poate depăși 255 de caractere" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "tipul proprietății trebuie inițializat cu „%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "UUID-ul necesită normalizare" @@ -5752,25 +5748,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7004,11 +7004,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ru.gmo b/po/ru.gmo index 63e8b18f..0a010dbd 100644 Binary files a/po/ru.gmo and b/po/ru.gmo differ diff --git a/po/ru.po b/po/ru.po index b70eead4..d5cbb94b 100644 --- a/po/ru.po +++ b/po/ru.po @@ -21,7 +21,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2021-03-31 20:27+0300\n" "Last-Translator: Дронова Ю \n" "Language-Team: Russian \n" @@ -1209,7 +1209,7 @@ msgstr "непредвиденный uuid %s вместо %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1558,7 +1558,7 @@ msgstr "пароль не поддерживается, если сертифи #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1845,7 +1845,7 @@ msgstr "недействительное лимитное значение %d" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "значение %d не является действительным" @@ -1854,44 +1854,40 @@ msgstr "значение %d не является действительным" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "Флаги «%u» не являются допустимыми; используйте сочетание %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "параметр DHCP не может превышать 255 символов" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD URL не является допустимым URL" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "недопустимые полномочия не в формате \"user:$UNAME[:]\"" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "свойство должно иметь тип «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" "для подчинённого соединения типа «%s» необходимо определить параметр «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1900,14 +1896,14 @@ msgstr "" "Определить подчинённое соединение с установленным «%s» и типом порта «%s». " "«%s» должно иметь значение «%s»." -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Подчинённое подключение со значением '%s' для параметра '%s'не может иметь " "параметр '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6126,25 +6122,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -8091,13 +8091,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "Шлюз, связанный с этой конфигурацией. Имеет значение только при указанном " "параметре \"addresses\". Главное назначение шлюза — контроль следующего " diff --git a/po/rw.po b/po/rw.po index eb597cf1..f2751a55 100644 --- a/po/rw.po +++ b/po/rw.po @@ -16,7 +16,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2005-03-31 20:55-0700\n" "Last-Translator: Steve Murphy \n" "Language-Team: Kinyarwanda \n" @@ -1193,7 +1193,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1536,7 +1536,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1819,7 +1819,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "(Sibyo" @@ -1828,56 +1828,52 @@ msgstr "(Sibyo" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "(Sibyo" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "(Sibyo" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5837,25 +5833,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7092,11 +7092,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/sk.po b/po/sk.po index 4b8eed3a..8ce1fc90 100644 --- a/po/sk.po +++ b/po/sk.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-05-15 16:46+0200\n" "Last-Translator: Jose Riha \n" "Language-Team: Slovak \n" @@ -1197,7 +1197,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1539,7 +1539,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1825,7 +1825,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1834,56 +1834,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "nesprávna adresa IP: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "nesprávna smerová adresa '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5830,25 +5826,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7082,11 +7082,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/sl.po b/po/sl.po index 0b471c41..4941ccea 100644 --- a/po/sl.po +++ b/po/sl.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:11-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Slovenian GNOME Translation Team \n" @@ -1243,7 +1243,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1587,7 +1587,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1874,7 +1874,7 @@ msgstr "Napaka: vrednost časovne omejitve '%s' ni veljavna." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Napaka: vrednost časovne omejitve '%s' ni veljavna." @@ -1883,56 +1883,52 @@ msgstr "Napaka: vrednost časovne omejitve '%s' ni veljavna." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Napaka: vrednost časovne omejitve '%s' ni veljavna." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Napaka: ukaz 'nm' '%s' ni veljaven" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "neveljavno polje '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5924,25 +5920,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7176,11 +7176,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/sq.po b/po/sq.po index 7e6af58e..b2c81e78 100644 --- a/po/sq.po +++ b/po/sq.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:11-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Albanian \n" @@ -1168,7 +1168,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1509,7 +1509,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1790,7 +1790,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1799,54 +1799,50 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5730,25 +5726,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6982,11 +6982,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/sr.po b/po/sr.po index 120ae714..d32e0585 100644 --- a/po/sr.po +++ b/po/sr.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2010-10-18 16:48+0200\n" "Last-Translator: Милош Поповић \n" "Language-Team: Serbian \n" @@ -1211,7 +1211,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1557,7 +1557,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1843,7 +1843,7 @@ msgstr "Грешка: није исправна вредност „%s“ за #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Грешка: није исправна вредност „%s“ за истек времена." @@ -1852,56 +1852,52 @@ msgstr "Грешка: није исправна вредност „%s“ за msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Грешка: „%s“ није исправан аргумент уз опцију „%s“." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Грешка: „nm“ наредба „'%s“ није исправна." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "неисправно поље „%s“" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5952,25 +5948,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7207,11 +7207,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/sr@latin.po b/po/sr@latin.po index 25fe899c..061ffe11 100644 --- a/po/sr@latin.po +++ b/po/sr@latin.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2010-10-18 16:48+0200\n" "Last-Translator: Miloš Popović \n" "Language-Team: Serbian \n" @@ -1214,7 +1214,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1560,7 +1560,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1846,7 +1846,7 @@ msgstr "Greška: nije ispravna vrednost „%s“ za istek vremena." #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "Greška: nije ispravna vrednost „%s“ za istek vremena." @@ -1855,56 +1855,52 @@ msgstr "Greška: nije ispravna vrednost „%s“ za istek vremena." msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "Greška: „%s“ nije ispravan argument uz opciju „%s“." -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Greška: „nm“ naredba „'%s“ nije ispravna." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "neispravno polje „%s“" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5956,25 +5952,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7211,11 +7211,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/sv.po b/po/sv.po index 22200fbc..ebc81d8f 100644 --- a/po/sv.po +++ b/po/sv.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-12-04 20:16+0100\n" "Last-Translator: Josef Andersson \n" "Language-Team: Swedish \n" @@ -1212,7 +1212,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1556,7 +1556,7 @@ msgstr "lösenordet stöds ej när certifikat inte på ett PKCS#11-token" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1848,7 +1848,7 @@ msgstr "mätvärdet %d är inte giltigt" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "mätvärdet %d är inte giltigt" @@ -1857,46 +1857,42 @@ msgstr "mätvärdet %d är inte giltigt" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "”%u”-flaggor är inte giltiga; använd en kombination av %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "gränssnittsnamnet är längre än 15 tecken" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "URI är inte giltig UTF-8" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ogiltig körare ”%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "egenskapstypen borde vara satt till ”%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slavtypen ”%s” kräver en ”%s”-inställning i anslutningen" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1905,13 +1901,13 @@ msgstr "" "Upptäck en slavanslutning med ”%s” satt och en porttyp ”%s”. ”%s” bör sättas " "till ”%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "En slavanslutning med ”%s” satt till ”%s” kan inte ha en inställning ”%s”" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6116,25 +6112,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7800,11 +7800,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/ta.po b/po/ta.po index 73ba34ab..f2478d69 100644 --- a/po/ta.po +++ b/po/ta.po @@ -14,7 +14,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:21-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Tamil \n" @@ -1220,7 +1220,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1567,7 +1567,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1858,7 +1858,7 @@ msgstr "'%s' என்ற மதிப்பு செல்லுபடிய #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "'%s' என்ற மதிப்பு செல்லுபடியாகும் UUID அல்ல" @@ -1867,44 +1867,40 @@ msgstr "'%s' என்ற மதிப்பு செல்லுபடிய msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' செல்லுபடியானதல்ல; [%s] அல்லது [%s] ஐப் பயன்படுத்தவும்" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' என்பது செல்லுபடியாகும் UUID அல்ல" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "தவறான தடம்: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "பண்பு வகை '%s' என அமைக்கப்பட்டிருக்க வேண்டும்" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "ஸ்லேவ் வகை '%s' க்கு இணைப்பில் '%s' அமைப்பு அவசியம்" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1913,14 +1909,14 @@ msgstr "" "'%s' அமைக்கப்பட்டுள்ள மற்றும் '%s' வகை துறை வகையைக் கொண்டுள்ள அடிமை இணைப்பைக் " "கண்டறியவும். '%s' ஆனது '%s' க்கு அமைக்கப்பட வேண்டும்." -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "'%s' அமைக்கப்பட்டுள்ள மற்றும் '%s' வகை துறை வகையைக் கொண்டுள்ள அடிமை இணைப்பைக் " "கண்டறியவும். '%s' ஆனது '%s' க்கு அமைக்கப்பட வேண்டும்." -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6086,25 +6082,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7338,11 +7338,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/te.po b/po/te.po index 9ed1b982..b87318f7 100644 --- a/po/te.po +++ b/po/te.po @@ -11,7 +11,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:58-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Telugu \n" @@ -1223,7 +1223,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1570,7 +1570,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1860,7 +1860,7 @@ msgstr "విలువ '%s' చెల్లునటువంటి UUID కా #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "విలువ '%s' చెల్లునటువంటి UUID కాదు" @@ -1869,56 +1869,52 @@ msgstr "విలువ '%s' చెల్లునటువంటి UUID కా msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' చెల్లునది కాదు; [%s] లేదా [%s] వుపయోగించు" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' చెల్లునటువంటి UUID కాదు" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "చెల్లని IPv4 రౌట్ '%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "లక్షణం రకం '%s' కు అమర్చాలి" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "స్లేవ్-రకం '%s' కు '%s' అమరిక అనుసంధానం నందు కావాలి" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "'%s' లేదా '%s' అమరిక కావాలి" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6064,25 +6060,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7316,11 +7316,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/th.po b/po/th.po index 9c7c0039..9e5b3fc8 100644 --- a/po/th.po +++ b/po/th.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 05:59-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Thai \n" @@ -1199,7 +1199,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1541,7 +1541,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1825,7 +1825,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1834,56 +1834,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "ที่อยู่ไอพี:" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "ที่อยู่ไอพี:" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5832,25 +5828,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7084,11 +7084,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/tr.po b/po/tr.po index 1b5a424c..16f232d3 100644 --- a/po/tr.po +++ b/po/tr.po @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:01-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Türkçe \n" @@ -1238,7 +1238,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1582,7 +1582,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1873,7 +1873,7 @@ msgstr "'%s' değeri geçerli bir UUID değil" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, fuzzy, c-format msgid "value %d is not valid" msgstr "'%s' değeri geçerli bir UUID değil" @@ -1882,44 +1882,40 @@ msgstr "'%s' değeri geçerli bir UUID değil" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "'%s' geçerli değil; [%s] ya da [%s] kullanın" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "'%s' geçerli bir UUID değil" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "geçersiz yönlendirme: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "özellik türü '%s' olarak ayarlanmalı" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "ikincil tür '%s' bağlantı ayarı olarak bir '%s' gereksinimi duyuyor" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1928,14 +1924,14 @@ msgstr "" "'%s' atanmış ve bağlantı noktası türü '%s' olan bir ikincil bağlantı " "algılandı. '%s' '%s' olarak atanmalıdır." -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, fuzzy, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "'%s' atanmış ve bağlantı noktası türü '%s' olan bir ikincil bağlantı " "algılandı. '%s' '%s' olarak atanmalıdır." -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -6122,25 +6118,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7374,11 +7374,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/uk.gmo b/po/uk.gmo index e8e7fc36..1b95d9a4 100644 Binary files a/po/uk.gmo and b/po/uk.gmo differ diff --git a/po/uk.po b/po/uk.po index addf706b..9c75f0a1 100644 --- a/po/uk.po +++ b/po/uk.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2022-07-03 08:50+0300\n" "Last-Translator: Yuri Chornoivan \n" "Language-Team: Ukrainian \n" @@ -1212,7 +1212,7 @@ msgstr "неочікуваний UUID %s замість %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1560,7 +1560,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1844,7 +1844,7 @@ msgstr "лічильне значення %d є некоректним" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "значення %d є некоректним" @@ -1853,43 +1853,39 @@ msgstr "значення %d є некоректним" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "прапорці «%u» не є коректними; скористайтеся комбінацією з %s" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "Довжина параметра DHCP не може перевищувати 255 символів" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "Адреса MUD не є коректною адресою" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "некоректний запис прав доступу, не у форматі «користувач:$UNAME[:]»" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "тип властивості має бути встановлено у значення «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "тип підлеглого з'єднання «%s» потребує параметра «%s» у з'єднанні" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1898,14 +1894,14 @@ msgstr "" "Визначити підлегле з'єднання зі встановленим «%s» і типом порту «%s». «%s» " "слід встановити у значення «%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" "Підлегле з'єднання з «%s», переведене у режим «%s», не може мати параметра " "«%s»" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "UUID потребує нормалізації" @@ -6112,25 +6108,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -8098,13 +8098,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "Шлюз, який пов'язано із цими налаштуваннями. Має значення, лише якщо вказано " "«addresses». Основним призначенням шлюзу є керування наступним переходом у " diff --git a/po/vi.po b/po/vi.po index 3654e41b..7463a767 100644 --- a/po/vi.po +++ b/po/vi.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:11-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Vietnamese \n" @@ -1145,7 +1145,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1487,7 +1487,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1769,7 +1769,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1778,56 +1778,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "Không thể giải mã khoá riêng." -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "Gặp lỗi khi sơ khởi dữ liệu chứng nhận: %s" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5723,25 +5719,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -6975,11 +6975,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/wa.po b/po/wa.po index cafb5380..2d693ca0 100644 --- a/po/wa.po +++ b/po/wa.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2004-09-09 10:41+0200\n" "Last-Translator: Pablo Saratxaga \n" "Language-Team: Walloon \n" @@ -1168,7 +1168,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1510,7 +1510,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1793,7 +1793,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1802,55 +1802,51 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "Raloyaedjes rantoele" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5805,25 +5801,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7059,11 +7059,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/zh_CN.gmo b/po/zh_CN.gmo index 6359537a..7b4d8292 100644 Binary files a/po/zh_CN.gmo and b/po/zh_CN.gmo differ diff --git a/po/zh_CN.po b/po/zh_CN.po index c06535a1..7b6d585a 100644 --- a/po/zh_CN.po +++ b/po/zh_CN.po @@ -20,7 +20,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2021-11-09 20:06+0800\n" "Last-Translator: Dingzhong Chen \n" "Language-Team: Chinese - China \n" @@ -1157,7 +1157,7 @@ msgstr "非预期的 uuid %s，而不是 %s" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1498,7 +1498,7 @@ msgstr "当证书不在 PKCS#11 令牌上时不支持密码" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1781,7 +1781,7 @@ msgstr "计量值 %d 无效" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "值 %d 无效" @@ -1790,43 +1790,39 @@ msgstr "值 %d 无效" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "\"%u\" 标记无效；请使用 %s 的组合" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "DHCP 选项不能多于 255 个字符" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 msgid "MUD URL is not a valid URL" msgstr "MUD URL不是一个有效的URL" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "无效的权限，没有以 \"user:$UNAME[:]\" 为格式" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "属性类型应该设置为 \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type \"%s\" 要求连接中有 \"%s\" 设置" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " @@ -1834,12 +1830,12 @@ msgid "" msgstr "" "检测到设置了 \"%s\" 和端口类型为 \"%s\" 的从连接。\"%s\" 应该设置为 \"%s\"" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "\"%s\" 设为 \"%s\" 的从连接不能有个 \"%s\" 设置" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5943,25 +5939,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7602,13 +7602,24 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:174 #: src/libnmc-setting/settings-docs.h.in:200 +#, fuzzy +#| msgid "" +#| "The gateway associated with this configuration. This is only meaningful " +#| "if \"addresses\" is also set. The gateway's main purpose is to control " +#| "the next hop of the standard default route on the device. Hence, the " +#| "gateway property conflicts with \"never-default\" and will be " +#| "automatically dropped if the IP configuration is set to never-default. As " +#| "an alternative to set the gateway, configure a static default route " +#| "with /0 as prefix length." msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" "与此配置相关联的网关。只有当 \"addresses\" 也被设置时，这才有意义。网关的主要" "目的是控制设备上标准默认路由的下一跳。因此，网关属性与 \"never-default\" 冲" diff --git a/po/zh_HK.po b/po/zh_HK.po index 6d0c45ca..499d6ea2 100644 --- a/po/zh_HK.po +++ b/po/zh_HK.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2017-04-21 06:26-0400\n" "Last-Translator: Copied by Zanata \n" "Language-Team: Chinese (Hong Kong) \n" @@ -1201,7 +1201,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1544,7 +1544,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1828,7 +1828,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "" @@ -1837,56 +1837,52 @@ msgstr "" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, c-format msgid "value %u is not a valid combination of MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 msgid "DHCP option cannot be longer than 255 characters" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "IP 位址：" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "IP 位址：" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5854,25 +5850,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7106,11 +7106,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/po/zh_TW.po b/po/zh_TW.po index 8934e760..307a5597 100644 --- a/po/zh_TW.po +++ b/po/zh_TW.po @@ -20,7 +20,7 @@ msgstr "" "Project-Id-Version: NetworkManager\n" "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/" "NetworkManager/issues\n" -"POT-Creation-Date: 2022-08-15 18:14-0300\n" +"POT-Creation-Date: 2022-08-26 16:42+0200\n" "PO-Revision-Date: 2019-06-28 19:18+0800\n" "Last-Translator: Hsiu-Ming Chang \n" "Language-Team: Traditional Chinese \n" @@ -1172,7 +1172,7 @@ msgstr "" #: src/libnm-core-impl/nm-setting-cdma.c:144 #: src/libnm-core-impl/nm-setting-connection.c:1149 #: src/libnm-core-impl/nm-setting-connection.c:1187 -#: src/libnm-core-impl/nm-setting-connection.c:1530 +#: src/libnm-core-impl/nm-setting-connection.c:1516 #: src/libnm-core-impl/nm-setting-ip-config.c:5423 #: src/libnm-core-impl/nm-setting-ip-tunnel.c:387 #: src/libnm-core-impl/nm-setting-olpc-mesh.c:99 @@ -1514,7 +1514,7 @@ msgstr "證書不在PKCS＃11令牌上時，不支持密碼" #: src/libnm-core-impl/nm-setting-cdma.c:159 #: src/libnm-core-impl/nm-setting-connection.c:1159 #: src/libnm-core-impl/nm-setting-connection.c:1202 -#: src/libnm-core-impl/nm-setting-connection.c:1468 +#: src/libnm-core-impl/nm-setting-connection.c:1454 #: src/libnm-core-impl/nm-setting-gsm.c:298 #: src/libnm-core-impl/nm-setting-gsm.c:353 #: src/libnm-core-impl/nm-setting-gsm.c:396 @@ -1802,7 +1802,7 @@ msgstr "索引「%s」無效" #: src/libnm-core-impl/nm-setting-connection.c:1351 #: src/libnm-core-impl/nm-setting-connection.c:1365 #: src/libnm-core-impl/nm-setting-connection.c:1379 -#: src/libnm-core-impl/nm-setting-connection.c:1454 +#: src/libnm-core-impl/nm-setting-connection.c:1440 #, c-format msgid "value %d is not valid" msgstr "值 %d 無效" @@ -1811,58 +1811,54 @@ msgstr "值 %d 無效" msgid "\"disabled\" flag cannot be combined with other MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1411 -msgid "\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together" -msgstr "" - -#: src/libnm-core-impl/nm-setting-connection.c:1422 +#: src/libnm-core-impl/nm-setting-connection.c:1409 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags" msgstr "" -#: src/libnm-core-impl/nm-setting-connection.c:1435 +#: src/libnm-core-impl/nm-setting-connection.c:1421 #, fuzzy, c-format #| msgid "'%u' flags are not valid; use combination of %s" msgid "value %u is not a valid combination of MPTCP flags" msgstr "「%u」旗標無效；請使用「%s」的組合" -#: src/libnm-core-impl/nm-setting-connection.c:1482 +#: src/libnm-core-impl/nm-setting-connection.c:1468 #, fuzzy msgid "DHCP option cannot be longer than 255 characters" msgstr "接口名稱超過15個字符" -#: src/libnm-core-impl/nm-setting-connection.c:1493 +#: src/libnm-core-impl/nm-setting-connection.c:1479 #, fuzzy msgid "MUD URL is not a valid URL" msgstr "URI無效UTF-8" -#: src/libnm-core-impl/nm-setting-connection.c:1513 +#: src/libnm-core-impl/nm-setting-connection.c:1499 #, fuzzy msgid "invalid permissions not in format \"user:$UNAME[:]\"" msgstr "無效的權限「%s」" -#: src/libnm-core-impl/nm-setting-connection.c:1542 +#: src/libnm-core-impl/nm-setting-connection.c:1528 #, c-format msgid "property type should be set to '%s'" msgstr "屬性類型應設置為'%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1560 +#: src/libnm-core-impl/nm-setting-connection.c:1546 #, c-format msgid "slave-type '%s' requires a '%s' setting in the connection" msgstr "slave-type「%s」需要連線中「%s」設定存在" -#: src/libnm-core-impl/nm-setting-connection.c:1571 +#: src/libnm-core-impl/nm-setting-connection.c:1557 #, c-format msgid "" "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be " "set to '%s'" msgstr "用'檢測從屬連接%s' 設置和端口類型'%s'. “%s' 應該設置為'%s'" -#: src/libnm-core-impl/nm-setting-connection.c:1597 +#: src/libnm-core-impl/nm-setting-connection.c:1583 #, c-format msgid "A slave connection with '%s' set to '%s' cannot have a '%s' setting" msgstr "「%s」設為「%s」的從屬連線不能有「%s」設定" -#: src/libnm-core-impl/nm-setting-connection.c:1614 +#: src/libnm-core-impl/nm-setting-connection.c:1600 msgid "UUID needs normalization" msgstr "" @@ -5958,25 +5954,29 @@ msgid "" "fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) " "will be excluded from being configured as endpoints. If \"disabled\" (0x1), " "MPTCP handling for the interface is disabled and no endpoints are " -"registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP " -"handling is enabled if the interface configures a default route in the main " -"routing table. This choice is per-address family, for example if there is an " -"IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The " -"\"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This " -"flag can also be implied from the presence of other flags. If MPTCP handling " -"is enabled, then endpoints will be configured with the specified address " -"flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), " -"\"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about " -"the flags. If the flags are zero, the global connection default from " -"NetworkManager.conf is honored. If still unspecified, the fallback is either " -"\"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/" -"net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor " -"enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host " -"configuration which the admin can change via sysctl and ip-mptcp. Strict " -"reverse path filtering (rp_filter) breaks many MPTCP use cases, so when " -"MPTCP handling for IPv4 addresses on the interface is enabled, " -"NetworkManager would loosen the strict reverse path filtering (1) to the " -"loose setting (2)." +"registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. " +"This flag can also be implied from the presence of other flags. Even when " +"enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/" +"net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl " +"and this is up to the administrator or distribution. To configure endpoints " +"even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be " +"used. In that case, NetworkManager doesn't look at the sysctl and configures " +"endpoints regardless. Even when enabled, NetworkManager will only configure " +"MPTCP endpoints for a certain address family, if there is a unicast default " +"route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-" +"default-route\" (0x8) can override that. When MPTCP handling is enabled then " +"endpoints are configured with the specified address flags \"signal\" (0x10), " +"\"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) " +"manual for additional information about the flags. If the flags are zero " +"(0x0), the global connection default from NetworkManager.conf is honored. If " +"still unspecified, the fallback is \"enabled,subflow\". Note that this means " +"that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/" +"enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable " +"MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration " +"which the admin can change via sysctl and ip-mptcp. Strict reverse path " +"filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling " +"for IPv4 addresses on the interface is enabled, NetworkManager would loosen " +"the strict reverse path filtering (1) to the loose setting (2)." msgstr "" #: src/libnmc-setting/settings-docs.h.in:18 @@ -7501,11 +7501,13 @@ msgstr "" #: src/libnmc-setting/settings-docs.h.in:200 msgid "" "The gateway associated with this configuration. This is only meaningful if " -"\"addresses\" is also set. The gateway's main purpose is to control the next " -"hop of the standard default route on the device. Hence, the gateway property " -"conflicts with \"never-default\" and will be automatically dropped if the IP " -"configuration is set to never-default. As an alternative to set the gateway, " -"configure a static default route with /0 as prefix length." +"\"addresses\" is also set. Setting the gateway causes NetworkManager to " +"configure a standard default route with the gateway as next hop. This is " +"ignored if \"never-default\" is set. An alternative is to configure the " +"default route explicitly with a manual route and /0 as prefix length. Note " +"that the gateway usually conflicts with routing that NetworkManager " +"configures for WireGuard interfaces, so usually it should not be set in that " +"case. See \"ip4-auto-default-route\"." msgstr "" #: src/libnmc-setting/settings-docs.h.in:175 diff --git a/src/core/devices/nm-device-bond.c b/src/core/devices/nm-device-bond.c index 41473abe..44bb316d 100644 --- a/src/core/devices/nm-device-bond.c +++ b/src/core/devices/nm-device-bond.c @@ -461,7 +461,7 @@ _platform_lnk_bond_init_from_setting(NMSettingBond *s_bond, NMPlatformLnkBond *p props->peer_notif_delay_has = (props->miimon || props->arp_interval) && props->peer_notif_delay; props->arp_all_targets_has = props->arp_interval && props->arp_all_targets; props->resend_igmp_has = props->resend_igmp != 1; - props->lp_interval = props->lp_interval != 1; + props->lp_interval_has = props->lp_interval != 1; props->tlb_dynamic_lb_has = NM_IN_SET(props->mode, NM_BOND_MODE_TLB, NM_BOND_MODE_ALB); } diff --git a/src/core/devices/nm-device-ethernet.c b/src/core/devices/nm-device-ethernet.c index 32f2fbf9..40c6d208 100644 --- a/src/core/devices/nm-device-ethernet.c +++ b/src/core/devices/nm-device-ethernet.c @@ -451,7 +451,7 @@ supplicant_auth_state_changed(NMSupplicantInterface *iface, if (state == NM_SUPPLICANT_AUTH_STATE_SUCCESS) { nm_clear_g_signal_handler(priv->supplicant.iface, &priv->supplicant.iface_state_id); - nm_device_update_dynamic_ip_setup(NM_DEVICE(self)); + nm_device_update_dynamic_ip_setup(NM_DEVICE(self), "supplicant auth state changed"); } } diff --git a/src/core/devices/nm-device.c b/src/core/devices/nm-device.c index c51da9ac..d63b902b 100644 --- a/src/core/devices/nm-device.c +++ b/src/core/devices/nm-device.c @@ -1410,8 +1410,6 @@ _prop_get_connection_mptcp_flags(NMDevice *self) if (connection) { mptcp_flags = nm_setting_connection_get_mptcp_flags(nm_connection_get_setting_connection(connection)); - if (mptcp_flags != NM_MPTCP_FLAGS_NONE) - mptcp_flags = nm_mptcp_flags_normalize(mptcp_flags); } if (mptcp_flags == NM_MPTCP_FLAGS_NONE) { @@ -1423,28 +1421,39 @@ _prop_get_connection_mptcp_flags(NMDevice *self) 0, G_MAXINT64, NM_MPTCP_FLAGS_NONE); - /* We filter out all invalid settings and accept it. Somewhat intentionally, we don't do a - * strict parsing of the value to support forward compatibility. */ - if (v != NM_MPTCP_FLAGS_NONE) - mptcp_flags = nm_mptcp_flags_normalize(v); + if (v != NM_MPTCP_FLAGS_NONE) { + /* We silently ignore all invalid flags (and will normalize them away below). */ + mptcp_flags = (NMMptcpFlags) v; + if (mptcp_flags == NM_MPTCP_FLAGS_NONE) + mptcp_flags = NM_MPTCP_FLAGS_ENABLED; + } } - if (mptcp_flags == NM_MPTCP_FLAGS_NONE) { - gint32 v; - - v = nm_platform_sysctl_get_int32(nm_device_get_platform(self), - NMP_SYSCTL_PATHID_ABSOLUTE("/proc/sys/net/mptcp/enabled"), - -1); - if (v > 0) { - /* if MPTCP is enabled via the sysctl, we use the default. */ - mptcp_flags = _NM_MPTCP_FLAGS_DEFAULT; + if (mptcp_flags == NM_MPTCP_FLAGS_NONE) + mptcp_flags = _NM_MPTCP_FLAGS_DEFAULT; + + mptcp_flags = nm_mptcp_flags_normalize(mptcp_flags); + + if (!NM_FLAGS_HAS(mptcp_flags, NM_MPTCP_FLAGS_DISABLED)) { + if (!NM_FLAGS_HAS(mptcp_flags, NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL)) { + guint32 v; + + /* If enabled, but without "also-without-sysctl", then MPTCP is still + * disabled, if the sysctl says so... + * + * We evaluate this here. The point is that the decision is then cached + * until deactivation/reapply. The user can toggle the sysctl any time, + * but we only pick it up at certain moments (now). */ + v = nm_platform_sysctl_get_int32( + nm_device_get_platform(self), + NMP_SYSCTL_PATHID_ABSOLUTE("/proc/sys/net/mptcp/enabled"), + -1); + if (v <= 0) + mptcp_flags = NM_MPTCP_FLAGS_DISABLED; } else - mptcp_flags = NM_MPTCP_FLAGS_DISABLED; + mptcp_flags = NM_FLAGS_UNSET(mptcp_flags, NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL); } - nm_assert(mptcp_flags != NM_MPTCP_FLAGS_NONE - && mptcp_flags == nm_mptcp_flags_normalize(mptcp_flags)); - return mptcp_flags; } @@ -6323,7 +6332,7 @@ _dev_unmanaged_check_external_down(NMDevice *self, gboolean only_if_unmanaged, g } void -nm_device_update_dynamic_ip_setup(NMDevice *self) +nm_device_update_dynamic_ip_setup(NMDevice *self, const char *reason) { NMDevicePrivate *priv; @@ -6334,6 +6343,8 @@ nm_device_update_dynamic_ip_setup(NMDevice *self) if (priv->state < NM_DEVICE_STATE_IP_CONFIG || priv->state > NM_DEVICE_STATE_ACTIVATED) return; + _LOGD(LOGD_DEVICE, "restarting dynamic IP configuration (%s)", reason); + g_hash_table_remove_all(priv->ip6_saved_properties); if (priv->ipdhcp_data_4.state != NM_DEVICE_IP_STATE_NONE) @@ -6635,6 +6646,7 @@ device_link_changed(gpointer user_data) NMDeviceClass *klass = NM_DEVICE_GET_CLASS(self); NMDevicePrivate *priv = NM_DEVICE_GET_PRIVATE(self); gboolean ip_ifname_changed = FALSE; + gboolean hw_addr_changed; nm_auto_nmpobj const NMPObject *pllink_keep_alive = NULL; const NMPlatformLink *pllink; const char *str; @@ -6681,9 +6693,9 @@ device_link_changed(gpointer user_data) if (ifindex == nm_device_get_ip_ifindex(self)) _stats_update_counters_from_pllink(self, pllink); - had_hw_addr = (priv->hw_addr != NULL); - nm_device_update_hw_address(self); - got_hw_addr = (!had_hw_addr && priv->hw_addr); + had_hw_addr = (priv->hw_addr != NULL); + hw_addr_changed = nm_device_update_hw_address(self); + got_hw_addr = (!had_hw_addr && priv->hw_addr); nm_device_update_permanent_hw_address(self, FALSE); if (pllink->name[0] && !nm_streq(priv->iface, pllink->name)) { @@ -6733,7 +6745,9 @@ device_link_changed(gpointer user_data) /* Update DHCP, etc, if needed */ if (ip_ifname_changed) - nm_device_update_dynamic_ip_setup(self); + nm_device_update_dynamic_ip_setup(self, "IP interface changed"); + else if (hw_addr_changed) + nm_device_update_dynamic_ip_setup(self, "hw-address changed"); was_up = priv->up; priv->up = NM_FLAGS_HAS(pllink->n_ifi_flags, IFF_UP); @@ -6793,7 +6807,7 @@ device_link_changed(gpointer user_data) * renew DHCP leases and such. */ if (priv->state == NM_DEVICE_STATE_ACTIVATED) { - nm_device_update_dynamic_ip_setup(self); + nm_device_update_dynamic_ip_setup(self, "interface got carrier"); } } @@ -6855,7 +6869,7 @@ device_ip_link_changed(gpointer user_data) priv->ip_iface_ = g_strdup(ip_iface); update_prop_ip_iface(self); - nm_device_update_dynamic_ip_setup(self); + nm_device_update_dynamic_ip_setup(self, "interface renamed"); } return G_SOURCE_REMOVE; @@ -15778,6 +15792,13 @@ _set_state_full(NMDevice *self, NMDeviceState state, NMDeviceStateReason reason, if (priv->sys_iface_state == NM_DEVICE_SYS_IFACE_STATE_MANAGED) ip6_managed_setup(self); device_init_static_sriov_num_vfs(self); + + /* We didn't bring the device up and we have little idea + * when was it brought up. Play it safe and assume it could + * have been brought up very recently and it might one of + * those who take time to detect carrier. + */ + carrier_detect_wait(self); } if (priv->sys_iface_state == NM_DEVICE_SYS_IFACE_STATE_MANAGED) { @@ -15785,13 +15806,6 @@ _set_state_full(NMDevice *self, NMDeviceState state, NMDeviceStateReason reason, if (!nm_device_bring_up(self, TRUE, &no_firmware) && no_firmware) _LOGW(LOGD_PLATFORM, "firmware may be missing."); nm_device_set_firmware_missing(self, no_firmware ? TRUE : FALSE); - } else { - /* We didn't bring the device up and we have little idea - * when was it brought up. Play it safe and assume it could - * have been brought up very recently and it might one of - * those who take time to detect carrier. - */ - carrier_detect_wait(self); } /* Ensure the device gets deactivated in response to stuff like diff --git a/src/core/devices/nm-device.h b/src/core/devices/nm-device.h index 382c8660..de850e68 100644 --- a/src/core/devices/nm-device.h +++ b/src/core/devices/nm-device.h @@ -764,7 +764,7 @@ void nm_device_update_metered(NMDevice *self); gboolean nm_device_update_hw_address(NMDevice *self); void nm_device_update_initial_hw_address(NMDevice *self); void nm_device_update_permanent_hw_address(NMDevice *self, gboolean force_freeze); -void nm_device_update_dynamic_ip_setup(NMDevice *self); +void nm_device_update_dynamic_ip_setup(NMDevice *self, const char *reason); guint nm_device_get_supplicant_timeout(NMDevice *self); gboolean nm_device_auth_retries_try_next(NMDevice *self); diff --git a/src/core/devices/wifi/nm-device-wifi.c b/src/core/devices/wifi/nm-device-wifi.c index 39c68d77..43798b85 100644 --- a/src/core/devices/wifi/nm-device-wifi.c +++ b/src/core/devices/wifi/nm-device-wifi.c @@ -2520,7 +2520,7 @@ supplicant_iface_state(NMDeviceWifi *self, _LOGD(LOGD_WIFI, "supplicant state settled after roaming, renew dynamic IP configuration"); nm_clear_g_source_inst(&priv->roam_supplicant_wait_source); - nm_device_update_dynamic_ip_setup(device); + nm_device_update_dynamic_ip_setup(device, "roamed to a different AP"); } } break; @@ -2663,7 +2663,7 @@ supplicant_iface_notify_current_bss(NMSupplicantInterface *iface, if (nm_supplicant_interface_get_state(priv->sup_iface) == NM_SUPPLICANT_INTERFACE_STATE_COMPLETED) { - nm_device_update_dynamic_ip_setup(NM_DEVICE(self)); + nm_device_update_dynamic_ip_setup(NM_DEVICE(self), "roamed to a different AP"); } else { /* Wait that the authentication to new the AP completes before * trying to renew, otherwise the DHCP REQUEST could be lost diff --git a/src/core/nm-l3cfg.c b/src/core/nm-l3cfg.c index b2fbb031..69ea0d26 100644 --- a/src/core/nm-l3cfg.c +++ b/src/core/nm-l3cfg.c @@ -4307,13 +4307,13 @@ _l3_commit_mptcp_af(NML3Cfg *self, if (mptcp_flags == NM_MPTCP_FLAGS_NONE || NM_FLAGS_HAS(mptcp_flags, NM_MPTCP_FLAGS_DISABLED)) mptcp_flags = NM_MPTCP_FLAGS_DISABLED; - else if (NM_FLAGS_HAS(mptcp_flags, NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE)) { - /* Whether MPTCP is enabled/disabled, depends on whether we have a unicast default - * route (in the main routing table). */ + else if (!NM_FLAGS_HAS(mptcp_flags, NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE)) { + /* Whether MPTCP is enabled/disabled (per address family), depends on whether we have a unicast + * default route (in the main routing table). */ if (self->priv.p->combined_l3cd_commited && nm_l3_config_data_get_best_default_route(self->priv.p->combined_l3cd_commited, addr_family)) - mptcp_flags = NM_FLAGS_UNSET(mptcp_flags, NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE) + mptcp_flags = NM_FLAGS_UNSET(mptcp_flags, NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE) | NM_MPTCP_FLAGS_ENABLED; else mptcp_flags = NM_MPTCP_FLAGS_DISABLED; diff --git a/src/core/nm-manager.c b/src/core/nm-manager.c index 3af24aa0..822df7ad 100644 --- a/src/core/nm-manager.c +++ b/src/core/nm-manager.c @@ -6580,7 +6580,7 @@ do_sleep_wake(NMManager *self, gboolean sleeping_changed) && !nm_device_get_unmanaged_flags(device, NM_UNMANAGED_SLEEPING)) { /* DHCP leases of software devices could have gone stale * so we need to renew them. */ - nm_device_update_dynamic_ip_setup(device); + nm_device_update_dynamic_ip_setup(device, "wake up"); continue; } diff --git a/src/libnm-client-impl/nm-remote-connection.c b/src/libnm-client-impl/nm-remote-connection.c index efc4dbfb..23dfc1da 100644 --- a/src/libnm-client-impl/nm-remote-connection.c +++ b/src/libnm-client-impl/nm-remote-connection.c @@ -443,7 +443,11 @@ nm_remote_connection_delete_finish(NMRemoteConnection *connection, * Returns: (transfer full): a #GVariant of type %NM_VARIANT_TYPE_CONNECTION containing * @connection's secrets, or %NULL on error. * - * Deprecated: 1.22: Use nm_remote_connection_get_secrets_async() or GDBusConnection. + * Warning: NMClient contains a cache of objects on D-Bus. This cache gets updated + * with D-Bus signals when iterating the GMainContext. This function performs a + * (pseudo) blocking D-Bus call. Aside blocking, the result will not be in sync + * and not be ordered with the content of the NMClient cache. + * This function used to be deprecated between 1.22 and 1.38 releases. **/ GVariant * nm_remote_connection_get_secrets(NMRemoteConnection *connection, diff --git a/src/libnm-client-impl/nm-settings-docs-gir.xml b/src/libnm-client-impl/nm-settings-docs-gir.xml index 0306dcd9..3ce853e4 100644 --- a/src/libnm-client-impl/nm-settings-docs-gir.xml +++ b/src/libnm-client-impl/nm-settings-docs-gir.xml @@ -31,17 +31,19 @@ If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. + The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + + If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. - Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". + Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://". The special value "none" is allowed to indicate that no MUD URL is used. @@ -173,9 +175,9 @@ When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". @@ -257,9 +259,9 @@ When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". diff --git a/src/libnm-client-public/nm-remote-connection.h b/src/libnm-client-public/nm-remote-connection.h index f00b25d6..abfeecb3 100644 --- a/src/libnm-client-public/nm-remote-connection.h +++ b/src/libnm-client-public/nm-remote-connection.h @@ -96,7 +96,6 @@ gboolean nm_remote_connection_delete_finish(NMRemoteConnection *connection, GAsyncResult *result, GError **error); -_NM_DEPRECATED_SYNC_METHOD GVariant *nm_remote_connection_get_secrets(NMRemoteConnection *connection, const char *setting_name, GCancellable *cancellable, diff --git a/src/libnm-core-aux-intern/nm-libnm-core-utils.c b/src/libnm-core-aux-intern/nm-libnm-core-utils.c index ba05b6cd..1febe5df 100644 --- a/src/libnm-core-aux-intern/nm-libnm-core-utils.c +++ b/src/libnm-core-aux-intern/nm-libnm-core-utils.c @@ -51,7 +51,7 @@ NM_UTILS_STRING_TABLE_LOOKUP_DEFINE( } }, { return NM_BOND_AD_SELECT_STABLE; }, - {"bandwith", NM_BOND_AD_SELECT_BANDWIDTH}, + {"bandwidth", NM_BOND_AD_SELECT_BANDWIDTH}, {"count", NM_BOND_AD_SELECT_COUNT}, {"stable", NM_BOND_AD_SELECT_STABLE}, ); @@ -512,14 +512,8 @@ nm_mptcp_flags_normalize(NMMptcpFlags flags) /* Clear all unknown flags. */ flags &= _NM_MPTCP_FLAGS_ALL; - /* We must either set "enabled-on-global-iface" or "enabled". The - * former takes precedence, if they are both set. - * - * If neither is set, we default to "enabled". */ - if (NM_FLAGS_HAS(flags, NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE)) - flags = NM_FLAGS_UNSET(flags, NM_MPTCP_FLAGS_ENABLED); - else - flags = NM_FLAGS_SET(flags, NM_MPTCP_FLAGS_ENABLED); + /* Not disabled means enabled. */ + flags |= NM_MPTCP_FLAGS_ENABLED; if (NM_FLAGS_ALL(flags, NM_MPTCP_FLAGS_SIGNAL | NM_MPTCP_FLAGS_FULLMESH)) flags = NM_FLAGS_UNSET(flags, NM_MPTCP_FLAGS_FULLMESH); diff --git a/src/libnm-core-aux-intern/nm-libnm-core-utils.h b/src/libnm-core-aux-intern/nm-libnm-core-utils.h index 5c827c01..0208bfdb 100644 --- a/src/libnm-core-aux-intern/nm-libnm-core-utils.h +++ b/src/libnm-core-aux-intern/nm-libnm-core-utils.h @@ -269,13 +269,13 @@ gpointer _nm_connection_new_setting(NMConnection *connection, GType gtype); /*****************************************************************************/ -#define _NM_MPTCP_FLAGS_ALL \ - ((NMMptcpFlags) (NM_MPTCP_FLAGS_DISABLED | NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE \ - | NM_MPTCP_FLAGS_ENABLED | NM_MPTCP_FLAGS_SIGNAL | NM_MPTCP_FLAGS_SUBFLOW \ - | NM_MPTCP_FLAGS_BACKUP | NM_MPTCP_FLAGS_FULLMESH)) +#define _NM_MPTCP_FLAGS_ALL \ + ((NMMptcpFlags) (NM_MPTCP_FLAGS_DISABLED | NM_MPTCP_FLAGS_ENABLED \ + | NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL \ + | NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE | NM_MPTCP_FLAGS_SIGNAL \ + | NM_MPTCP_FLAGS_SUBFLOW | NM_MPTCP_FLAGS_BACKUP | NM_MPTCP_FLAGS_FULLMESH)) -#define _NM_MPTCP_FLAGS_DEFAULT \ - ((NMMptcpFlags) (NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE | NM_MPTCP_FLAGS_SUBFLOW)) +#define _NM_MPTCP_FLAGS_DEFAULT ((NMMptcpFlags) (NM_MPTCP_FLAGS_ENABLED | NM_MPTCP_FLAGS_SUBFLOW)) NMMptcpFlags nm_mptcp_flags_normalize(NMMptcpFlags flags); diff --git a/src/libnm-core-impl/nm-setting-connection.c b/src/libnm-core-impl/nm-setting-connection.c index 0d307be3..cbce1c12 100644 --- a/src/libnm-core-impl/nm-setting-connection.c +++ b/src/libnm-core-impl/nm-setting-connection.c @@ -1402,19 +1402,6 @@ after_interface_name: } else { guint32 f; - if (NM_FLAGS_ALL(priv->mptcp_flags, - NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE | NM_MPTCP_FLAGS_ENABLED)) { - g_set_error_literal( - error, - NM_CONNECTION_ERROR, - NM_CONNECTION_ERROR_INVALID_PROPERTY, - _("\"enabled\" and \"enabled-on-global-iface\" flag cannot be set together")); - g_prefix_error(error, - "%s.%s: ", - NM_SETTING_CONNECTION_SETTING_NAME, - NM_SETTING_CONNECTION_MPTCP_FLAGS); - return FALSE; - } if (NM_FLAGS_ALL(priv->mptcp_flags, NM_MPTCP_FLAGS_SIGNAL | NM_MPTCP_FLAGS_FULLMESH)) { g_set_error_literal(error, NM_CONNECTION_ERROR, @@ -1426,8 +1413,7 @@ after_interface_name: NM_SETTING_CONNECTION_MPTCP_FLAGS); return FALSE; } - f = NM_FLAGS_UNSET(priv->mptcp_flags, NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE) - | ((guint32) NM_MPTCP_FLAGS_ENABLED); + f = priv->mptcp_flags | ((guint32) NM_MPTCP_FLAGS_ENABLED); if (f != nm_mptcp_flags_normalize(f)) { g_set_error(error, NM_CONNECTION_ERROR, @@ -2608,21 +2594,30 @@ nm_setting_connection_class_init(NMSettingConnectionClass *klass) * If "disabled" (0x1), MPTCP handling for the interface is disabled and * no endpoints are registered. * - * The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled - * if the interface configures a default route in the main routing table. - * This choice is per-address family, for example if there is an IPv4 default route - * 0.0.0.0/0, IPv4 endpoints are configured. - * - * The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. + * The "enabled" (0x2) flag means that MPTCP handling is enabled. * This flag can also be implied from the presence of other flags. * - * If MPTCP handling is enabled, then endpoints will be configured - * with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), + * Even when enabled, MPTCP handling will by default still be disabled + * unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager + * does not change the sysctl and this is up to the administrator + * or distribution. To configure endpoints even if the sysctl is + * disabled, "also-without-sysctl" (0x4) flag can be used. In that case, + * NetworkManager doesn't look at the sysctl and configures endpoints + * regardless. + * + * Even when enabled, NetworkManager will only configure MPTCP endpoints + * for a certain address family, if there is a unicast default route (0.0.0.0/0 + * or ::/0) in the main routing table. The flag "also-without-default-route" + * (0x8) can override that. + * + * When MPTCP handling is enabled then endpoints are configured with + * the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), * "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. * - * If the flags are zero, the global connection default from NetworkManager.conf is - * honored. If still unspecified, the fallback is either "disabled" or - * "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + * If the flags are zero (0x0), the global connection default from NetworkManager.conf is + * honored. If still unspecified, the fallback is "enabled,subflow". + * Note that this means that MPTCP is by default done depending on the + * "/proc/sys/net/mptcp/enabled" sysctl. * * NetworkManager does not change the MPTCP limits nor enable MPTCP via * "/proc/sys/net/mptcp/enabled". That is a host configuration which the diff --git a/src/libnm-core-impl/nm-setting-ip-config.c b/src/libnm-core-impl/nm-setting-ip-config.c index ab760c4e..916a8038 100644 --- a/src/libnm-core-impl/nm-setting-ip-config.c +++ b/src/libnm-core-impl/nm-setting-ip-config.c @@ -6304,12 +6304,14 @@ nm_setting_ip_config_class_init(NMSettingIPConfigClass *klass) * The gateway associated with this configuration. This is only meaningful * if #NMSettingIPConfig:addresses is also set. * - * The gateway's main purpose is to control the next hop of the standard default route on the device. - * Hence, the gateway property conflicts with #NMSettingIPConfig:never-default and will be - * automatically dropped if the IP configuration is set to never-default. + * Setting the gateway causes NetworkManager to configure a standard default route + * with the gateway as next hop. This is ignored if #NMSettingIPConfig:never-default + * is set. An alternative is to configure the default route explicitly with a manual + * route and /0 as prefix length. * - * As an alternative to set the gateway, configure a static default route with /0 as prefix - * length. + * Note that the gateway usually conflicts with routing that NetworkManager configures + * for WireGuard interfaces, so usually it should not be set in that case. See + * #NMSettingWireGuard:ip4-auto-default-route. **/ obj_properties[PROP_GATEWAY] = g_param_spec_string( NM_SETTING_IP_CONFIG_GATEWAY, diff --git a/src/libnm-core-impl/tests/test-general.c b/src/libnm-core-impl/tests/test-general.c index 3c8cd3ba..64b3dca7 100644 --- a/src/libnm-core-impl/tests/test-general.c +++ b/src/libnm-core-impl/tests/test-general.c @@ -9123,6 +9123,10 @@ test_nm_utils_enum(void) .nick = "nick-5", .value = 5, }, + { + .nick = "nick-0", + .value = 0, + }, { .nick = "nick-red", .value = NM_TEST_GENERAL_COLOR_FLAGS_RED, @@ -9170,6 +9174,8 @@ test_nm_utils_enum(void) "nick-5, green", color_value_infos); + _test_nm_utils_enum_to_str_do_full(color_flags, 0, "nick-0", color_value_infos); + _test_nm_utils_enum_from_str_do(bool_enum, "", FALSE, 0, NULL); _test_nm_utils_enum_from_str_do(bool_enum, " ", FALSE, 0, NULL); _test_nm_utils_enum_from_str_do(bool_enum, "invalid", FALSE, 0, "invalid"); diff --git a/src/libnm-core-public/nm-dbus-interface.h b/src/libnm-core-public/nm-dbus-interface.h index a980f5aa..4557dde0 100644 --- a/src/libnm-core-public/nm-dbus-interface.h +++ b/src/libnm-core-public/nm-dbus-interface.h @@ -1319,12 +1319,25 @@ typedef enum /*< flags >*/ { * NMMptcpFlags: * @NM_MPTCP_FLAGS_NONE: The default, meaning that no MPTCP flags are set. * @NM_MPTCP_FLAGS_DISABLED: don't configure MPTCP endpoints on the device. - * @NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE: MPTCP handling is enabled - * or disabled depending on whether a /0 default route (either IPv4 or IPv6) is - * configured in the main routing table. * @NM_MPTCP_FLAGS_ENABLED: MPTCP is enabled and endpoints will be configured. * This flag is implied if any of the other flags indicate that * MPTCP is enabled and therefore in most cases unnecessary. + * Note that if "/proc/sys/net/mptcp/enabled" sysctl is disabled, MPTCP + * handling is disabled despite this flag. This can be overruled with the + * "also-without-sysctl" flag. + * Note that by default interfaces that don't have a default route are + * excluded from having MPTCP endpoints configured. This can be overruled + * with the "also-without-default-route" and this affects endpoints + * per address family. + * @NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL: even if MPTCP handling is enabled + * via the "enabled" flag, it is ignored unless "/proc/sys/net/mptcp/enabled" + * is on. With this flag, MPTCP endpoints will be configured regardless + * of the sysctl setting. + * @NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE: even if MPTCP handling is enabled + * via the "enabled" flag, it is ignored per-address family unless NetworkManager + * configures a default route. With this flag, NetworkManager will also configure + * MPTCP endpoints if there is no default route. This takes effect per-address + * family. * @NM_MPTCP_FLAGS_SIGNAL: Flag for the MPTCP endpoint. The endpoint will be * announced/signaled to each peer via an MPTCP ADD_ADDR sub-option. * @NM_MPTCP_FLAGS_SUBFLOW: Flag for the MPTCP endpoint. If additional subflow creation @@ -1350,9 +1363,11 @@ typedef enum /*< flags >*/ { typedef enum /*< flags >*/ { NM_MPTCP_FLAGS_NONE = 0, - NM_MPTCP_FLAGS_DISABLED = 0x1, - NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE = 0x2, - NM_MPTCP_FLAGS_ENABLED = 0x4, + NM_MPTCP_FLAGS_DISABLED = 0x1, + NM_MPTCP_FLAGS_ENABLED = 0x2, + + NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL = 0x4, + NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE = 0x8, NM_MPTCP_FLAGS_SIGNAL = 0x10, NM_MPTCP_FLAGS_SUBFLOW = 0x20, diff --git a/src/libnm-core-public/nm-dbus-types.xml b/src/libnm-core-public/nm-dbus-types.xml index 0c8425ef..cb72820d 100644 --- a/src/libnm-core-public/nm-dbus-types.xml +++ b/src/libnm-core-public/nm-dbus-types.xml @@ -2248,14 +2248,19 @@ don't configure MPTCP endpoints on the device. - NM_MPTCP_FLAGS_ENABLED_ON_GLOBAL_IFACE + NM_MPTCP_FLAGS_ENABLED = 0x2 - MPTCP handling is enabled or disabled depending on whether a /0 default route (either IPv4 or IPv6) is configured in the main routing table. + MPTCP is enabled and endpoints will be configured. This flag is implied if any of the other flags indicate that MPTCP is enabled and therefore in most cases unnecessary. Note that if "/proc/sys/net/mptcp/enabled" sysctl is disabled, MPTCP handling is disabled despite this flag. This can be overruled with the "also-without-sysctl" flag. Note that by default interfaces that don't have a default route are excluded from having MPTCP endpoints configured. This can be overruled with the "also-without-default-route" and this affects endpoints per address family. - NM_MPTCP_FLAGS_ENABLED + NM_MPTCP_FLAGS_ALSO_WITHOUT_SYSCTL = 0x4 - MPTCP is enabled and endpoints will be configured. This flag is implied if any of the other flags indicate that MPTCP is enabled and therefore in most cases unnecessary. + even if MPTCP handling is enabled via the "enabled" flag, it is ignored unless "/proc/sys/net/mptcp/enabled" is on. With this flag, MPTCP endpoints will be configured regardless of the sysctl setting. + + + NM_MPTCP_FLAGS_ALSO_WITHOUT_DEFAULT_ROUTE + = 0x8 + even if MPTCP handling is enabled via the "enabled" flag, it is ignored per-address family unless NetworkManager configures a default route. With this flag, NetworkManager will also configure MPTCP endpoints if there is no default route. This takes effect per-address family. NM_MPTCP_FLAGS_SIGNAL diff --git a/src/libnm-core-public/nm-version-macros.h b/src/libnm-core-public/nm-version-macros.h index f61f68b7..acf84ddd 100644 --- a/src/libnm-core-public/nm-version-macros.h +++ b/src/libnm-core-public/nm-version-macros.h @@ -22,7 +22,7 @@ * Evaluates to the minor version number of NetworkManager which this source * is compiled against. */ -#define NM_MINOR_VERSION (39) +#define NM_MINOR_VERSION (40) /** * NM_MICRO_VERSION: @@ -30,7 +30,7 @@ * Evaluates to the micro version number of NetworkManager which this source * compiled against. */ -#define NM_MICRO_VERSION (90) +#define NM_MICRO_VERSION (0) /** * NM_CHECK_VERSION: diff --git a/src/libnm-glib-aux/nm-enum-utils.c b/src/libnm-glib-aux/nm-enum-utils.c index b7f7a3f6..2593a9cd 100644 --- a/src/libnm-glib-aux/nm-enum-utils.c +++ b/src/libnm-glib-aux/nm-enum-utils.c @@ -136,7 +136,8 @@ _nm_utils_enum_to_str_full(GType type, else return g_strdup(enum_value->value_nick); } else if (G_IS_FLAGS_CLASS(klass)) { - unsigned uvalue = (unsigned) value; + unsigned uvalue = (unsigned) value; + gboolean uvalue_was_zero = (uvalue == 0); GFlagsValue *flags_value; NMStrBuf strbuf; @@ -147,6 +148,9 @@ _nm_utils_enum_to_str_full(GType type, for (; value_infos && value_infos->nick; value_infos++) { nm_assert(_enum_is_valid_flags_nick(value_infos->nick)); + if (value_infos->value == 0 && !uvalue_was_zero) + continue; + if (uvalue == 0) { if (value_infos->value != 0) continue; diff --git a/src/libnmc-setting/settings-docs-input.xml b/src/libnmc-setting/settings-docs-input.xml index 87302f0e..d9ce0e2d 100644 --- a/src/libnmc-setting/settings-docs-input.xml +++ b/src/libnmc-setting/settings-docs-input.xml @@ -26,17 +26,19 @@ This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved. Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately. Whether the connection is metered. - When updating this property on a currently activated connection, the change takes effect immediately. Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. + When updating this property on a currently activated connection, the change takes effect immediately. Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2). Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. - The flag "enabled-on-global-iface" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. + The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. - The "enabled" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. + Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. - If MPTCP handling is enabled, then endpoints will be configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. - If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either "disabled" or "enabled-on-global-iface,subflow" depending on "/proc/sys/net/mptcp/enabled". + When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. + + If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. @@ -158,11 +160,11 @@ When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. - When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. The gateway associated with this configuration. This is only meaningful if "addresses" is also set. + When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". Since 1.40 Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default". @@ -328,11 +330,11 @@ Example: priority 5 from 192.167.4.0/24 table 45 When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. - When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length. The gateway associated with this configuration. This is only meaningful if "addresses" is also set. + When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15). The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". The gateway associated with this configuration. This is only meaningful if "addresses" is also set. - The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with "never-default" and will be automatically dropped if the IP configuration is set to never-default. + Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. - As an alternative to set the gateway, configure a static default route with /0 as prefix length. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). + Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route". When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". If also global configuration is unspecified or set to "-1", fallback to read "/proc/sys/net/ipv6/conf/default/use_tempaddr". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the "addr-gen-mode" property's "stable-privacy" setting as another way of avoiding host tracking with IPv6 addresses. Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to "-1" (unknown) means fallback to global configuration "ipv6.ip6-privacy". diff --git a/src/libnmc-setting/settings-docs.h b/src/libnmc-setting/settings-docs.h index 3e86c04b..1ed2f134 100644 --- a/src/libnmc-setting/settings-docs.h +++ b/src/libnmc-setting/settings-docs.h @@ -14,7 +14,7 @@ #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MASTER N_("Interface name of the master device or UUID of the master connection.") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MDNS N_("Whether mDNS is enabled for the connection. The permitted values are: \"yes\" (2) register hostname and resolving for the connection, \"no\" (0) disable mDNS for the interface, \"resolve\" (1) do not register hostname but allow resolving of mDNS host names and \"default\" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, \"default\" ultimately depends on the DNS plugin (which for systemd-resolved currently means \"no\"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_METERED N_("Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.") -#define DESCRIBE_DOC_NM_SETTING_CONNECTION_MPTCP_FLAGS N_("Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If \"disabled\" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The \"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either \"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).") +#define DESCRIBE_DOC_NM_SETTING_CONNECTION_MPTCP_FLAGS N_("Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If \"disabled\" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-default-route\" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is \"enabled,subflow\". Note that this means that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MUD_URL N_("If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with \"https://\". The special value \"none\" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is \"none\".") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MULTI_CONNECT N_("Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_PERMISSIONS N_("An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form \"[type]:[id]:[reserved]\"; for example, \"user:dcbw:blah\". At this time only the \"user\" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the \":\" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.") @@ -171,7 +171,7 @@ #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_DNS_OPTIONS N_("Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are \"attempts\", \"debug\", \"edns0\", \"inet6\", \"ip6-bytestring\", \"ip6-dotint\", \"ndots\", \"no-check-names\", \"no-ip6-dotint\", \"no-reload\", \"no-tld-query\", \"rotate\", \"single-request\", \"single-request-reopen\", \"timeout\", \"trust-ad\", \"use-vc\". The \"trust-ad\" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have \"trust-ad\" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then \"edns0\" and \"trust-ad\" are automatically added.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_DNS_PRIORITY N_("DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the \"rotate\" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_DNS_SEARCH N_("List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting \"ignore-auto-dns\". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).") -#define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with \"never-default\" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.") +#define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if \"never-default\" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See \"ip4-auto-default-route\".") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_IGNORE_AUTO_DNS N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the \"dns\" and \"dns-search\" properties, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_IGNORE_AUTO_ROUTES N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured routes are ignored and only routes specified in the \"routes\" property, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_LINK_LOCAL N_("Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to \"auto\", the value is dependent on \"ipv4.method\". When set to \"default\", it honors the global connection default, before falling back to \"auto\". Note that if \"ipv4.method\" is \"disabled\", then link local addressing is always disabled too. The default is \"default\". Since 1.40") @@ -197,7 +197,7 @@ #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_DNS_OPTIONS N_("Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are \"attempts\", \"debug\", \"edns0\", \"inet6\", \"ip6-bytestring\", \"ip6-dotint\", \"ndots\", \"no-check-names\", \"no-ip6-dotint\", \"no-reload\", \"no-tld-query\", \"rotate\", \"single-request\", \"single-request-reopen\", \"timeout\", \"trust-ad\", \"use-vc\". The \"trust-ad\" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have \"trust-ad\" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then \"edns0\" and \"trust-ad\" are automatically added.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_DNS_PRIORITY N_("DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the \"rotate\" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_DNS_SEARCH N_("List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting \"ignore-auto-dns\". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).") -#define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with \"never-default\" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.") +#define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if \"never-default\" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See \"ip4-auto-default-route\".") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_IGNORE_AUTO_DNS N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the \"dns\" and \"dns-search\" properties, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_IGNORE_AUTO_ROUTES N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured routes are ignored and only routes specified in the \"routes\" property, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_IP6_PRIVACY N_("Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to \"-1\" (unknown) means fallback to global configuration \"ipv6.ip6-privacy\". If also global configuration is unspecified or set to \"-1\", fallback to read \"/proc/sys/net/ipv6/conf/default/use_tempaddr\". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the \"addr-gen-mode\" property's \"stable-privacy\" setting as another way of avoiding host tracking with IPv6 addresses.") diff --git a/src/libnmc-setting/settings-docs.h.in b/src/libnmc-setting/settings-docs.h.in index 3e86c04b..1ed2f134 100644 --- a/src/libnmc-setting/settings-docs.h.in +++ b/src/libnmc-setting/settings-docs.h.in @@ -14,7 +14,7 @@ #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MASTER N_("Interface name of the master device or UUID of the master connection.") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MDNS N_("Whether mDNS is enabled for the connection. The permitted values are: \"yes\" (2) register hostname and resolving for the connection, \"no\" (0) disable mDNS for the interface, \"resolve\" (1) do not register hostname but allow resolving of mDNS host names and \"default\" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, \"default\" ultimately depends on the DNS plugin (which for systemd-resolved currently means \"no\"). This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_METERED N_("Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.") -#define DESCRIBE_DOC_NM_SETTING_CONNECTION_MPTCP_FLAGS N_("Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If \"disabled\" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The flag \"enabled-on-global-iface\" (0x2) means that MPTCP handling is enabled if the interface configures a default route in the main routing table. This choice is per-address family, for example if there is an IPv4 default route 0.0.0.0/0, IPv4 endpoints are configured. The \"enabled\" (0x4) flag means that MPTCP handling is explicitly enabled. This flag can also be implied from the presence of other flags. If MPTCP handling is enabled, then endpoints will be configured with the specified address flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero, the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is either \"disabled\" or \"enabled-on-global-iface,subflow\" depending on \"/proc/sys/net/mptcp/enabled\". NetworkManager does not change the MPTCP limits nor enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).") +#define DESCRIBE_DOC_NM_SETTING_CONNECTION_MPTCP_FLAGS N_("Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If \"disabled\" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The \"enabled\" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless \"/proc/sys/net/mptcp/enabled\" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, \"also-without-sysctl\" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag \"also-without-default-route\" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags \"signal\" (0x10), \"subflow\" (0x20), \"backup\" (0x40), \"fullmesh\" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is \"enabled,subflow\". Note that this means that MPTCP is by default done depending on the \"/proc/sys/net/mptcp/enabled\" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via \"/proc/sys/net/mptcp/enabled\". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MUD_URL N_("If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with \"https://\". The special value \"none\" is allowed to indicate that no MUD URL is used. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is \"none\".") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_MULTI_CONNECT N_("Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.") #define DESCRIBE_DOC_NM_SETTING_CONNECTION_PERMISSIONS N_("An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form \"[type]:[id]:[reserved]\"; for example, \"user:dcbw:blah\". At this time only the \"user\" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the \":\" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.") @@ -171,7 +171,7 @@ #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_DNS_OPTIONS N_("Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are \"attempts\", \"debug\", \"edns0\", \"inet6\", \"ip6-bytestring\", \"ip6-dotint\", \"ndots\", \"no-check-names\", \"no-ip6-dotint\", \"no-reload\", \"no-tld-query\", \"rotate\", \"single-request\", \"single-request-reopen\", \"timeout\", \"trust-ad\", \"use-vc\". The \"trust-ad\" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have \"trust-ad\" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then \"edns0\" and \"trust-ad\" are automatically added.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_DNS_PRIORITY N_("DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the \"rotate\" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_DNS_SEARCH N_("List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting \"ignore-auto-dns\". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).") -#define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with \"never-default\" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.") +#define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if \"never-default\" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See \"ip4-auto-default-route\".") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_IGNORE_AUTO_DNS N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the \"dns\" and \"dns-search\" properties, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_IGNORE_AUTO_ROUTES N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured routes are ignored and only routes specified in the \"routes\" property, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP4_CONFIG_LINK_LOCAL N_("Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server. When set to \"auto\", the value is dependent on \"ipv4.method\". When set to \"default\", it honors the global connection default, before falling back to \"auto\". Note that if \"ipv4.method\" is \"disabled\", then link local addressing is always disabled too. The default is \"default\". Since 1.40") @@ -197,7 +197,7 @@ #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_DNS_OPTIONS N_("Array of DNS options as described in man 5 resolv.conf. NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties. The currently supported options are \"attempts\", \"debug\", \"edns0\", \"inet6\", \"ip6-bytestring\", \"ip6-dotint\", \"ndots\", \"no-check-names\", \"no-ip6-dotint\", \"no-reload\", \"no-tld-query\", \"rotate\", \"single-request\", \"single-request-reopen\", \"timeout\", \"trust-ad\", \"use-vc\". The \"trust-ad\" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have \"trust-ad\" enabled. When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then \"edns0\" and \"trust-ad\" are automatically added.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_DNS_PRIORITY N_("DNS servers priority. The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority). Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles. Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the \"rotate\" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered. When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_DNS_SEARCH N_("List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names. When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting. When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting \"ignore-auto-dns\". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).") -#define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. The gateway's main purpose is to control the next hop of the standard default route on the device. Hence, the gateway property conflicts with \"never-default\" and will be automatically dropped if the IP configuration is set to never-default. As an alternative to set the gateway, configure a static default route with /0 as prefix length.") +#define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_GATEWAY N_("The gateway associated with this configuration. This is only meaningful if \"addresses\" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if \"never-default\" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See \"ip4-auto-default-route\".") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_IGNORE_AUTO_DNS N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the \"dns\" and \"dns-search\" properties, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_IGNORE_AUTO_ROUTES N_("When \"method\" is set to \"auto\" and this property to TRUE, automatically configured routes are ignored and only routes specified in the \"routes\" property, if any, are used.") #define DESCRIBE_DOC_NM_SETTING_IP6_CONFIG_IP6_PRIVACY N_("Configure IPv6 Privacy Extensions for SLAAC, described in RFC4941. If enabled, it makes the kernel generate a temporary IPv6 address in addition to the public one generated from MAC address via modified EUI-64. This enhances privacy, but could cause problems in some applications, on the other hand. The permitted values are: -1: unknown, 0: disabled, 1: enabled (prefer public address), 2: enabled (prefer temporary addresses). Having a per-connection setting set to \"-1\" (unknown) means fallback to global configuration \"ipv6.ip6-privacy\". If also global configuration is unspecified or set to \"-1\", fallback to read \"/proc/sys/net/ipv6/conf/default/use_tempaddr\". Note that this setting is distinct from the Stable Privacy addresses that can be enabled with the \"addr-gen-mode\" property's \"stable-privacy\" setting as another way of avoiding host tracking with IPv6 addresses.") diff --git a/src/nmcli/generate-docs-nm-settings-nmcli.xml b/src/nmcli/generate-docs-nm-settings-nmcli.xml index 85df9ce5..371081b0 100644 --- a/src/nmcli/generate-docs-nm-settings-nmcli.xml +++ b/src/nmcli/generate-docs-nm-settings-nmcli.xml @@ -420,7 +420,7 @@ + description="Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2)." /> + description="The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route"." /> + description="The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route"." /> + description="Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints. If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered. The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags. Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless. Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that. When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags. If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl. NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp. Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2)." /> + description="The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route"." /> + description="The gateway associated with this configuration. This is only meaningful if "addresses" is also set. Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length. Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route"." />