From 964ae8cc391520440cf5aa13e2b9cc34850ea6c2 Mon Sep 17 00:00:00 2001
From: Michael Biebl If left unspecified, the default value is 3 tries before failing the connection.
If configured explicitly to 0, the MTU is not reconfigured during device activation unless it is required due to IPv6 constraints. If left unspecified, a DHCP/IPv6 SLAAC provided value is used or the MTU is left unspecified on activation. If left unspecified, the default value
"
@@ -1164,6 +1180,8 @@ enable=env:TAG1
be used to negate the match. Note that if one except-predicate
matches, the entire configuration will be disabled.
In other words, a except predicate always wins over other predicates.
+ If the setting only consists of "except:" matches and none of the
+ negative conditions are satisfied, the configuration is still enabled.
+
+
+802-1x.auth-timeout
+
+
+
+cdma.mtu
+
connection.auth-retries
@@ -644,6 +652,10 @@ ipv6.ip6-privacy=0
+
+
+gsm.mtu
+
@@ -742,6 +754,10 @@ ipv6.ip6-privacy=0
infiniband.mtu
+optional" will be used.
+
+wifi.wake-on-wlan
+
# enable the configuration either when the environment variable
@@ -1351,10 +1369,21 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
dhcp-plugin:DHCP
Match the configured DHCP plugin "main.dhcp".
+
except:SPEC
Negative match of a device. SPEC must be explicitly qualified with
+
Negative match of a device. SPEC must be explicitly qualified with
a prefix such as interface-name:. A negative match has higher priority then the positive
- matches above.
If there is a list consisting only of negative matches, the behavior is the same as if there
+ is also match-all. That means, if none of all the negative matches is satisfied, the overall result is
+ still a positive match. That means, "except:interface-name:eth0" is the same as
+ "*,except:interface-name:eth0".
SPEC[,;]SPEC