New upstream version 1.40.2 upstream/1.40.2

70 files changed, 2802 insertions, 3001 deletions

diff --git a/po/Makevars b/po/Makevars
index ebd690f6..b858b6db 100644
--- a/po/Makevars
+++ b/po/Makevars
@@ -75,4 +75,4 @@ PO_DEPENDS_ON_POT = no
 # regenerate PO files on "make dist".  Possible values are "yes" and
 # "no".  Set this to no if the POT file and PO files are maintained
 # externally.
-DIST_DEPENDS_ON_UPDATE_PO = yes
+DIST_DEPENDS_ON_UPDATE_PO = no
diff --git a/po/NetworkManager.pot b/po/NetworkManager.pot
index bb133641..263569a1 100644
--- a/po/NetworkManager.pot
+++ b/po/NetworkManager.pot
@@ -6,10 +6,10 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: NetworkManager 1.40.0\n"
+"Project-Id-Version: NetworkManager 1.40.2\n"
 "Report-Msgid-Bugs-To: https://gitlab.freedesktop.org/NetworkManager/"
 "NetworkManager/issues\n"
-"POT-Creation-Date: 2022-08-26 16:42+0200\n"
+"POT-Creation-Date: 2022-10-18 10:10+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -608,25 +608,25 @@ msgstr ""
 msgid "VPN connection"
 msgstr ""
 
-#: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:5612
+#: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:5594
 #: src/libnm-client-impl/nm-device.c:1779
 #: src/libnm-core-impl/nm-connection.c:3172 src/nmtui/nm-editor-utils.c:196
 msgid "Bond"
 msgstr ""
 
-#: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:5683
+#: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:5665
 #: src/libnm-client-impl/nm-device.c:1781
 #: src/libnm-core-impl/nm-connection.c:3174 src/nmtui/nm-editor-utils.c:214
 msgid "Team"
 msgstr ""
 
-#: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:6020
+#: src/core/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c:6002
 #: src/libnm-client-impl/nm-device.c:1783
 #: src/libnm-core-impl/nm-connection.c:3176 src/nmtui/nm-editor-utils.c:205
 msgid "Bridge"
 msgstr ""
 
-#: src/core/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh.c:8755
+#: src/core/settings/plugins/ifcfg-rh/tests/test-ifcfg-rh.c:8801
 #: src/libnm-core-impl/nm-team-utils.c:2391
 msgid "invalid json"
 msgstr ""
@@ -1573,8 +1573,14 @@ msgid "missing setting"
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-bond-port.c:92
+#: src/libnm-core-impl/nm-setting-bridge-port.c:338
+#: src/libnm-core-impl/nm-setting-ovs-interface.c:312
+#: src/libnm-core-impl/nm-setting-ovs-port.c:193
+#: src/libnm-core-impl/nm-setting-team-port.c:333
 #, c-format
-msgid "A connection with a '%s' setting must have the slave-type set to '%s'"
+msgid ""
+"A connection with a '%s' setting must have the slave-type set to '%s'. "
+"Instead it is '%s'"
 msgstr ""
 
 #: src/libnm-core-impl/nm-setting-bond.c:504
@@ -1601,84 +1607,74 @@ msgstr ""
 msgid "invalid value '%s' for option '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:861
+#: src/libnm-core-impl/nm-setting-bond.c:888
 #, c-format
 msgid "mandatory option '%s' is missing"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:871
+#: src/libnm-core-impl/nm-setting-bond.c:898
 #, c-format
 msgid "'%s' is not a valid value for '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:884
+#: src/libnm-core-impl/nm-setting-bond.c:911
 #, c-format
 msgid "'%s=%s' is incompatible with '%s > 0'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:901
+#: src/libnm-core-impl/nm-setting-bond.c:928
 #, c-format
 msgid "'%s' is not valid for the '%s' option: %s"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:913
+#: src/libnm-core-impl/nm-setting-bond.c:940
 #, c-format
 msgid "'%s' option is only valid for '%s=%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:926
+#: src/libnm-core-impl/nm-setting-bond.c:953
 #, c-format
 msgid "'%s=%s' is not a valid configuration for '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:941
-#: src/libnm-core-impl/nm-setting-bond.c:952
-#: src/libnm-core-impl/nm-setting-bond.c:965
+#: src/libnm-core-impl/nm-setting-bond.c:968
+#: src/libnm-core-impl/nm-setting-bond.c:979
+#: src/libnm-core-impl/nm-setting-bond.c:992
 #, c-format
 msgid "'%s' option requires '%s' option to be enabled"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:982
+#: src/libnm-core-impl/nm-setting-bond.c:1009
 #, c-format
 msgid "'%s' option needs to be a value multiple of '%s' value"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:999
-#: src/libnm-core-impl/nm-setting-bond.c:1010
+#: src/libnm-core-impl/nm-setting-bond.c:1026
+#: src/libnm-core-impl/nm-setting-bond.c:1037
 #, c-format
 msgid "'%s' option requires '%s' option to be set"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1023
+#: src/libnm-core-impl/nm-setting-bond.c:1050
 #, c-format
 msgid "'%s' option is only valid with mode '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1036
+#: src/libnm-core-impl/nm-setting-bond.c:1063
 #, c-format
 msgid "'%s' and '%s' cannot have different values"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1059
+#: src/libnm-core-impl/nm-setting-bond.c:1086
 #, c-format
 msgid "'%s' option should be string"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bond.c:1072
+#: src/libnm-core-impl/nm-setting-bond.c:1099
 #, c-format
 msgid "'%s' option is not valid with mode '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-bridge-port.c:338
-#: src/libnm-core-impl/nm-setting-ovs-interface.c:312
-#: src/libnm-core-impl/nm-setting-ovs-port.c:193
-#: src/libnm-core-impl/nm-setting-team-port.c:333
-#, c-format
-msgid ""
-"A connection with a '%s' setting must have the slave-type set to '%s'. "
-"Instead it is '%s'"
-msgstr ""
-
 #: src/libnm-core-impl/nm-setting-bridge.c:1175
 #, c-format
 msgid "value '%d' is out of range <%d-%d>"
diff --git a/po/as.po b/po/as.po
index 5ed0f2c3..ad3c9179 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:06-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Assamese <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "মান '%s' এটা বৈধ UUID নহয়"
@@ -1884,52 +1884,56 @@ msgstr "মান '%s' এটা বৈধ UUID নহয়"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "সূচী '%s' বৈধ নহয়"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "অবৈধ IPv4 পথ '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "বৈশিষ্ট্য ধৰণ '%s' লৈ সংহতি কৰিব লাগিব"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6094,29 +6098,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7350,13 +7350,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/be@latin.po b/po/be@latin.po
index 15151904..35afe9f8 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2008-03-29 21:43+0200\n"
 "Last-Translator: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>\n"
 "Language-Team: Belarusian Latin <i18n@mova.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1765,50 +1765,54 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5670,29 +5674,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6926,13 +6926,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/bg.po b/po/bg.po
index 71accb23..94fd8cff 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:07-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Bulgarian <dict@fsa-bg.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Ограничението на времето „%s“ не е правилно."
@@ -1869,52 +1869,56 @@ msgstr "Ограничението на времето „%s“ не е прав
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, fuzzy, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr "Ограничението на времето „%s“ не е правилно."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Грешка: „%s“ не е правилна команда за „nm“."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "грешно поле „%s“"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5938,29 +5942,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7194,13 +7194,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/bn_IN.po b/po/bn_IN.po
index f0571150..a30d967f 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:09-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Bengali (India) <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "মান '%s' একটি বৈধ UUID নয়"
@@ -1907,52 +1907,56 @@ msgstr "মান '%s' একটি বৈধ UUID নয়"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "সূচি '%s' বৈধ নয়"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "অবৈধ IPv4 রাউট '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "বিশিষ্টতা ধরন '%s' এ সেট করা উচিত"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "স্লেভ-ধরন '%s' -এর সংযোগে একটি '%s' সেটিং -এর প্রয়োজন"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6124,29 +6128,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7380,13 +7380,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/bs.po b/po/bs.po
index 306fd6da..52e6a128 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:12-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Bosnian <lokal@linux.org.ba>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1801,50 +1801,54 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5730,29 +5734,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6986,13 +6986,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ca.po b/po/ca.po
index 389cba24..e9c835e1 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:12-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Catalan <tradgnome@softcatala.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "el valor %d mesurat no és vàlid"
@@ -1890,41 +1890,45 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ruta no vàlida: %s"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1933,14 +1937,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6191,29 +6195,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7447,13 +7447,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/cs.po b/po/cs.po
index 6542fb29..2c5834d4 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2018-09-30 14:02+0200\n"
 "Last-Translator: Daniel Rusek <mail@asciiwolf.com>\n"
 "Language-Team: Czech <gnome-cs-list@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Chyba: hodnota časového limitu „%s“ není platná."
@@ -1841,52 +1841,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "neplatné pole „%s“"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5893,29 +5897,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7149,13 +7149,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/da.po b/po/da.po
index 5053e486..9cb8c4a0 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Fejl: Værdi for tidsudløb “%s” er ikke korrekt."
@@ -1854,52 +1854,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ugyldigt felt “%s”"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5878,29 +5882,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7134,13 +7134,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/de.po b/po/de.po
index 202144c2..f4270905 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2018-07-15 17:31+0200\n"
 "Last-Translator: Mario Blättermann <mario.blaettermann@gmail.com>\n"
 "Language-Team: Deutsch <gnome-de@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Der mdns-Wert %d ist ungültig"
@@ -1904,44 +1904,48 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ungültiger Runner »%s«"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1950,14 +1954,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6254,29 +6258,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -8084,13 +8084,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/dz.po b/po/dz.po
index eb12a219..6cc550b5 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2007-03-20 10:17+0530\n"
 "Last-Translator: sonam pelden <sonaa_peldn@yahoo.com>\n"
 "Language-Team: Dzongkha <pgeyleg@dit.gov.bt>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1807,52 +1807,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "ཝི་པི་ཨེན་མཐུད་ལམ་འདི་ཁ་སྐོང་བརྐྱབ་མ་ཚུགས་"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ཝི་པི་ཨེན་མཐུད་ལམ་'%s'སླར་འདྲེན་འབདཝ་ད་འཛོལ་བ་"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5793,29 +5797,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7051,13 +7051,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/el.po b/po/el.po
index f43e7bca..4702122f 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-05-29 11:19-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "η τιμή '%s' δεν είναι έγκυρο UUID"
@@ -1926,52 +1926,56 @@ msgstr "η τιμή '%s' δεν είναι έγκυρο UUID"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "ο δείκτης '%s' δεν είναι έγκυρος"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "άκυρη επιλογή '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, fuzzy, c-format
 msgid "property type should be set to '%s'"
 msgstr "αυτή η ιδιότητα δεν μπορεί να είναι κενή για '%s=%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, fuzzy, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "απαιτεί την παρουσία της ρύθμισης '%s' στη σύνδεση"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6152,29 +6156,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7408,13 +7408,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/en_CA.po b/po/en_CA.po
index f693e3b5..dba24013 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2005-09-06 14:52-0400\n"
 "Last-Translator: Adam Weinberger <adamw@gnome.org>\n"
 "Language-Team: Canadian English <adamw@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "VPN connection '%s' said:"
@@ -1834,52 +1834,56 @@ msgstr "VPN connection '%s' said:"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "IP Address:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "IP Address:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5887,29 +5891,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7146,13 +7146,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/en_GB.po b/po/en_GB.po
index a12c6545..6a17cba6 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:17-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Error: timeout value '%s' is not valid."
@@ -1873,52 +1873,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "invalid field '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5928,29 +5932,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7184,13 +7184,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/eo.po b/po/eo.po
index 0db41ea4..6fd82e19 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2020-01-12 14:16+0100\n"
 "Last-Translator: Carmen Bianca BAKKER <carmen@carmenbianca.eu>\n"
 "Language-Team: Esperanto <gnome-eo-list@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "valoro %d ne validas"
@@ -1827,52 +1827,56 @@ msgstr "valoro %d ne validas"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Eraro: 'nm'-komando '%s' ne validas"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "nevalida kampo \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5818,29 +5822,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7074,13 +7074,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/es.po b/po/es.po
index 60b5b7bf..5875c044 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-05-03 09:09+0200\n"
 "Last-Translator: Daniel Mustieles <daniel.mustieles@gmail.com>\n"
 "Language-Team: es <gnome-es-list@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "el valor %d no es válido"
@@ -1884,42 +1884,46 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "permiso no válido «%s»"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1928,14 +1932,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6223,29 +6227,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -8012,13 +8012,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/et.po b/po/et.po
index c17ce568..d583336a 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:05-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Estonian <gnome-et@linux.ee>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1788,52 +1788,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Privaatvõtit ei saa dešifreerida."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "Sertifikaadi andmete lähtestamine nurjus: %s"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5728,29 +5732,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6984,13 +6984,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/eu.po b/po/eu.po
index ddf61216..7045bd6b 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:06-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Basque <itzulpena@euskalgnu.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Errorea: denbora-mugaren '%s' balioa ez da baliozkoa."
@@ -1846,52 +1846,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "VPNren ezkutukoak baliogabeak"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5890,29 +5894,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7146,13 +7146,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/fi.po b/po/fi.po
index 8a7315ac..dd9c49fb 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:18-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Finnish <gnome-fi-laatu@lists.sourceforge.net>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen"
@@ -1847,52 +1847,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Virhe: Kytkentäajan asetus '%s' virheellinen"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "Virhe: annettu parametri on virheellinen."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5871,29 +5875,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7127,13 +7127,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/fr.po b/po/fr.po
index 02568e99..db704f57 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-08-15 10:06+0000\n"
 "Last-Translator: ljanda <ljanda@redhat.com>\n"
 "Language-Team: French <trans-fr@lists.fedoraproject.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "la valeur %d n’est pas valide"
@@ -1887,43 +1887,47 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "permission non valide \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1932,14 +1936,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6245,29 +6249,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -8167,24 +8167,13 @@ 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. 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\"."
+"\"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."
 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 e8f83997..c4bc3cb2 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2016-01-29 11:29+0100\n"
 "Last-Translator: GunChleoc <fios@foramnagaidhlig.net>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "chan eil \"%s\" 'na luach dligheach airson na buaidh"
@@ -1837,52 +1837,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "geata \"%s\" mì-dhligheach"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5893,29 +5897,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7152,13 +7152,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/gl.po b/po/gl.po
index c16841fa..aebf7f95 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:08-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Erro: O valor do tempo de espera máximo «%s» non é válido."
@@ -1886,52 +1886,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ruta non válida: %s"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5955,29 +5959,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7211,13 +7211,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/gu.po b/po/gu.po
index a497efe1..911c35e1 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:23-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: American English <kde-i18n-doc@kde.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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી"
@@ -1893,52 +1893,56 @@ msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "અનુક્રમણિકા '%s' યોગ્ય નથી"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "અયોગ્ય IPv4 માર્ગ '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, fuzzy, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "જોડાણમાં '%s' સુયોજનની હાજરીની જરૂરિયાત છે"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6071,29 +6075,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7327,13 +7327,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/he.po b/po/he.po
index bc5e5351..e9c6ed78 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2016-04-16 05:26-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1765,50 +1765,54 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5668,29 +5672,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6924,13 +6924,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/hi.po b/po/hi.po
index 7fc01380..18233e4d 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:25-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Hindi <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "मान '%s' एक वैध UUID नहीं है"
@@ -1874,52 +1874,56 @@ msgstr "मान '%s' एक वैध UUID नहीं है"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "सूची '%s' वैध नहीं है"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "अवैध IPv4 रूट '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "विशेषता किस्म को '%s' पर सेट होना चाहिए"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6076,29 +6080,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7332,13 +7332,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/hr.gmo b/po/hr.gmo
index d787df4a..b731de6e 100644
--- a/po/hr.gmo
+++ b/po/hr.gmo
Binary files differdiff --git a/po/hr.po b/po/hr.po
index 5ff85504..52d41a92 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2022-03-31 20:12+0200\n"
 "Last-Translator: gogo <trebelnik2@gmail.com>\n"
 "Language-Team: Croatian <hr@li.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "vrijednost %d nije valjana"
@@ -1813,39 +1813,43 @@ msgstr "vrijednost %d nije valjana"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "nevaljane dozvole nisu u obliku \"user:$UNAME[:]\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1854,14 +1858,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr "UUID treba normalizaciju"
 
@@ -6040,29 +6044,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7916,24 +7916,13 @@ 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. 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\"."
+"\"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."
 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 61c53ba9..17859471 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:27-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Hungarian <gnome-hu-list at gnome dot org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Hiba: a(z) „%s” időkorlát érvénytelen."
@@ -1905,52 +1905,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "„%s” nem érvényes UUID"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "érvénytelen mező: „%s”"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5968,29 +5972,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7224,13 +7224,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/id.po b/po/id.po
index 8b84d420..996e1d6b 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-12-31 15:54+0700\n"
 "Last-Translator: Andika Triwidada <atriwidada@gnome.org>\n"
 "Language-Team: GNOME Indonesian Translation Team <gnome@i15n.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "nilai %d tidak valid"
@@ -1827,42 +1827,46 @@ msgstr "nilai %d tidak valid"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "URI bukan UTF-8 yang valid"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "izin tak valid \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1871,14 +1875,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6072,29 +6076,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7885,13 +7885,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/it.po b/po/it.po
index 0cbc6847..b8ce357e 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-03-21 14:53+0100\n"
 "Last-Translator: Milo Casagrande <milo@milo.name>\n"
 "Language-Team: Italian <tp@lists.linux.it>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "il valore %d non è valido"
@@ -1876,42 +1876,46 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "l'URI non è UTF-8 valido"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "esecutore «%s» non valido"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1920,14 +1924,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6152,29 +6156,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7920,13 +7920,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ja.po b/po/ja.po
index fde30024..6f08e991 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-08-15 04:44+0000\n"
 "Last-Translator: kemorigu <kemorigu@redhat.com>\n"
 "Language-Team: Japanese <gnome-translation@gnome.gr.jp>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "値 %d は無効です"
@@ -1819,40 +1819,44 @@ msgstr "値 %d は無効です"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr "DHCP オプションは 255 文字より長くすることはできません。"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr "MUD の URL は有効な URL ではありません"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "無効なパーミッション \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "プロパティータイプは '%s' に設定する必要があります"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "スレーブタイプ '%s' の接続には '%s' 設定が必要です"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1861,12 +1865,12 @@ msgstr ""
 "'%s' が設定され、ポートタイプが '%s' のスレーブ接続を検出します。'%s' は "
 "'%s' に設定する必要があります"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6053,29 +6057,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7869,24 +7869,13 @@ 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. 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\"."
+"\"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."
 msgstr ""
 "この設定に関連付けられたゲートウェイ。これは \"address\" も設定されている場合"
 "にのみ意味があります。ゲートウェイの主な目的は、デバイス上の標準デフォルト"
diff --git a/po/ka.po b/po/ka.po
index 36f5c891..d75b2036 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2022-07-16 18:47+0200\n"
 "Last-Translator: Temuri Doghonadze <temuri.doghonadze@gmail.com>\n"
 "Language-Team: Georgian <http://mail.gnome.org/mailman/listinfo/gnome-ge-"
@@ -1139,7 +1139,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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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
@@ -1480,7 +1480,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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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
@@ -1761,7 +1761,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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1770,50 +1770,54 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5706,29 +5710,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6962,13 +6962,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/kn.po b/po/kn.po
index e752035a..467007a8 100644
--- a/po/kn.po
+++ b/po/kn.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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:36-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Kannada <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "'%s' ಮೌಲ್ಯವು ಒಂದು ಸರಿಯಾದ UUID ಆಗಿಲ್ಲ"
@@ -1882,52 +1882,56 @@ msgstr "'%s' ಮೌಲ್ಯವು ಒಂದು ಸರಿಯಾದ UUID ಆಗ�
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s\" ಯು ಒಂದು ಮಾನ್ಯವಾದ UUID ಆಗಿಲ್ಲ"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ಅಮಾನ್ಯವಾದ IPv4 ರೌಟ್ '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "ಗುಣದ ಬಗೆಯನ್ನು '%s' ಗೆ ಹೊಂದಿಸಬೇಕು"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "ಸ್ಲೇವ್‌-ಬಗೆ '%s' ಗಾಗಿ ಸಂಪರ್ಕದಲ್ಲಿ '%s' ಸಿದ್ಧತೆಯ ಅಗತ್ಯವಿರುತ್ತದೆ"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6095,29 +6099,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7351,13 +7351,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ko.po b/po/ko.po
index a97ae2d0..7465656d 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2020-08-23 16:31+0900\n"
 "Last-Translator: Changwoo Ryu <cwryu@debian.org>\n"
 "Language-Team: GNOME Korea <gnome-kr@googlegroups.com>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "%d 값은 유효하지 않습니다"
@@ -1820,40 +1820,44 @@ msgstr "%d 값은 유효하지 않습니다"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr "DHCP 옵션은 255자를 초과할 수 없습니다"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr "MUD URL이 유효한 URL이 아닙니다"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "잘못된 권한 \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "속성 유형을 '%s'(으)로 설정해야 합니다"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1862,13 +1866,13 @@ msgstr ""
 "'%s'(으)로 설정되고 포트 유형이 '%s'인 슬레이브 연결을 감지합니다. '%s'은"
 "(는) '%s'(으)로 설정해야 합니다"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6016,29 +6020,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7759,24 +7759,13 @@ 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. 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\"."
+"\"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."
 msgstr ""
 "이 구성과 연관된 게이트웨이. \"addresses\"도 설정한 경우에만 의미가 있습니"
 "다. 게이트웨이의 주요 목적은 장치에서 표준 기본 경로의 다음 홉을 제어하는 것"
diff --git a/po/ku.po b/po/ku.po
index c66a0827..d7de1314 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2007-01-02 21:47+0000\n"
 "Last-Translator: Erdal Ronahi <erdal.ronahi@gmail.com>\n"
 "Language-Team: Kurdish <ku@li.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Navnîşana IP:"
@@ -1814,52 +1814,56 @@ msgstr "Navnîşana IP:"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Navnîşana IP:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "Navnîşana IP:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5817,29 +5821,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7075,13 +7075,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/lt.po b/po/lt.po
index 92bb6516..bacbd2d0 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:10-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Lietuvių <gnome-lt@lists.akl.lt>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "indeksas „%s“ yra netinkamas"
@@ -1880,52 +1880,56 @@ msgstr "indeksas „%s“ yra netinkamas"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "„%s“ nėra tinkamas UUID"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "netinkamas IPv4 kelias „%s“"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6037,29 +6041,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7293,13 +7293,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/lv.po b/po/lv.po
index a9f8fafa..f07cc15e 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:39-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Latvian <locale@laka.lv>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1835,52 +1835,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "IP adrese:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "IP adrese:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5823,29 +5827,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7079,13 +7079,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/mk.po b/po/mk.po
index 74817c92..a7e19b4d 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2016-04-16 12:56-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Macedonian <ossm-members@hedona.on.net.mk>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1771,50 +1771,54 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5674,29 +5678,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6930,13 +6930,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ml.po b/po/ml.po
index b233cdd0..359dd84f 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:41-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Malayalam <discuss@lists.smc.org.in>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "'%s' സൂചിക ശരിയല്ല"
@@ -1892,52 +1892,56 @@ msgstr "'%s' സൂചിക ശരിയല്ല"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s' ശരിയായ യുയുഐഡിയല്ല"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "തെറ്റായ IPv4 റൂട്ട് '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, fuzzy, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "കണക്ഷനില്‍ '%s' സജ്ജീകരണം ആവശ്യമുണ്ടു്"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6060,29 +6064,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7316,13 +7316,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/mr.po b/po/mr.po
index 8cd05e70..1499f757 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:43-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Marathi <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "मूल्य '%s' वैध UUID नाही"
@@ -1867,52 +1867,56 @@ msgstr "मूल्य '%s' वैध UUID नाही"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s' वैध UUID नाही"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "अवैध IPv4 राउट '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "गुणधर्म प्रकार '%s' करिता सेट केले पाहिजे"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6058,29 +6062,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7314,13 +7314,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/nb.po b/po/nb.po
index c990c33a..fe42dd07 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:43-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Norwegian Bokmål <i18n-nb@lister.ping.uio.no>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1773,51 +1773,55 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Kunne ikke dekode privat nøkkel."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5694,29 +5698,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6950,13 +6950,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ne.po b/po/ne.po
index 6e92ab67..acd4f1b9 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:26-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Nepali <info@mpp.org.np>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1808,52 +1808,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "भीपीएन जडान थप गर्न सकिँदैन"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "भीपीएन जडान पुन: प्राप्ति गर्दा त्रुटि '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5754,29 +5758,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7010,13 +7010,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/nl.po b/po/nl.po
index c5d82a35..49cfc4e2 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2022-03-27 21:08+0200\n"
 "Last-Translator: Nathan Follens <nfollens@gnome.org>\n"
 "Language-Team: Dutch <gnome-nl-list@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "waarde %d is ongeldig"
@@ -1860,50 +1860,54 @@ msgstr "waarde %d is ongeldig"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr "MUD-URL is geen geldige URL"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5910,29 +5914,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7167,13 +7167,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/oc.po b/po/oc.po
index bd00fcab..7e548c1b 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "camp '%s' invalid"
@@ -1853,52 +1853,56 @@ msgstr "camp '%s' invalid"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, fuzzy, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr "Error&nbsp;: %s - connexion introbabla."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "camp '%s' invalid"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "camp '%s' invalid"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5901,29 +5905,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7160,13 +7160,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/or.po b/po/or.po
index c18b9647..bff59077 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:45-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Oriya <oriya-it@googlegroups.com>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "ଅନୁକ୍ରମଣିକା '%s' ଟି ବୈଧ ନୁହଁ"
@@ -1880,52 +1880,56 @@ msgstr "ଅନୁକ୍ରମଣିକା '%s' ଟି ବୈଧ ନୁହଁ"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s' ଟି ଗୋଟିଏ ବୈଧ UUID ନୁହଁ"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ଅବୈଧ IPv4 ପଥ '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, fuzzy, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "ସଂଯୋଗରେ '%s' ବ୍ୟବସ୍ଥାର ଉପସ୍ଥିତି ଆବଶ୍ୟକ"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6046,29 +6050,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7302,13 +7302,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/pa.po b/po/pa.po
index da8b7e67..d7955b43 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-04-19 10:17-0500\n"
 "Last-Translator: A S Alam <alam.yellow@gmail.com>\n"
 "Language-Team: Punjabi <punjabi-users@lists.sf.net>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "ਇੰਡੈਕਸ '%s' ਢੁਕਵਾਂ ਨਹੀਂ ਹੈ"
@@ -1824,52 +1824,56 @@ msgstr "ਇੰਡੈਕਸ '%s' ਢੁਕਵਾਂ ਨਹੀਂ ਹੈ"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s' ਢੁਕਵਾਂ UUID ਨਹੀਂ ਹੈ"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ਅਢੁਕਵਾਂ IPv4 ਰੂਟ '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, fuzzy, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "ਨੂੰ ਸੰਪਰਕ ਵਿੱਚ '%s' ਸੈਟਿੰਗ ਦੀ ਮੌਜੂਦਗੀ ਲੋੜੀਂਦੀ ਹੈ"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5927,29 +5931,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7183,13 +7183,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/pl.po b/po/pl.po
index f029a455..e6aa2bc5 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2020-04-12 11:20+0200\n"
 "Last-Translator: Piotr Drąg <piotrdrag@gmail.com>\n"
 "Language-Team: Polish <community-poland@mozilla.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "wartość %d jest nieprawidłowa"
@@ -1840,42 +1840,46 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "nieprawidłowe uprawnienie „%s”"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1884,13 +1888,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6042,29 +6046,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7306,13 +7306,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/pt.po b/po/pt.po
index 4bfa5cdf..cd02527b 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2020-10-11 21:09+0100\n"
 "Last-Translator: Juliano de Souza Camargo <julianosc@protonmail.com>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1806,52 +1806,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, 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:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5789,29 +5793,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7047,13 +7047,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/pt_BR.po b/po/pt_BR.po
index 255a5f78..effec72c 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2020-03-10 04:12-0300\n"
 "Last-Translator: Rafael Fontenelle <rafaelff@gnome.org>\n"
 "Language-Team: Brazilian Portuguese <gnome-pt_br-list@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "valor %d não é válido"
@@ -1856,42 +1856,46 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "permissão inválida “%s”"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1900,14 +1904,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6133,29 +6137,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7968,13 +7968,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ro.po b/po/ro.po
index 245e8866..02a9ca2e 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2022-03-14 13:23+0000\n"
 "Last-Translator: Sergiu Bivol <sergiu@cip.md>\n"
 "Language-Team: Romanian <kde-i18n-ro@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "valoarea %d nu e validă"
@@ -1807,51 +1807,55 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr "UUID-ul necesită normalizare"
 
@@ -5748,29 +5752,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7004,13 +7004,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ru.po b/po/ru.po
index d5cbb94b..733b899a 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2021-03-31 20:27+0300\n"
 "Last-Translator: Дронова Ю <juliette.tux@gmail.com>\n"
 "Language-Team: Russian <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "значение %d не является действительным"
@@ -1854,40 +1854,44 @@ msgstr "значение %d не является действительным"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr "параметр DHCP не может превышать 255 символов"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr "MUD URL не является допустимым URL"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "недопустимые полномочия не в формате \"user:$UNAME[:]\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "свойство должно иметь тип «%s»"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 "для подчинённого соединения типа  «%s» необходимо определить параметр «%s»"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1896,14 +1900,14 @@ msgstr ""
 "Определить подчинённое соединение с установленным «%s» и типом порта  «%s».  "
 "«%s» должно иметь значение  «%s»."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6122,29 +6126,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -8091,24 +8091,13 @@ 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. 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\"."
+"\"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."
 msgstr ""
 "Шлюз, связанный с этой конфигурацией. Имеет значение только при указанном "
 "параметре \"addresses\". Главное назначение шлюза — контроль следующего "
diff --git a/po/rw.po b/po/rw.po
index f2751a55..60c456e8 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2005-03-31 20:55-0700\n"
 "Last-Translator: Steve Murphy <murf@e-tools.com>\n"
 "Language-Team: Kinyarwanda <translation-team-rw@lists.sourceforge.net>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "(Sibyo"
@@ -1828,52 +1828,56 @@ msgstr "(Sibyo"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "(Sibyo"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "(Sibyo"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5833,29 +5837,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7092,13 +7092,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/sk.po b/po/sk.po
index 8ce1fc90..d3ef9331 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-05-15 16:46+0200\n"
 "Last-Translator: Jose Riha <jose1711@gmail.com>\n"
 "Language-Team: Slovak <sk-i18n@lists.linux.sk>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1834,52 +1834,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "nesprávna adresa IP: %s"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "nesprávna smerová adresa '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5826,29 +5830,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7082,13 +7082,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/sl.po b/po/sl.po
index 4941ccea..233333a5 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:11-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Slovenian GNOME Translation Team <gnome-si@googlegroups.com>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Napaka: vrednost časovne omejitve '%s' ni veljavna."
@@ -1883,52 +1883,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Napaka: ukaz 'nm' '%s' ni veljaven"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "neveljavno polje '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5920,29 +5924,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7176,13 +7176,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/sq.po b/po/sq.po
index b2c81e78..253f1c79 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:11-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Albanian <gnome-albanian-perkthyesit@lists.sourceforge.net>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1799,50 +1799,54 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5726,29 +5730,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6982,13 +6982,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/sr.po b/po/sr.po
index d32e0585..18d7c714 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2010-10-18 16:48+0200\n"
 "Last-Translator: Милош Поповић <gpopac@gmail.com>\n"
 "Language-Team: Serbian <gnom@prevod.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Грешка: није исправна вредност „%s“ за истек времена."
@@ -1852,52 +1852,56 @@ msgstr "Грешка: није исправна вредност „%s“ за �
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "Грешка: „nm“ наредба „'%s“ није исправна."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "неисправно поље „%s“"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5948,29 +5952,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7207,13 +7207,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/sr@latin.po b/po/sr@latin.po
index 061ffe11..9d582837 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2010-10-18 16:48+0200\n"
 "Last-Translator: Miloš Popović <gpopac@gmail.com>\n"
 "Language-Team: Serbian <gnom@prevod.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "Greška: nije ispravna vrednost „%s“ za istek vremena."
@@ -1855,52 +1855,56 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "neispravno polje „%s“"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5952,29 +5956,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7211,13 +7211,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/sv.po b/po/sv.po
index ebc81d8f..eae59716 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-12-04 20:16+0100\n"
 "Last-Translator: Josef Andersson <josef.andersson@fripost.org>\n"
 "Language-Team: Swedish <tp-sv@listor.tp-sv.se>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "mätvärdet %d är inte giltigt"
@@ -1857,42 +1857,46 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, 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:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "URI är inte giltig UTF-8"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ogiltig körare ”%s”"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1901,13 +1905,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6112,29 +6116,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7800,13 +7800,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/ta.po b/po/ta.po
index f2478d69..ecbbbce9 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:21-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Tamil <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "'%s' என்ற மதிப்பு செல்லுபடியாகும் UUID அல்ல"
@@ -1867,40 +1867,44 @@ msgstr "'%s' என்ற மதிப்பு செல்லுபடிய�
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s' என்பது செல்லுபடியாகும் UUID அல்ல"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "தவறான தடம்: %s"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "பண்பு வகை '%s' என அமைக்கப்பட்டிருக்க வேண்டும்"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "ஸ்லேவ் வகை '%s' க்கு இணைப்பில் '%s' அமைப்பு அவசியம்"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1909,14 +1913,14 @@ msgstr ""
 "'%s' அமைக்கப்பட்டுள்ள மற்றும் '%s' வகை துறை வகையைக் கொண்டுள்ள அடிமை இணைப்பைக் "
 "கண்டறியவும். '%s' ஆனது '%s' க்கு அமைக்கப்பட வேண்டும்."
 
-#: src/libnm-core-impl/nm-setting-connection.c:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6082,29 +6086,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7338,13 +7338,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/te.po b/po/te.po
index b87318f7..b5cd7a0c 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:58-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Telugu <kde-i18n-doc@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "విలువ '%s' చెల్లునటువంటి UUID కాదు"
@@ -1869,52 +1869,56 @@ msgstr "విలువ '%s' చెల్లునటువంటి UUID కా
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "'%s' చెల్లునటువంటి UUID కాదు"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "చెల్లని IPv4 రౌట్ '%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "లక్షణం రకం '%s' కు అమర్చాలి"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "స్లేవ్-రకం '%s' కు '%s' అమరిక అనుసంధానం నందు కావాలి"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6060,29 +6064,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7316,13 +7316,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/th.po b/po/th.po
index 9e5b3fc8..40ddd573 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 05:59-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Thai <l10n@opentle.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1834,52 +1834,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "ที่อยู่ไอพี:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "ที่อยู่ไอพี:"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5828,29 +5832,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7084,13 +7084,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/tr.po b/po/tr.po
index 16f232d3..71b768a7 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:01-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Türkçe <gnome-turk@gnome.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, fuzzy, c-format
 msgid "value %d is not valid"
 msgstr "'%s' değeri geçerli bir UUID değil"
@@ -1882,40 +1882,44 @@ 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:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "geçersiz yönlendirme: %s"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, 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:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1924,14 +1928,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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -6118,29 +6122,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7374,13 +7374,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/uk.gmo b/po/uk.gmo
index 1b95d9a4..35596fe4 100644
--- a/po/uk.gmo
+++ b/po/uk.gmo
Binary files differdiff --git a/po/uk.po b/po/uk.po
index 9c75f0a1..ad03dd5e 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2022-07-03 08:50+0300\n"
 "Last-Translator: Yuri Chornoivan <yurchor@ukr.net>\n"
 "Language-Team: Ukrainian <kde-i18n-uk@kde.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "значення %d є некоректним"
@@ -1853,39 +1853,43 @@ msgstr "значення %d є некоректним"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr "Довжина параметра DHCP не може перевищувати 255 символів"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr "Адреса MUD не є коректною адресою"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "некоректний запис прав доступу, не у форматі «користувач:$UNAME[:]»"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "тип властивості має бути встановлено у значення «%s»"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr "тип підлеглого з'єднання «%s» потребує параметра «%s» у з'єднанні"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1894,14 +1898,14 @@ msgstr ""
 "Визначити підлегле з'єднання зі встановленим «%s» і типом порту «%s». «%s» "
 "слід встановити у значення «%s»"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr "UUID потребує нормалізації"
 
@@ -6108,29 +6112,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -8098,24 +8098,13 @@ 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. 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\"."
+"\"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."
 msgstr ""
 "Шлюз, який пов'язано із цими налаштуваннями. Має значення, лише якщо вказано "
 "«addresses». Основним призначенням шлюзу є керування наступним переходом у "
diff --git a/po/vi.po b/po/vi.po
index 7463a767..56a8bd70 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:11-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Vietnamese <vi-VN@googlegroups.com>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1778,52 +1778,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, 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:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, 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:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5719,29 +5723,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -6975,13 +6975,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/wa.po b/po/wa.po
index 2d693ca0..23963fb7 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2004-09-09 10:41+0200\n"
 "Last-Translator: Pablo Saratxaga <pablo@walon.org>\n"
 "Language-Team: Walloon <linux-wa@walon.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1802,51 +1802,55 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "Raloyaedjes rantoele"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5801,29 +5805,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7059,13 +7059,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/zh_CN.po b/po/zh_CN.po
index 7b6d585a..536abd0a 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2021-11-09 20:06+0800\n"
 "Last-Translator: Dingzhong Chen <wsxy162@gmail.com>\n"
 "Language-Team: Chinese - China <i18n-zh@googlegroups.com>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "值 %d 无效"
@@ -1790,39 +1790,43 @@ msgstr "值 %d 无效"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr "DHCP 选项不能多于 255 个字符"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 msgid "MUD URL is not a valid URL"
 msgstr "MUD URL不是一个有效的URL"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "无效的权限，没有以 \"user:$UNAME[:]\" 为格式"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "属性类型应该设置为 \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, c-format
 msgid ""
 "Detect a slave connection with '%s' set and a port type '%s'. '%s' should be "
@@ -1830,12 +1834,12 @@ msgid ""
 msgstr ""
 "检测到设置了 \"%s\" 和端口类型为 \"%s\" 的从连接。\"%s\" 应该设置为 \"%s\""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5939,29 +5943,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7602,24 +7602,13 @@ 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. 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\"."
+"\"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."
 msgstr ""
 "与此配置相关联的网关。只有当 \"addresses\" 也被设置时，这才有意义。网关的主要"
 "目的是控制设备上标准默认路由的下一跳。因此，网关属性与 \"never-default\" 冲"
diff --git a/po/zh_HK.po b/po/zh_HK.po
index 499d6ea2..b01f7d65 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2017-04-21 06:26-0400\n"
 "Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
 "Language-Team: Chinese (Hong Kong) <community@linuxhall.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr ""
@@ -1837,52 +1837,56 @@ msgstr ""
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, c-format
 msgid "value %u is not a valid combination of MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "IP 位址："
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "IP 位址："
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, c-format
 msgid "slave-type '%s' requires a '%s' setting in the connection"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5850,29 +5854,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7106,13 +7106,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175
diff --git a/po/zh_TW.po b/po/zh_TW.po
index 307a5597..2b56f90d 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-26 16:42+0200\n"
+"POT-Creation-Date: 2022-08-11 16:06-0300\n"
 "PO-Revision-Date: 2019-06-28 19:18+0800\n"
 "Last-Translator: Hsiu-Ming Chang <cges30901@gmail.com>\n"
 "Language-Team: Traditional Chinese <zh@li.org>\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:1516
+#: src/libnm-core-impl/nm-setting-connection.c:1530
 #: 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:1454
+#: src/libnm-core-impl/nm-setting-connection.c:1468
 #: 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:1440
+#: src/libnm-core-impl/nm-setting-connection.c:1454
 #, c-format
 msgid "value %d is not valid"
 msgstr "值 %d 無效"
@@ -1811,54 +1811,58 @@ msgstr "值 %d 無效"
 msgid "\"disabled\" flag cannot be combined with other MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1409
+#: 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
 msgid "cannot set both \"signal\" and \"fullmesh\" MPTCP flags"
 msgstr ""
 
-#: src/libnm-core-impl/nm-setting-connection.c:1421
+#: src/libnm-core-impl/nm-setting-connection.c:1435
 #, 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:1468
+#: src/libnm-core-impl/nm-setting-connection.c:1482
 #, fuzzy
 msgid "DHCP option cannot be longer than 255 characters"
 msgstr "接口名稱超過15個字符"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1479
+#: src/libnm-core-impl/nm-setting-connection.c:1493
 #, fuzzy
 msgid "MUD URL is not a valid URL"
 msgstr "URI無效UTF-8"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1499
+#: src/libnm-core-impl/nm-setting-connection.c:1513
 #, fuzzy
 msgid "invalid permissions not in format \"user:$UNAME[:]\""
 msgstr "無效的權限「%s」"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1528
+#: src/libnm-core-impl/nm-setting-connection.c:1542
 #, c-format
 msgid "property type should be set to '%s'"
 msgstr "屬性類型應設置為'%s'"
 
-#: src/libnm-core-impl/nm-setting-connection.c:1546
+#: src/libnm-core-impl/nm-setting-connection.c:1560
 #, 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:1557
+#: src/libnm-core-impl/nm-setting-connection.c:1571
 #, 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:1583
+#: src/libnm-core-impl/nm-setting-connection.c:1597
 #, 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:1600
+#: src/libnm-core-impl/nm-setting-connection.c:1614
 msgid "UUID needs normalization"
 msgstr ""
 
@@ -5954,29 +5958,25 @@ 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 \"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)."
+"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)."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:18
@@ -7501,13 +7501,11 @@ 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. 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\"."
+"\"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."
 msgstr ""
 
 #: src/libnmc-setting/settings-docs.h.in:175