From 1372848511cb896b80b51ed1a3e9606bd9816631 Mon Sep 17 00:00:00 2001
From: Michael Biebl
reapply
+ The connection was reapplied on the device. +
diff --git a/docs/api/html/NetworkManager-wait-online.service.html b/docs/api/html/NetworkManager-wait-online.service.html index 76b703a0..c951c7b6 100644 --- a/docs/api/html/NetworkManager-wait-online.service.html +++ b/docs/api/html/NetworkManager-wait-online.service.html @@ -24,132 +24,102 @@
NetworkManager-wait-online.service-NetworkManager-wait-online.service — Wait for network to come online +NetworkManager-wait-online.service — Wait for the network to come online |
- NetworkManager-wait-online.service delays network-online.target until network
- is ready.
+ The NetworkManager-wait-online service is a oneshot
+ systemd service that delays reaching the network-online target until
+ NetworkManager reports that the startup is completed on the D-Bus.
- The systemd target network-online.target acts as a synchronization point
- for services to start after network is configured. Such services should
- order themselves After=network-online.target
- (and never After=NetworkManager-wait-online.service).
- NetworkManager-wait-online.service is a one-shot service
- that itself is ordered Before=network-online.target
- and this way delays the target until the network is configured.
+ When the system boots, for example, remote mounts defined in /etc/fstab,
+ require that the network is up. For this, these systemd units contain the
+ After=network-online.target setting to order themselves after this
+ target. NetworkManager-wait-online ensures that the
+ network-online target is reached only after the network is available.
- NetworkManager-wait-online.service itself is almost not configurable
- itself. Instead the connection profiles and configuration in NetworkManager affects
- the behavior.
+ Optimally, all services on the host react dynamically to network changes and systemd
+ services do not need to be configured to start after reaching the
+ network-online target. In this case,
+ NetworkManager-wait-online.service has no effect and does not delay
+ the boot time. On the other hand, if you encounter a long boot time due to the delay
+ of NetworkManager-wait-online, investigate the services that require
+ network access and fix them.
- In the best case, all services on the system can react to networking changes dynamically and
- no service orders itself after network-online.target. That way,
- NetworkManager-wait-online.service has no effect and, for example,
- does not delay the boot. That means, if the problem is a long boot time related to
- NetworkManager-wait-online.service, a possible solution is to
- investigate the services that claim to require network and fix those.
+ Except for the time out value in the NetworkManager-wait-online.service
+ unit, you cannot configure this service. Instead, settings in NetworkManager and the
+ connection profiles affect the behavior:
- For services that require network configured,
- NetworkManager-wait-online.service is the default implementation
- provided by NetworkManager to delay the target. But it does nothing magical. With
- special requirements, it may be sensible to disable NetworkManager-wait-online.service
- and replace it with a similar service that better implements the requirement.
-
- NetworkManager-wait-online.service blocks until
- NetworkManager logs "startup complete" and announces startup complete
- on D-Bus. How long that takes depends on the network
- and the NetworkManager configuration. If it takes longer than expected, then
- the reasons need to be investigated in NetworkManager.
-
- There are various reasons what affects NetworkManager reaching "startup complete"
- and how long NetworkManager-wait-online.service blocks.
-
- In general, startup complete is not reached as long as NetworkManager is busy
- activating a device and as long as there are profiles in activating state.
- During boot, NetworkManager starts autoactivating
- suitable profiles that are configured to autoconnect. If activation fails,
- NetworkManager might retry right away (depending on connection.autoconnect-retries
- setting). While trying and retrying, NetworkManager is busy until all
- profiles and devices either reached an activated or disconnected state
- and no further events are expected.
-
connection.autoconnect=yes setting. If activation fails,
+ NetworkManager retries the activation depending on the value of the
+ connection.autoconnect-retries setting.
+
-
+ NetworkManager reports startup complete when all profiles and devices are either + activated or in a disconnect state and no further events are expected. + +
- Basically, as long as there are devices and connections in activating
- state visible with nmcli device and nmcli connection,
- startup is still pending.
-
+ The ipv4.may-fail and ipv6.may-fail settings
+ control this behavior. Additionally, the following settings influence when the
+ two address families complete: ipv4.required-timeout,
+ ipv6.required-timeout, ipv4.dhcp-timeout,
+ and ipv6.ra-timeout. For details, see
+ nm-settings-nmcli(5).
+
- When a device reaches activated state, depends on its configuration.
- For example, with a profile with both IPv4 and IPv6 addressing
- enabled, the device is possibly considered fully activated when
- either of the address families is ready. This can be controlled with the
- ipv4.may-fail and ipv6.may-fail
- settings, to indicate that the address family is required.
- There are also ipv4.required-timeout and ipv6.required-timeout
- settings which affect how long to wait for an address family.
- Likewise, properties like ipv4.dhcp-timeout and
- ipv6.ra-timeout affect how long NetworkManager
- will try the IP configuration before giving up.
-
- For example, a bridge or bond profile cannot do IP configuration
- without ports. When booting with such profiles that autoactivate
- without ports, NetworkManager-wait-online.service blocks until timeout.
- This is a configuration error.
-
NetworkManager-wait-online blocks until the service reaches
+ its timeout value.
+
- Dispatcher scripts for the "pre-up" event run at a late stage during activation - of a profile. These scripts block the activation for when NetworkManager considers - the profile fully activated. - See also NetworkManager-dispatcher(8) - for details. -
pre-up event run at a late stage
+ during activation of a profile. These scripts block the activation for when
+ NetworkManager considers the profile fully activated. For details, see
+ NetworkManager-dispatcher(8).
+
- The connection property connection.wait-activation-delay also
- adds an additional delay during activation and delays startup complete. This is to
- workaround certain cases where a device is known to not be ready for a certain
- amount of time.
-
connection.wait-activation-delay adds an additional
+ delay during activation and delays startup complete. This setting works around
+ certain cases where a device is known to not be ready for a certain amount of time.
+
- The property connection.wait-device-timeout of the connection
- profiles waits until the waited devices appear. This is useful if the driver
- takes a longer time to detect the networking interfaces. Similar with the
- connection.gateway-ping-timeout property.
-
connection.wait-device-timeout in the connection
+ profiles cause a delay until the waiting devices appear. This is useful if the
+ driver takes a longer time to detect the networking interfaces. This setting is
+ similar to the connection.gateway-ping-timeout property.
+
- With Wi-Fi devices, NetworkManager needs to wait for the first scan - result to know which networks might be available. That always adds a delay. -
- With ethernet devices, NetworkManager waits for carrier until the
- configurable [device*].carrier-timeout is reached.
- This is because some devices take a long time to detect carrier
- and it means to boot with cable unplugged, will unnecessarily delay
- NetworkManager-wait-online.service.
-
[device*].carrier-timeout is reached. This is because some
+ devices take a long time to detect the carrier. Consequently, booting with cable
+ unplugged, unnecessarily delays NetworkManager-wait-online.service.
+
-
-
- NetworkManager-wait-online.service internally uses
- nm-online.
-
network-online.target description in systemd.special(7)
loopback.mtu
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.
sriov.autoprobe-drivers
If left unspecified, drivers are autoprobed when the SR-IOV VF gets created.
--print-config
- Print the NetworkManager configuration to stdout and exit. -
+ Print the NetworkManager configuration to stdout and exit. See + NetworkManager.conf(5). + This does not include connection profiles. View them with nmcli connection. +
++ This reads configuration files from disk. If NetworkManager is currently running, + make sure that it has the same configuration loaded. +
++FwMark readable u ++
+The fwmark value to assign to tunnel packets. This property applies only to +VTI tunnels. +
+Flags readable u diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html index c706d1ff..2aef5cdb 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Infiniband.html @@ -7,7 +7,7 @@ - + @@ -21,7 +21,7 @@- + diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html new file mode 100644 index 00000000..c522f1f7 --- /dev/null +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Loopback.html @@ -0,0 +1,45 @@ + + + + +org.freedesktop.NetworkManager.Device.Loopback: NetworkManager Reference Manual + + + + + + + + + ++
+ +Top + ++ + + + + + + ++ + + \ No newline at end of file diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html index 8d85d33a..68e709aa 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Lowpan.html @@ -6,7 +6,7 @@ - + @@ -20,7 +20,7 @@- + @@ -33,7 +33,7 @@ -Properties
+Properties
HwAddress readable s Parent readable o diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html index 795aee21..9f868062 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macsec.html @@ -33,7 +33,7 @@ -Properties
+Properties
Parent readable o Sci readable t diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html index fcbb003c..b7ffeaf3 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Macvlan.html @@ -33,7 +33,7 @@ -Properties
+Properties
Parent readable o Mode readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html index 4b6cc204..b55163c1 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Modem.html @@ -33,7 +33,7 @@ -Properties
+Properties
ModemCapabilities readable u CurrentCapabilities readable u diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html index 2f71abd8..631e01b3 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OlpcMesh.html @@ -33,7 +33,7 @@ -Properties
+Properties
HwAddress readable s Companion readable o diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html index 46b3fbd4..571a45e6 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsBridge.html @@ -33,7 +33,7 @@ -Properties
+Properties
Slaves readable aodiff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html index 08cf13ba..4dcf9283 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.OvsPort.html @@ -33,7 +33,7 @@ -Properties
+Properties
Slaves readable aodiff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html index 5864fd40..8340f542 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Team.html @@ -33,7 +33,7 @@ -Properties
+Properties
HwAddress readable s Carrier readable b diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html index 8c05cf5c..4ff42e7a 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Tun.html @@ -33,7 +33,7 @@ -Properties
+Properties
Owner readable x Group readable x diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html index 46b788f2..d2ba1876 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Veth.html @@ -33,7 +33,7 @@ -Properties
+Properties
Peer readable odiff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html index a55b8250..0a17c6ef 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vlan.html @@ -33,7 +33,7 @@ -Properties
+Properties
HwAddress readable s Carrier readable b diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html index 88e848a0..a37962e2 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vrf.html @@ -33,7 +33,7 @@ -Properties
+Properties
Table readable udiff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html index 9349aa4c..38f938f8 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Vxlan.html @@ -33,7 +33,7 @@ -Properties
+Properties
Parent readable o HwAddress readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html index 2ef395cf..4f99d38e 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WifiP2P.html @@ -41,14 +41,14 @@-Properties
+Properties
HwAddress readable s Peers readable ao diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html index 60ad16dc..ab48943e 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.WireGuard.html @@ -33,7 +33,7 @@ -Properties
+Properties
PublicKey readable ay ListenPort readable q diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html index e62fe697..94fcf349 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wired.html @@ -33,7 +33,7 @@ -Properties
+Properties
HwAddress readable s PermHwAddress readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html index 39d0305d..ba1206a8 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wireless.html @@ -42,14 +42,14 @@-Properties
+Properties
HwAddress readable s PermHwAddress readable s diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html index 4415fe36..28bba258 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.Wpan.html @@ -33,7 +33,7 @@ -Properties
+Properties
HwAddress readable sdiff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html index f5026a1f..8da3cea1 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.Device.html @@ -130,8 +130,8 @@ settings-connection, just like updating the settings-connection can make them different.-Since 1.42, 1.40.10, "preserve-external-ip" flag (0x1) is supported to not -remove externally added IP addresses and routes on the device during reapply. +Since 1.42, "preserve-external-ip" flag (0x1) is supported to not remove +externally added IP addresses and routes on the device during reapply.
diff --git a/docs/api/html/gdbus-org.freedesktop.NetworkManager.html b/docs/api/html/gdbus-org.freedesktop.NetworkManager.html index 96ae6b68..57560d60 100644 --- a/docs/api/html/gdbus-org.freedesktop.NetworkManager.html +++ b/docs/api/html/gdbus-org.freedesktop.NetworkManager.html @@ -108,6 +108,7 @@ ActivatingConnection readable o Startup readable b Version readable s +VersionInfo readable au Capabilities readable au State readable u Connectivity readable u @@ -1057,6 +1058,28 @@ NetworkManager version.
++The "VersionInfo" property
++VersionInfo readable au +++NetworkManager version and capabilities. +
++The first element in the array is the NM_VERSION of the daemon. It is a binary representation +of the "Version" and can be compared numerically. The version is encoded as +"(major << 16 | minor << 8 | micro)". +
++The following elements are a bitfield of static capabilities of the daemon. See +#NMVersionInfoCapability for the available capability numbers. +
++Since: 1.42 +
+
+The "Capabilities" property
Capabilities readable au diff --git a/docs/api/html/index.html b/docs/api/html/index.html index d4b84edd..f9ac99a9 100644 --- a/docs/api/html/index.html +++ b/docs/api/html/index.html @@ -16,7 +16,7 @@
NetworkManager Reference Manual
@@ -982,21 +990,21 @@- for NetworkManager 1.40.12 + for NetworkManager 1.42.0 The latest version of this documentation can be found on-line at https://networkmanager.dev/docs/api/latest/. @@ -79,7 +79,7 @@ NetworkManager-dispatcher — Dispatch user scripts for NetworkManager
-NetworkManager-wait-online.service — Wait for network to come online +NetworkManager-wait-online.service — Wait for the network to come online nmcli — command-line tool for controlling NetworkManager @@ -120,160 +120,166 @@ Configuration Settings
- -connection — General Connection Profile Settings +connection — General Connection Profile Settings
- -6lowpan — 6LoWPAN Settings +6lowpan — 6LoWPAN Settings
- -802-1x — IEEE 802.1x Authentication Settings +802-1x — IEEE 802.1x Authentication Settings
- -adsl — ADSL Settings +adsl — ADSL Settings
- -bluetooth — Bluetooth Settings +bluetooth — Bluetooth Settings
- -bond — Bonding Settings +bond — Bonding Settings
- -bridge — Bridging Settings +bridge — Bridging Settings
- -bridge-port — Bridge Port Settings +bridge-port — Bridge Port Settings
- -cdma — CDMA-based Mobile Broadband Settings +cdma — CDMA-based Mobile Broadband Settings
- -dcb — Data Center Bridging Settings +dcb — Data Center Bridging Settings
- -dummy — Dummy Link Settings +dummy — Dummy Link Settings
- -ethtool — Ethtool Ethernet Settings +ethtool — Ethtool Ethernet Settings
- -generic — Generic Link Settings +generic — Generic Link Settings
- -gsm — GSM-based Mobile Broadband Settings +gsm — GSM-based Mobile Broadband Settings
- -infiniband — Infiniband Settings +infiniband — Infiniband Settings
- -ipv4 — IPv4 Settings +ipv4 — IPv4 Settings
- -ipv6 — IPv6 Settings +ipv6 — IPv6 Settings
- -ip-tunnel — IP Tunneling Settings +ip-tunnel — IP Tunneling Settings
- -macsec — MACSec Settings +macsec — MACSec Settings
- -macvlan — MAC VLAN Settings +macvlan — MAC VLAN Settings
- -match — Match settings +match — Match settings
- -802-11-olpc-mesh — OLPC Wireless Mesh Settings +802-11-olpc-mesh — OLPC Wireless Mesh Settings
- -ovs-bridge — OvsBridge Link Settings +ovs-bridge — OvsBridge Link Settings
- -ovs-dpdk — OvsDpdk Link Settings +ovs-dpdk — OvsDpdk Link Settings
- -ovs-interface — Open vSwitch Interface Settings +ovs-interface — Open vSwitch Interface Settings
- -ovs-patch — OvsPatch Link Settings +ovs-patch — OvsPatch Link Settings
- -ovs-port — OvsPort Link Settings +ovs-port — OvsPort Link Settings
- -ppp — Point-to-Point Protocol Settings +ppp — Point-to-Point Protocol Settings
- -pppoe — PPP-over-Ethernet Settings +pppoe — PPP-over-Ethernet Settings
- -proxy — WWW Proxy Settings +proxy — WWW Proxy Settings
- -serial — Serial Link Settings +serial — Serial Link Settings
- -sriov — SR-IOV settings +sriov — SR-IOV settings
- -tc — Linux Traffic Control Settings +tc — Linux Traffic Control Settings
- -team — Teaming Settings +team — Teaming Settings
- -team-port — Team Port Settings +team-port — Team Port Settings
- -tun — Tunnel Settings +tun — Tunnel Settings
- -user — General User Profile Settings +user — General User Profile Settings
- -vlan — VLAN Settings +vlan — VLAN Settings
- -vpn — VPN Settings +vpn — VPN Settings
- -vrf — VRF settings +vrf — VRF settings
- -vxlan — VXLAN Settings +vxlan — VXLAN Settings
- -wifi-p2p — Wi-Fi P2P Settings +wifi-p2p — Wi-Fi P2P Settings
- -wimax — WiMax Settings +wimax — WiMax Settings
- -802-3-ethernet — Wired Ethernet Settings +802-3-ethernet — Wired Ethernet Settings
- -wireguard — WireGuard Settings +wireguard — WireGuard Settings
- -802-11-wireless — Wi-Fi Settings +802-11-wireless — Wi-Fi Settings
- -802-11-wireless-security — Wi-Fi Security Settings +802-11-wireless-security — Wi-Fi Security Settings
- -wpan — IEEE 802.15.4 (WPAN) MAC Settings +wpan — IEEE 802.15.4 (WPAN) MAC Settings
- -bond-port — Bond Port Settings +bond-port — Bond Port Settings
- -hostname — Hostname settings +hostname — Hostname settings
- -ovs-external-ids — OVS External IDs Settings +loopback — Loopback Link Settings
- -veth — Veth Settings +ovs-external-ids — OVS External IDs Settings +
+- +ovs-other-config — OVS Other Config Settings +
+- +veth — Veth Settings
Secret flag types @@ -333,6 +339,9 @@ org.freedesktop.NetworkManager.Device.Infiniband — Infiniband Device.+org.freedesktop.NetworkManager.Device.Loopback — Loopback Device. + +org.freedesktop.NetworkManager.Device.Lowpan — 6LoWPAN Device. diff --git a/docs/api/html/ix01.html b/docs/api/html/ix01.html index d1897057..01dd7cd9 100644 --- a/docs/api/html/ix01.html +++ b/docs/api/html/ix01.html @@ -112,10 +112,12 @@ org.freedesktop.NetworkManager.Device.IPTunnel:EncapsulationLimit, The "EncapsulationLimit" property -org.freedesktop.NetworkManager.Device.IPTunnel:Flags, The "Flags" property + org.freedesktop.NetworkManager.Device.IPTunnel:Flags, The "Flags" property org.freedesktop.NetworkManager.Device.IPTunnel:FlowLabel, The "FlowLabel" property +org.freedesktop.NetworkManager.Device.IPTunnel:FwMark, The "FwMark" property + org.freedesktop.NetworkManager.Device.IPTunnel:InputKey, The "InputKey" property org.freedesktop.NetworkManager.Device.IPTunnel:Local, The "Local" property @@ -134,81 +136,83 @@ org.freedesktop.NetworkManager.Device.IPTunnel:Ttl, The "Ttl" property -org.freedesktop.NetworkManager.Device.Lowpan, org.freedesktop.NetworkManager.Device.Lowpan + org.freedesktop.NetworkManager.Device.Loopback, org.freedesktop.NetworkManager.Device.Loopback + +org.freedesktop.NetworkManager.Device.Lowpan, org.freedesktop.NetworkManager.Device.Lowpan -org.freedesktop.NetworkManager.Device.Lowpan:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.Lowpan:HwAddress, The "HwAddress" property -org.freedesktop.NetworkManager.Device.Lowpan:Parent, The "Parent" property + org.freedesktop.NetworkManager.Device.Lowpan:Parent, The "Parent" property -org.freedesktop.NetworkManager.Device.Macsec, org.freedesktop.NetworkManager.Device.Macsec + org.freedesktop.NetworkManager.Device.Macsec, org.freedesktop.NetworkManager.Device.Macsec -org.freedesktop.NetworkManager.Device.Macsec:CipherSuite, The "CipherSuite" property + org.freedesktop.NetworkManager.Device.Macsec:CipherSuite, The "CipherSuite" property -org.freedesktop.NetworkManager.Device.Macsec:EncodingSa, The "EncodingSa" property + org.freedesktop.NetworkManager.Device.Macsec:EncodingSa, The "EncodingSa" property -org.freedesktop.NetworkManager.Device.Macsec:Encrypt, The "Encrypt" property + org.freedesktop.NetworkManager.Device.Macsec:Encrypt, The "Encrypt" property -org.freedesktop.NetworkManager.Device.Macsec:Es, The "Es" property + org.freedesktop.NetworkManager.Device.Macsec:Es, The "Es" property -org.freedesktop.NetworkManager.Device.Macsec:IcvLength, The "IcvLength" property + org.freedesktop.NetworkManager.Device.Macsec:IcvLength, The "IcvLength" property -org.freedesktop.NetworkManager.Device.Macsec:IncludeSci, The "IncludeSci" property + org.freedesktop.NetworkManager.Device.Macsec:IncludeSci, The "IncludeSci" property -org.freedesktop.NetworkManager.Device.Macsec:Parent, The "Parent" property + org.freedesktop.NetworkManager.Device.Macsec:Parent, The "Parent" property -org.freedesktop.NetworkManager.Device.Macsec:Protect, The "Protect" property + org.freedesktop.NetworkManager.Device.Macsec:Protect, The "Protect" property -org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect, The "ReplayProtect" property + org.freedesktop.NetworkManager.Device.Macsec:ReplayProtect, The "ReplayProtect" property -org.freedesktop.NetworkManager.Device.Macsec:Scb, The "Scb" property + org.freedesktop.NetworkManager.Device.Macsec:Scb, The "Scb" property -org.freedesktop.NetworkManager.Device.Macsec:Sci, The "Sci" property + org.freedesktop.NetworkManager.Device.Macsec:Sci, The "Sci" property -org.freedesktop.NetworkManager.Device.Macsec:Validation, The "Validation" property + org.freedesktop.NetworkManager.Device.Macsec:Validation, The "Validation" property -org.freedesktop.NetworkManager.Device.Macsec:Window, The "Window" property + org.freedesktop.NetworkManager.Device.Macsec:Window, The "Window" property -org.freedesktop.NetworkManager.Device.Macvlan, org.freedesktop.NetworkManager.Device.Macvlan + org.freedesktop.NetworkManager.Device.Macvlan, org.freedesktop.NetworkManager.Device.Macvlan -org.freedesktop.NetworkManager.Device.Macvlan:Mode, The "Mode" property + org.freedesktop.NetworkManager.Device.Macvlan:Mode, The "Mode" property -org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc, The "NoPromisc" property + org.freedesktop.NetworkManager.Device.Macvlan:NoPromisc, The "NoPromisc" property -org.freedesktop.NetworkManager.Device.Macvlan:Parent, The "Parent" property + org.freedesktop.NetworkManager.Device.Macvlan:Parent, The "Parent" property -org.freedesktop.NetworkManager.Device.Macvlan:Tap, The "Tap" property + org.freedesktop.NetworkManager.Device.Macvlan:Tap, The "Tap" property -org.freedesktop.NetworkManager.Device.Modem, org.freedesktop.NetworkManager.Device.Modem + org.freedesktop.NetworkManager.Device.Modem, org.freedesktop.NetworkManager.Device.Modem -org.freedesktop.NetworkManager.Device.Modem:Apn, The "Apn" property + org.freedesktop.NetworkManager.Device.Modem:Apn, The "Apn" property -org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities, The "CurrentCapabilities" property + org.freedesktop.NetworkManager.Device.Modem:CurrentCapabilities, The "CurrentCapabilities" property -org.freedesktop.NetworkManager.Device.Modem:DeviceId, The "DeviceId" property + org.freedesktop.NetworkManager.Device.Modem:DeviceId, The "DeviceId" property -org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities, The "ModemCapabilities" property + org.freedesktop.NetworkManager.Device.Modem:ModemCapabilities, The "ModemCapabilities" property -org.freedesktop.NetworkManager.Device.Modem:OperatorCode, The "OperatorCode" property + org.freedesktop.NetworkManager.Device.Modem:OperatorCode, The "OperatorCode" property -org.freedesktop.NetworkManager.Device.OlpcMesh, org.freedesktop.NetworkManager.Device.OlpcMesh + org.freedesktop.NetworkManager.Device.OlpcMesh, org.freedesktop.NetworkManager.Device.OlpcMesh -org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel, The "ActiveChannel" property + org.freedesktop.NetworkManager.Device.OlpcMesh:ActiveChannel, The "ActiveChannel" property -org.freedesktop.NetworkManager.Device.OlpcMesh:Companion, The "Companion" property + org.freedesktop.NetworkManager.Device.OlpcMesh:Companion, The "Companion" property -org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.OlpcMesh:HwAddress, The "HwAddress" property -org.freedesktop.NetworkManager.Device.OvsBridge, org.freedesktop.NetworkManager.Device.OvsBridge + org.freedesktop.NetworkManager.Device.OvsBridge, org.freedesktop.NetworkManager.Device.OvsBridge -org.freedesktop.NetworkManager.Device.OvsBridge:Slaves, The "Slaves" property + org.freedesktop.NetworkManager.Device.OvsBridge:Slaves, The "Slaves" property -org.freedesktop.NetworkManager.Device.OvsInterface, org.freedesktop.NetworkManager.Device.OvsInterface + org.freedesktop.NetworkManager.Device.OvsInterface, org.freedesktop.NetworkManager.Device.OvsInterface -org.freedesktop.NetworkManager.Device.OvsPort, org.freedesktop.NetworkManager.Device.OvsPort + org.freedesktop.NetworkManager.Device.OvsPort, org.freedesktop.NetworkManager.Device.OvsPort -org.freedesktop.NetworkManager.Device.OvsPort:Slaves, The "Slaves" property + org.freedesktop.NetworkManager.Device.OvsPort:Slaves, The "Slaves" property -org.freedesktop.NetworkManager.Device.Ppp, org.freedesktop.NetworkManager.Device.Ppp + org.freedesktop.NetworkManager.Device.Ppp, org.freedesktop.NetworkManager.Device.Ppp org.freedesktop.NetworkManager.Device.Reapply(), The Reapply() method @@ -220,97 +224,97 @@org.freedesktop.NetworkManager.Device.Statistics:TxBytes, The "TxBytes" property -org.freedesktop.NetworkManager.Device.Team, org.freedesktop.NetworkManager.Device.Team + org.freedesktop.NetworkManager.Device.Team, org.freedesktop.NetworkManager.Device.Team -org.freedesktop.NetworkManager.Device.Team:Carrier, The "Carrier" property + org.freedesktop.NetworkManager.Device.Team:Carrier, The "Carrier" property -org.freedesktop.NetworkManager.Device.Team:Config, The "Config" property + org.freedesktop.NetworkManager.Device.Team:Config, The "Config" property -org.freedesktop.NetworkManager.Device.Team:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.Team:HwAddress, The "HwAddress" property -org.freedesktop.NetworkManager.Device.Team:Slaves, The "Slaves" property + org.freedesktop.NetworkManager.Device.Team:Slaves, The "Slaves" property -org.freedesktop.NetworkManager.Device.Tun, org.freedesktop.NetworkManager.Device.Tun + org.freedesktop.NetworkManager.Device.Tun, org.freedesktop.NetworkManager.Device.Tun -org.freedesktop.NetworkManager.Device.Tun:Group, The "Group" property + org.freedesktop.NetworkManager.Device.Tun:Group, The "Group" property -org.freedesktop.NetworkManager.Device.Tun:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.Tun:HwAddress, The "HwAddress" property -org.freedesktop.NetworkManager.Device.Tun:Mode, The "Mode" property + org.freedesktop.NetworkManager.Device.Tun:Mode, The "Mode" property -org.freedesktop.NetworkManager.Device.Tun:MultiQueue, The "MultiQueue" property + org.freedesktop.NetworkManager.Device.Tun:MultiQueue, The "MultiQueue" property -org.freedesktop.NetworkManager.Device.Tun:NoPi, The "NoPi" property + org.freedesktop.NetworkManager.Device.Tun:NoPi, The "NoPi" property -org.freedesktop.NetworkManager.Device.Tun:Owner, The "Owner" property + org.freedesktop.NetworkManager.Device.Tun:Owner, The "Owner" property -org.freedesktop.NetworkManager.Device.Tun:VnetHdr, The "VnetHdr" property + org.freedesktop.NetworkManager.Device.Tun:VnetHdr, The "VnetHdr" property -org.freedesktop.NetworkManager.Device.Veth, org.freedesktop.NetworkManager.Device.Veth + org.freedesktop.NetworkManager.Device.Veth, org.freedesktop.NetworkManager.Device.Veth -org.freedesktop.NetworkManager.Device.Veth:Peer, The "Peer" property + org.freedesktop.NetworkManager.Device.Veth:Peer, The "Peer" property -org.freedesktop.NetworkManager.Device.Vlan, org.freedesktop.NetworkManager.Device.Vlan + org.freedesktop.NetworkManager.Device.Vlan, org.freedesktop.NetworkManager.Device.Vlan -org.freedesktop.NetworkManager.Device.Vlan:Carrier, The "Carrier" property + org.freedesktop.NetworkManager.Device.Vlan:Carrier, The "Carrier" property -org.freedesktop.NetworkManager.Device.Vlan:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.Vlan:HwAddress, The "HwAddress" property -org.freedesktop.NetworkManager.Device.Vlan:Parent, The "Parent" property + org.freedesktop.NetworkManager.Device.Vlan:Parent, The "Parent" property -org.freedesktop.NetworkManager.Device.Vlan:VlanId, The "VlanId" property + org.freedesktop.NetworkManager.Device.Vlan:VlanId, The "VlanId" property -org.freedesktop.NetworkManager.Device.Vrf, org.freedesktop.NetworkManager.Device.Vrf + org.freedesktop.NetworkManager.Device.Vrf, org.freedesktop.NetworkManager.Device.Vrf -org.freedesktop.NetworkManager.Device.Vrf:Table, The "Table" property + org.freedesktop.NetworkManager.Device.Vrf:Table, The "Table" property -org.freedesktop.NetworkManager.Device.Vxlan, org.freedesktop.NetworkManager.Device.Vxlan + org.freedesktop.NetworkManager.Device.Vxlan, org.freedesktop.NetworkManager.Device.Vxlan -org.freedesktop.NetworkManager.Device.Vxlan:Ageing, The "Ageing" property + org.freedesktop.NetworkManager.Device.Vxlan:Ageing, The "Ageing" property -org.freedesktop.NetworkManager.Device.Vxlan:DstPort, The "DstPort" property + org.freedesktop.NetworkManager.Device.Vxlan:DstPort, The "DstPort" property -org.freedesktop.NetworkManager.Device.Vxlan:Group, The "Group" property + org.freedesktop.NetworkManager.Device.Vxlan:Group, The "Group" property -org.freedesktop.NetworkManager.Device.Vxlan:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.Vxlan:HwAddress, The "HwAddress" property -org.freedesktop.NetworkManager.Device.Vxlan:Id, The "Id" property + org.freedesktop.NetworkManager.Device.Vxlan:Id, The "Id" property -org.freedesktop.NetworkManager.Device.Vxlan:L2miss, The "L2miss" property + org.freedesktop.NetworkManager.Device.Vxlan:L2miss, The "L2miss" property -org.freedesktop.NetworkManager.Device.Vxlan:L3miss, The "L3miss" property + org.freedesktop.NetworkManager.Device.Vxlan:L3miss, The "L3miss" property -org.freedesktop.NetworkManager.Device.Vxlan:Learning, The "Learning" property + org.freedesktop.NetworkManager.Device.Vxlan:Learning, The "Learning" property -org.freedesktop.NetworkManager.Device.Vxlan:Limit, The "Limit" property + org.freedesktop.NetworkManager.Device.Vxlan:Limit, The "Limit" property -org.freedesktop.NetworkManager.Device.Vxlan:Local, The "Local" property + org.freedesktop.NetworkManager.Device.Vxlan:Local, The "Local" property -org.freedesktop.NetworkManager.Device.Vxlan:Parent, The "Parent" property + org.freedesktop.NetworkManager.Device.Vxlan:Parent, The "Parent" property -org.freedesktop.NetworkManager.Device.Vxlan:Proxy, The "Proxy" property + org.freedesktop.NetworkManager.Device.Vxlan:Proxy, The "Proxy" property -org.freedesktop.NetworkManager.Device.Vxlan:Rsc, The "Rsc" property + org.freedesktop.NetworkManager.Device.Vxlan:Rsc, The "Rsc" property -org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax, The "SrcPortMax" property + org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMax, The "SrcPortMax" property -org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin, The "SrcPortMin" property + org.freedesktop.NetworkManager.Device.Vxlan:SrcPortMin, The "SrcPortMin" property -org.freedesktop.NetworkManager.Device.Vxlan:Tos, The "Tos" property + org.freedesktop.NetworkManager.Device.Vxlan:Tos, The "Tos" property -org.freedesktop.NetworkManager.Device.Vxlan:Ttl, The "Ttl" property + org.freedesktop.NetworkManager.Device.Vxlan:Ttl, The "Ttl" property -org.freedesktop.NetworkManager.Device.WireGuard, org.freedesktop.NetworkManager.Device.WireGuard + org.freedesktop.NetworkManager.Device.WireGuard, org.freedesktop.NetworkManager.Device.WireGuard -org.freedesktop.NetworkManager.Device.WireGuard:FwMark, The "FwMark" property + org.freedesktop.NetworkManager.Device.WireGuard:FwMark, The "FwMark" property -org.freedesktop.NetworkManager.Device.WireGuard:ListenPort, The "ListenPort" property + org.freedesktop.NetworkManager.Device.WireGuard:ListenPort, The "ListenPort" property -org.freedesktop.NetworkManager.Device.WireGuard:PublicKey, The "PublicKey" property + org.freedesktop.NetworkManager.Device.WireGuard:PublicKey, The "PublicKey" property -org.freedesktop.NetworkManager.Device.Wpan, org.freedesktop.NetworkManager.Device.Wpan + org.freedesktop.NetworkManager.Device.Wpan, org.freedesktop.NetworkManager.Device.Wpan -org.freedesktop.NetworkManager.Device.Wpan:HwAddress, The "HwAddress" property + org.freedesktop.NetworkManager.Device.Wpan:HwAddress, The "HwAddress" property org.freedesktop.NetworkManager.Device::StateChanged, The "StateChanged" signal @@ -589,6 +593,8 @@auto-negotiate, 802-3-ethernet +auto-route-ext-gw, ipv4, ipv6 + autoconnect, connection autoconnect-priority, connection @@ -662,9 +668,9 @@ D
-
- dad-timeout, ipv4, ipv6 +
- dad-timeout, ipv4, ipv6
-- data, user, vpn, ovs-external-ids +
- data, user, vpn, ovs-external-ids, ovs-other-config
- datapath-type, ovs-bridge
@@ -674,81 +680,81 @@- device-id, gsm
-- org.freedesktop.NetworkManager.Device.Wired, org.freedesktop.NetworkManager.Device.Wired +
- org.freedesktop.NetworkManager.Device.Wired, org.freedesktop.NetworkManager.Device.Wired
-- org.freedesktop.NetworkManager.Device.Wired:Carrier, The "Carrier" property +
- org.freedesktop.NetworkManager.Device.Wired:Carrier, The "Carrier" property
-- org.freedesktop.NetworkManager.Device.Wired:HwAddress, The "HwAddress" property +
- org.freedesktop.NetworkManager.Device.Wired:HwAddress, The "HwAddress" property
-- org.freedesktop.NetworkManager.Device.Wired:PermHwAddress, The "PermHwAddress" property +
- org.freedesktop.NetworkManager.Device.Wired:PermHwAddress, The "PermHwAddress" property
-- org.freedesktop.NetworkManager.Device.Wired:S390Subchannels, The "S390Subchannels" property +
- org.freedesktop.NetworkManager.Device.Wired:S390Subchannels, The "S390Subchannels" property
-- org.freedesktop.NetworkManager.Device.Wired:Speed, The "Speed" property +
- org.freedesktop.NetworkManager.Device.Wired:Speed, The "Speed" property
-- org.freedesktop.NetworkManager.Device.Wireless, org.freedesktop.NetworkManager.Device.Wireless +
- org.freedesktop.NetworkManager.Device.Wireless, org.freedesktop.NetworkManager.Device.Wireless
-- org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints(), The GetAccessPoints() method +
- org.freedesktop.NetworkManager.Device.Wireless.GetAccessPoints(), The GetAccessPoints() method
-- org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints(), The GetAllAccessPoints() method +
- org.freedesktop.NetworkManager.Device.Wireless.GetAllAccessPoints(), The GetAllAccessPoints() method
-- org.freedesktop.NetworkManager.Device.Wireless.RequestScan(), The RequestScan() method +
- org.freedesktop.NetworkManager.Device.Wireless.RequestScan(), The RequestScan() method
-- org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded, The "AccessPointAdded" signal +
- org.freedesktop.NetworkManager.Device.Wireless::AccessPointAdded, The "AccessPointAdded" signal
-- org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved, The "AccessPointRemoved" signal +
- org.freedesktop.NetworkManager.Device.Wireless::AccessPointRemoved, The "AccessPointRemoved" signal
-- org.freedesktop.NetworkManager.Device.Wireless:AccessPoints, The "AccessPoints" property +
- org.freedesktop.NetworkManager.Device.Wireless:AccessPoints, The "AccessPoints" property
-- org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint, The "ActiveAccessPoint" property +
- org.freedesktop.NetworkManager.Device.Wireless:ActiveAccessPoint, The "ActiveAccessPoint" property
-- org.freedesktop.NetworkManager.Device.Wireless:Bitrate, The "Bitrate" property +
- org.freedesktop.NetworkManager.Device.Wireless:Bitrate, The "Bitrate" property
-- org.freedesktop.NetworkManager.Device.Wireless:HwAddress, The "HwAddress" property +
- org.freedesktop.NetworkManager.Device.Wireless:HwAddress, The "HwAddress" property
-- org.freedesktop.NetworkManager.Device.Wireless:LastScan, The "LastScan" property +
- org.freedesktop.NetworkManager.Device.Wireless:LastScan, The "LastScan" property
-- org.freedesktop.NetworkManager.Device.Wireless:Mode, The "Mode" property +
- org.freedesktop.NetworkManager.Device.Wireless:Mode, The "Mode" property
-- org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress, The "PermHwAddress" property +
- org.freedesktop.NetworkManager.Device.Wireless:PermHwAddress, The "PermHwAddress" property
-- org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities, The "WirelessCapabilities" property +
- org.freedesktop.NetworkManager.Device.Wireless:WirelessCapabilities, The "WirelessCapabilities" property
-- org.freedesktop.NetworkManager.Device.WifiP2P, org.freedesktop.NetworkManager.Device.WifiP2P +
- org.freedesktop.NetworkManager.Device.WifiP2P, org.freedesktop.NetworkManager.Device.WifiP2P
-- org.freedesktop.NetworkManager.Device.WifiP2P.StartFind(), The StartFind() method +
- org.freedesktop.NetworkManager.Device.WifiP2P.StartFind(), The StartFind() method
-- org.freedesktop.NetworkManager.Device.WifiP2P.StopFind(), The StopFind() method +
- org.freedesktop.NetworkManager.Device.WifiP2P.StopFind(), The StopFind() method
-- org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded, The "PeerAdded" signal +
- org.freedesktop.NetworkManager.Device.WifiP2P::PeerAdded, The "PeerAdded" signal
-- org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved, The "PeerRemoved" signal +
- org.freedesktop.NetworkManager.Device.WifiP2P::PeerRemoved, The "PeerRemoved" signal
-- org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress, The "HwAddress" property +
- org.freedesktop.NetworkManager.Device.WifiP2P:HwAddress, The "HwAddress" property
-- org.freedesktop.NetworkManager.Device.WifiP2P:Peers, The "Peers" property +
- org.freedesktop.NetworkManager.Device.WifiP2P:Peers, The "Peers" property
- dhcp-anycast-address, 802-11-olpc-mesh
-- dhcp-client-id, ipv4 +
- dhcp-client-id, ipv4
-- dhcp-duid, ipv6 +
- dhcp-duid, ipv6
-- dhcp-fqdn, ipv4 +
- dhcp-fqdn, ipv4
-- dhcp-hostname, ipv4, ipv6 +
- dhcp-hostname, ipv4, ipv6
-- dhcp-hostname-flags, ipv4, ipv6 +
- dhcp-hostname-flags, ipv4, ipv6
-- dhcp-iaid, ipv4, ipv6 +
- dhcp-iaid, ipv4, ipv6
-- dhcp-reject-servers, ipv4, ipv6 +
- dhcp-reject-servers, ipv4, ipv6
-- dhcp-send-hostname, ipv4, ipv6 +
- dhcp-send-hostname, ipv4, ipv6
-- dhcp-timeout, ipv4, ipv6 +
- dhcp-timeout, ipv4, ipv6
-- dhcp-vendor-class-identifier, ipv4 +
- dhcp-vendor-class-identifier, ipv4
- org.freedesktop.NetworkManager.DHCP4Config, org.freedesktop.NetworkManager.DHCP4Config
@@ -758,15 +764,17 @@- org.freedesktop.NetworkManager.DHCP6Config:Options, The "Options" property
-- dns, ipv4, ipv6 +
- dns, ipv4, ipv6
-- dns-options, ipv4, ipv6 +
- dns-data, ipv4, ipv6 +
+- dns-options, ipv4, ipv6
- dns-over-tls, connection
-- dns-priority, ipv4, ipv6 +
- dns-priority, ipv4, ipv6
-- dns-search, ipv4, ipv6 +
- dns-search, ipv4, ipv6
- domain-match, 802-1x
@@ -810,14 +818,14 @@- from-dns-lookup, hostname
-- fwmark, wireguard +
- fwmark, ip-tunnel, wireguard
@@ -905,7 +913,7 @@G
-
- gateway, ipv4, ipv6 +
- gateway, ipv4, ipv6
- gateway-ping-timeout, connection
@@ -851,13 +859,13 @@- identity, 802-1x
-- ignore-auto-dns, ipv4, ipv6 +
- ignore-auto-dns, ipv4, ipv6
-- ignore-auto-routes, ipv4, ipv6 +
- ignore-auto-routes, ipv4, ipv6
- ingress-priority-map, vlan
-- input-key, ip-tunnel +
- input-key, ip-tunnel
- interface-name, connection, bond, bridge, match, team, vlan
@@ -865,7 +873,7 @@- ip6-auto-default-route, wireguard
-- ip6-privacy, ipv6 +
- ip6-privacy, ipv6
limit, vxlan -link-local, ipv4 + link-local, ipv4 link-watchers, team, team-port @@ -915,7 +923,7 @@llmnr, connection -local, ip-tunnel, vxlan + local, ip-tunnel, vxlan org.freedesktop.NetworkManager:AllDevices, The "AllDevices" property -org.freedesktop.NetworkManager:Capabilities, The "Capabilities" property + org.freedesktop.NetworkManager:Capabilities, The "Capabilities" property org.freedesktop.NetworkManager:Checkpoints, The "Checkpoints" property -org.freedesktop.NetworkManager:Connectivity, The "Connectivity" property + org.freedesktop.NetworkManager:Connectivity, The "Connectivity" property -org.freedesktop.NetworkManager:ConnectivityCheckAvailable, The "ConnectivityCheckAvailable" property + org.freedesktop.NetworkManager:ConnectivityCheckAvailable, The "ConnectivityCheckAvailable" property -org.freedesktop.NetworkManager:ConnectivityCheckEnabled, The "ConnectivityCheckEnabled" property + org.freedesktop.NetworkManager:ConnectivityCheckEnabled, The "ConnectivityCheckEnabled" property -org.freedesktop.NetworkManager:ConnectivityCheckUri, The "ConnectivityCheckUri" property + org.freedesktop.NetworkManager:ConnectivityCheckUri, The "ConnectivityCheckUri" property org.freedesktop.NetworkManager:Devices, The "Devices" property -org.freedesktop.NetworkManager:GlobalDnsConfiguration, The "GlobalDnsConfiguration" property + org.freedesktop.NetworkManager:GlobalDnsConfiguration, The "GlobalDnsConfiguration" property org.freedesktop.NetworkManager:Metered, The "Metered" property @@ -1010,10 +1018,12 @@org.freedesktop.NetworkManager:Startup, The "Startup" property -org.freedesktop.NetworkManager:State, The "State" property + org.freedesktop.NetworkManager:State, The "State" property org.freedesktop.NetworkManager:Version, The "Version" property +org.freedesktop.NetworkManager:VersionInfo, The "VersionInfo" property + org.freedesktop.NetworkManager:WimaxEnabled, The "WimaxEnabled" property org.freedesktop.NetworkManager:WimaxHardwareEnabled, The "WimaxHardwareEnabled" property @@ -1030,7 +1040,7 @@ max-age, bridge -may-fail, ipv4, ipv6 + may-fail, ipv4, ipv6 mcast-rejoin-count, team @@ -1042,7 +1052,7 @@metered, connection -method, ipv4, ipv6, proxy + method, ipv4, ipv6, proxy mka-cak, macsec @@ -1050,7 +1060,7 @@mka-ckn, macsec -mode, ip-tunnel, macsec, macvlan, tun, 802-11-wireless + mode, ip-tunnel, macsec, macvlan, tun, 802-11-wireless mppe-stateful, ppp @@ -1058,7 +1068,7 @@mru, ppp -mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless + mtu, cdma, gsm, infiniband, ipv6, ip-tunnel, ppp, 802-3-ethernet, wireguard, 802-11-wireless, loopback mud-url, connection @@ -1099,79 +1109,85 @@
- n-rxq, ovs-dpdk
+- n-rxq-desc, ovs-dpdk +
+- n-txq-desc, ovs-dpdk +
- network-id, gsm
- network-name, wimax
-- never-default, ipv4, ipv6 +
- never-default, ipv4, ipv6 +
+- NM80211ApFlags, enum NM80211ApFlags
-- NM80211ApFlags, enum NM80211ApFlags +
- NM80211ApSecurityFlags, enum NM80211ApSecurityFlags
-- NM80211ApSecurityFlags, enum NM80211ApSecurityFlags +
- NM80211Mode, enum NM80211Mode
-- NM80211Mode, enum NM80211Mode +
- NMActivationStateFlags, enum NMActivationStateFlags
-- NMActivationStateFlags, enum NMActivationStateFlags +
- NMActiveConnectionState, enum NMActiveConnectionState
-- NMActiveConnectionState, enum NMActiveConnectionState +
- NMActiveConnectionStateReason, enum NMActiveConnectionStateReason
-- NMActiveConnectionStateReason, enum NMActiveConnectionStateReason +
- NMBluetoothCapabilities, enum NMBluetoothCapabilities
-- NMBluetoothCapabilities, enum NMBluetoothCapabilities +
- NMCapability, enum NMCapability
-- NMCapability, enum NMCapability +
- NMCheckpointCreateFlags, enum NMCheckpointCreateFlags
-- NMCheckpointCreateFlags, enum NMCheckpointCreateFlags +
- NMClientPermission, enum NMClientPermission
-- NMClientPermission, enum NMClientPermission +
- NMClientPermissionResult, enum NMClientPermissionResult
-- NMClientPermissionResult, enum NMClientPermissionResult +
- NMConnectionMultiConnect, enum NMConnectionMultiConnect
-- NMConnectionMultiConnect, enum NMConnectionMultiConnect +
- NMConnectivityState, enum NMConnectivityState
-- NMConnectivityState, enum NMConnectivityState +
- NMDeviceCapabilities, enum NMDeviceCapabilities
-- NMDeviceCapabilities, enum NMDeviceCapabilities +
- NMDeviceInterfaceFlags, enum NMDeviceInterfaceFlags
-- NMDeviceInterfaceFlags, enum NMDeviceInterfaceFlags +
- NMDeviceModemCapabilities, enum NMDeviceModemCapabilities
-- NMDeviceModemCapabilities, enum NMDeviceModemCapabilities +
- NMDeviceReapplyFlags, enum NMDeviceReapplyFlags
-- NMDeviceReapplyFlags, enum NMDeviceReapplyFlags +
- NMDeviceState, enum NMDeviceState
-- NMDeviceState, enum NMDeviceState +
- NMDeviceStateReason, enum NMDeviceStateReason
-- NMDeviceStateReason, enum NMDeviceStateReason +
- NMDeviceType, enum NMDeviceType
-- NMDeviceType, enum NMDeviceType +
- NMDeviceWifiCapabilities, enum NMDeviceWifiCapabilities
-- NMDeviceWifiCapabilities, enum NMDeviceWifiCapabilities +
- NMIPTunnelMode, enum NMIPTunnelMode
-- NMIPTunnelMode, enum NMIPTunnelMode +
- NMManagerReloadFlags, enum NMManagerReloadFlags
-- NMManagerReloadFlags, enum NMManagerReloadFlags +
- NMMetered, enum NMMetered
-- NMMetered, enum NMMetered +
- NMMptcpFlags, enum NMMptcpFlags
-- NMMptcpFlags, enum NMMptcpFlags +
- NMRadioFlags, enum NMRadioFlags
-- NMRadioFlags, enum NMRadioFlags +
- NMRollbackResult, enum NMRollbackResult
-- NMRollbackResult, enum NMRollbackResult +
- NMSecretAgentCapabilities, enum NMSecretAgentCapabilities
-- NMSecretAgentCapabilities, enum NMSecretAgentCapabilities +
- NMSecretAgentGetSecretsFlags, enum NMSecretAgentGetSecretsFlags
-- NMSecretAgentGetSecretsFlags, enum NMSecretAgentGetSecretsFlags +
- NMSettingsAddConnection2Flags, enum NMSettingsAddConnection2Flags
-- NMSettingsAddConnection2Flags, enum NMSettingsAddConnection2Flags +
- NMSettingsConnectionFlags, enum NMSettingsConnectionFlags
-- NMSettingsConnectionFlags, enum NMSettingsConnectionFlags +
- NMSettingsUpdate2Flags, enum NMSettingsUpdate2Flags
-- NMSettingsUpdate2Flags, enum NMSettingsUpdate2Flags +
- NMState, enum NMState
-- NMState, enum NMState +
- NMTernary, enum NMTernary
-- NMTernary, enum NMTernary +
- NMVersionInfoCapability, enum NMVersionInfoCapability
- NMVpnConnectionState, enum NMVpnConnectionState
@@ -1181,7 +1197,7 @@- NMVpnServiceState, enum NMVpnServiceState
-- NMWimaxNspNetworkType, enum NMWimaxNspNetworkType +
- NMWimaxNspNetworkType, enum NMWimaxNspNetworkType
- no-vj-comp, ppp
@@ -1202,13 +1218,15 @@O
+
- ofport-request, ovs-interface +
- only-from-default, hostname
- optional, 802-1x
- options, bond
-- output-key, ip-tunnel +
- output-key, ip-tunnel
- owner, tun
@@ -1247,7 +1265,7 @@- path-cost, bridge-port
-- path-mtu-discovery, ip-tunnel +
- path-mtu-discovery, ip-tunnel
- peer, ovs-patch, wifi-p2p, veth
@@ -1311,17 +1329,17 @@- powersave, 802-11-wireless
-- org.freedesktop.NetworkManager.PPP, org.freedesktop.NetworkManager.PPP +
- org.freedesktop.NetworkManager.PPP, org.freedesktop.NetworkManager.PPP
-- org.freedesktop.NetworkManager.PPP.NeedSecrets(), The NeedSecrets() method +
- org.freedesktop.NetworkManager.PPP.NeedSecrets(), The NeedSecrets() method
-- org.freedesktop.NetworkManager.PPP.SetIfindex(), The SetIfindex() method +
- org.freedesktop.NetworkManager.PPP.SetIfindex(), The SetIfindex() method
-- org.freedesktop.NetworkManager.PPP.SetIp4Config(), The SetIp4Config() method +
- org.freedesktop.NetworkManager.PPP.SetIp4Config(), The SetIp4Config() method
-- org.freedesktop.NetworkManager.PPP.SetIp6Config(), The SetIp6Config() method +
- org.freedesktop.NetworkManager.PPP.SetIp6Config(), The SetIp6Config() method
-- org.freedesktop.NetworkManager.PPP.SetState(), The SetState() method +
- org.freedesktop.NetworkManager.PPP.SetState(), The SetState() method
- prio, team-port
@@ -1355,7 +1373,7 @@- proto, 802-11-wireless-security
-- protocol, adsl +
- protocol, adsl, vlan
- proxy, vxlan
@@ -1377,7 +1395,7 @@R
-
- ra-timeout, ipv6 +
- ra-timeout, ipv6
- rate, 802-11-wireless
@@ -1393,21 +1411,23 @@- refuse-pap, ppp
-- remote, ip-tunnel, vxlan +
- remote, ip-tunnel, vxlan
- require-mppe, ppp
- require-mppe-128, ppp
-- required-timeout, ipv4, ipv6 +
- required-timeout, ipv4, ipv6
-- route-data, ipv4, ipv6 +
- route-data, ipv4, ipv6
-- route-metric, ipv4, ipv6 +
- route-metric, ipv4, ipv6
-- route-table, ipv4, ipv6 +
- route-table, ipv4, ipv6
-- routes, ipv4, ipv6 +
- routes, ipv4, ipv6 +
+- routing-rules, ipv4, ipv6
- rsc, vxlan
@@ -1507,15 +1527,17 @@- timestamp, connection
-- token, ipv6 +
- token, ipv6
-- tos, ip-tunnel, vxlan +
- tos, ip-tunnel, vxlan
- total-vfs, sriov
- transport-mode, infiniband
-- ttl, ip-tunnel, vxlan +
- trunks, ovs-port +
+- ttl, ip-tunnel, vxlan
- tx-power, 802-11-wireless
@@ -1547,7 +1569,7 @@- vlan-filtering, bridge
-- vlan-mode, ovs-port +
- vlan-mode, ovs-port
- vlan-protocol, bridge
diff --git a/docs/api/html/manpages.html b/docs/api/html/manpages.html index 4ce24258..b3befb31 100644 --- a/docs/api/html/manpages.html +++ b/docs/api/html/manpages.html @@ -35,7 +35,7 @@ NetworkManager-dispatcher — Dispatch user scripts for NetworkManager- -NetworkManager-wait-online.service — Wait for network to come online +NetworkManager-wait-online.service — Wait for the network to come online
- nmcli — command-line tool for controlling NetworkManager diff --git a/docs/api/html/nm-dbus-types.html b/docs/api/html/nm-dbus-types.html index 892a1924..5d7db24a 100644 --- a/docs/api/html/nm-dbus-types.html +++ b/docs/api/html/nm-dbus-types.html @@ -29,13 +29,33 @@
++enum NMVersionInfoCapability
+%_NM_VERSION_INFO_CAPABILITY_UNUSED: a dummy capability. It has no meaning, don't use it.
+Currently no enum values are defined. These capabilities are exposed on D-Bus in the "VersionInfo" bit field.
+Since: 1.42
+ + +
+enum NMCapability
NMCapability names the numbers in the Capabilities property. Capabilities are positive numbers. They are part of stable API and a certain capability number is guaranteed not to change.
The range 0x7000 - 0x7FFF of capabilities is guaranteed not to be used by upstream NetworkManager. It could thus be used for downstream extensions.
Since: 1.6
-Values
+Values
@@ -84,7 +104,7 @@ NMState values indicate the current overall networking state.
-Values
+Values
@@ -222,7 +242,7 @@ enum NMConnectivityState
-Values
+Values
@@ -316,7 +336,7 @@ NMDeviceType values indicate the type of hardware represented by a device object.
-@@ -815,7 +850,7 @@Values
+Values
@@ -805,6 +825,21 @@ + + + +NM_DEVICE_TYPE_LOOPBACK
+ ++ +=
+ +32+ +a loopback interface. Since: 1.42.
+ ++ General device capability flags.
-Values
+Values
@@ -909,7 +944,7 @@ 802.11 specific device encryption and authentication capabilities.
-Values
+Values
@@ -1138,7 +1173,7 @@ 802.11 access point flags.
-Values
+Values
@@ -1232,7 +1267,7 @@ 802.11 access point security and authentication flags. These flags describe the current security requirements of an access point as determined from the access point's beacon.
-Values
+Values
@@ -1476,7 +1511,7 @@ Indicates the 802.11 mode an access point or device is currently in.
-Values
+Values
@@ -1570,7 +1605,7 @@ NMBluetoothCapabilities values indicate the usable capabilities of a Bluetooth device.
-Values
+Values
@@ -1634,7 +1669,7 @@ NMDeviceModemCapabilities values indicate the generic radio access technology families a modem device supports. For more information on the specific access technologies the device supports use the ModemManager D-Bus API.
-Values
+Values
@@ -1743,7 +1778,7 @@ WiMAX network type.
-Values
+Values
@@ -1821,7 +1856,7 @@ enum NMDeviceState
-Values
+Values
@@ -2035,7 +2070,7 @@ Device state change reason codes
-Values
+Values
@@ -3079,7 +3114,7 @@ Since: 1.2
-Values
+Values
@@ -3173,7 +3208,7 @@ Since: 1.14
-Values
+Values
@@ -3252,7 +3287,7 @@ NMActiveConnectionState values indicate the state of a connection to a specific network while it is starting, connected, or disconnecting from that network.
-Values
+Values
@@ -3347,7 +3382,7 @@ Since: 1.8
-Values
+Values
@@ -3591,7 +3626,7 @@ NMSecretAgentGetSecretsFlags values modify the behavior of a GetSecrets request.
-Values
+Values
@@ -3715,7 +3750,7 @@ NMSecretAgentCapabilities indicate various capabilities of the agent.
-Values
+Values
@@ -3765,7 +3800,7 @@ Since: 1.2
-Values
+Values
@@ -3965,7 +4000,7 @@ Since: 1.12 (public since 1.4, g-ir since 1.12)
-Values
+Values
@@ -4075,7 +4110,7 @@ Since: 1.4
-Values
+Values
@@ -4155,7 +4190,7 @@ Since: 1.12
-Values
+Values
@@ -4250,7 +4285,7 @@ Since: 1.10
-Values
+Values
@@ -4405,7 +4440,7 @@ Since: 1.20
-Values
+Values
@@ -4484,7 +4519,7 @@ Since: 1.12
-Values
+Values
@@ -4621,11 +4656,10 @@ enum NMDeviceReapplyFlags
Flags for the Reapply() D-Bus call of a device and nm_device_reapply_async().
-Since: 1.42, 1.40.10
-On 1.40.10+, no GFlags type is created.
+Since: 1.42
-Values
+Values
@@ -4675,7 +4709,7 @@ Since: 1.14
-Values
+Values
@@ -4740,7 +4774,7 @@ Since: 1.22
-Values
+Values
@@ -4835,7 +4869,7 @@ Since: 1.22
-Values
+Values
@@ -4944,7 +4978,7 @@ NMClientPermission values indicate various permissions that NetworkManager clients can obtain to perform certain tasks on behalf of the current user.
-Values
+Values
@@ -5233,7 +5267,7 @@ NMClientPermissionResult values indicate what authorizations and permissions the user requires to obtain a given NMClientPermission
-Values
+Values
@@ -5313,7 +5347,7 @@ Since: 1.38
-Values
+Values
@@ -5377,7 +5411,7 @@ Since: 1.40
-Values
+Values
diff --git a/docs/api/html/nm-settings-dbus.html b/docs/api/html/nm-settings-dbus.html index fd1f0892..96bd6976 100644 --- a/docs/api/html/nm-settings-dbus.html +++ b/docs/api/html/nm-settings-dbus.html @@ -95,7 +95,7 @@ connection setting
-General Connection Profile Settings.
+General Connection Profile Settings.
@@ -380,7 +380,7 @@
802-1x setting
-IEEE 802.1x Authentication Settings.
+IEEE 802.1x Authentication Settings.
@@ -778,7 +782,7 @@
adsl setting
-ADSL Settings.
+ADSL Settings.
@@ -848,7 +852,7 @@
bluetooth setting
-Bluetooth Settings.
+Bluetooth Settings.
@@ -883,7 +887,7 @@
bond setting
-Bonding Settings.
+Bonding Settings.
@@ -918,7 +922,7 @@
bridge setting
-Bridging Settings.
+Bridging Settings.
@@ -1149,7 +1155,7 @@
bridge-port setting
-Bridge Port Settings.
+Bridge Port Settings.
@@ -1204,7 +1210,7 @@
cdma setting
-CDMA-based Mobile Broadband Settings.
+CDMA-based Mobile Broadband Settings.
@@ -1260,7 +1266,7 @@
dcb setting
-Data Center Bridging Settings.
+Data Center Bridging Settings.
@@ -1388,7 +1394,7 @@
dummy setting
-Dummy Link Settings.
+Dummy Link Settings.
@@ -1408,7 +1414,7 @@
ethtool setting
-Ethtool Ethernet Settings.
+Ethtool Ethernet Settings.
@@ -1428,7 +1434,7 @@
generic setting
-Generic Link Settings.
+Generic Link Settings.
-Table 12. 802-1x setting
-+
Table 12. 802-11-wireless setting
++ +
@@ -290,370 +290,331 @@ DEVICETYPE=TeamPort - eap -IEEE_8021X_EAP_METHODS(+) - +ssid +ESSID - EAP method for 802.1X authentication. - -Example: IEEE_8021X_EAP_METHODS=PEAP + SSID of Wi-Fi network. -Allowed values: "LEAP", "PWD", "TLS", "PEAP", "TTLS", "FAST" +Example: ESSID="Quick Net"- identity -IEEE_8021X_IDENTITY(+) - +mode +MODE - Identity for EAP authentication methods. + Wi-Fi network mode. -Example: IEEE_8021X_IDENTITY=itsme +Allowed values: Ad-Hoc, Managed (Auto) [case insensitive]- anonymous-identity -IEEE_8021X_ANON_IDENTITY(+) + band +BAND(+) - Anonymous identity for EAP authentication methods. +BAND alone is honored, but CHANNEL overrides BAND since it implies a band. + +Example: BAND=bg + +Allowed values: a, bg - pac-file -IEEE_8021X_PAC_FILE(+) - +channel +CHANNEL - File with PAC (Protected Access Credential) for EAP-FAST. + Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg". -Example: IEEE_8021X_PAC_FILE=/home/joe/my-fast.pac +Example: CHANNEL=6- ca-cert -IEEE_8021X_CA_CERT(+) + bssid +BSSID(+) - CA certificate for EAP. + Restricts association only to a single AP. -Example: IEEE_8021X_CA_CERT=/home/joe/cacert.crt +Example: BSSID=00:1E:BD:64:83:21- ca-path -IEEE_8021X_CA_PATH(+) - +rate +(none) - The search path for the certificate. +This property is not handled by ifcfg-rh plugin. - subject-match -IEEE_8021X_SUBJECT_MATCH(+) - +tx-power +(none) - Substring to match subject of server certificate against. - -Example: IEEE_8021X_SUBJECT_MATCH="Red Hat" +This property is not handled by ifcfg-rh plugin. - altsubject-matches -IEEE_8021X_ALTSUBJECT_MATCHES(+) - +mac-address +HWADDR - List of strings to be matched against the altSubjectName. - -Example: IEEE_8021X_ALTSUBJECT_MATCHES="s1.domain.cc" +Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device. - domain-suffix-match -IEEE_8021X_DOMAIN_SUFFIX_MATCH(+) - +cloned-mac-address +MACADDR - Suffix to match domain of server certificate against. +Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99). - domain-match -IEEE_8021X_DOMAIN_MATCH(+) + generate-mac-address-mask +GENERATE_MAC_ADDRESS_MASK(+) - Value to match domain of server certificate against. +the MAC address mask for generating randomized and stable cloned-mac-address. - client-cert -IEEE_8021X_CLIENT_CERT(+) + mac-address-blacklist +HWADDR_BLACKLIST(+) - Client certificate for EAP. - -Example: IEEE_8021X_CLIENT_CERT=/home/joe/mycert.crt +It denies usage of the connection for any device whose address is listed. - phase1-peapver -IEEE_8021X_PEAP_VERSION(+) - +seen-bssids +(none) - Use to force a specific PEAP version. - -Allowed values: 0, 1 +This property is not handled by ifcfg-rh plugin. - +phase1-peaplabel -IEEE_8021X_PEAP_FORCE_NEW_LABEL(+) + mtu +MTU ++ MTU of the wireless interface. ++ hidden +SSID_HIDDEN(+) -no -Use to force the new PEAP label during key derivation. - -Allowed values: yes, no ++ Whether the network hides the SSID. - phase1-fast-provisioning -IEEE_8021X_FAST_PROVISIONING(+) + powersave +POWERSAVE(+) - Enable in-line provisioning of EAP-FAST credentials. + Enables or disables Wi-Fi power saving. -Example: IEEE_8021X_FAST_PROVISIONING="allow-auth allow-unauth" +Example: POWERSAVE=enable -Allowed values: space-separated list of these values [allow-auth, allow-unauth] +Allowed values: default, ignore, enable, disable- phase1-auth-flags -IEEE_8021X_PHASE1_AUTH_FLAGS(+) + mac-address-randomization +MAC_ADDRESS_RANDOMIZATION(+) - Authentication flags for the supplicant + Enables or disables Wi-Fi MAC address randomization. -Example: IEEE_8021X_PHASE1_AUTH_FLAGS="tls-1-0-disable tls-1-1-disable" +Example: MAC_ADDRESS_RANDOMIZATION=always -Allowed values: space-separated list of authentication flags names +Allowed values: default, never, always- +phase2-auth -IEEE_8021X_INNER_AUTH_METHODS(+) - +security +(none) - Inner non-EAP authentication methods for TTLS or the inner EAP authentication method for PEAP. IEEE_8021X_INNER_AUTH_METHODS can contain values both for 'phase2-auth' and 'phase2-autheap' properties. - -Example: IEEE_8021X_INNER_AUTH_METHODS=PAP + This property is deprecated and not handled by ifcfg-rh-plugin. ++ + +ap-isolation +AP_ISOLATION(+) + +missing variable means global default +Whether AP isolation is enabled -Allowed values: "PAP", "CHAP", "MSCHAP", "MSCHAPV2", "GTC", "OTP", "MD5" and "TLS" +Allowed values: "yes", "no"+-Table 13. 802-11-wireless-security setting
+-+
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description +- +phase2-autheap -IEEE_8021X_INNER_AUTH_METHODS(+) + key-mgmt +KEY_MGMT(+) - Inner EAP-based authentication methods. Note that IEEE_8021X_INNER_AUTH_METHODS is also used for 'phase2-auth' values. + Key management method. -Example: IEEE_8021X_INNER_AUTH_METHODS="MSCHAPV2 EAP-TLS" +Allowed values: none, ieee8021x, owe, wpa-psk, sae, wpa-eap, wpa-eap-suite-b-192 ++ wep-tx-keyidx +DEFAULTKEY +1 +Index of active WEP key. Note that in ifcfg format the index starts counting at 1, while NetworkManager API otherwise is zero based. -Allowed values: "EAP-MD5", "EAP-MSCHAPV2", "EAP-GTC", "EAP-OTP" and "EAP-TLS" +Allowed values: 1, 2, 3, 4- phase2-ca-path -IEEE_8021X_PHASE2_CA_PATH(+) + auth-alg +SECURITYMODE(+) - The search path for the certificate. +Authentication algorithm for WEP. + +Allowed values: restricted, open, leap - phase2-subject-match -IEEE_8021X_PHASE2_SUBJECT_MATCH(+) + proto +WPA_ALLOW_WPA(+), WPA_ALLOW_WPA2(+) -- Substring to match subject of server certificate against. + no +Allowed WPA protocols, WPA and WPA2 (RSN). -Example: IEEE_8021X_PHASE2_SUBJECT_MATCH="Red Hat" +Allowed values: yes, no- phase2-altsubject-matches -IEEE_8021X_PHASE2_ALTSUBJECT_MATCHES(+) + pairwise +CIPHER_PAIRWISE(+) - + Restrict pairwise encryption algorithms, specified as a space separated list. + +Allowed values: CCMP, TKIP - phase2-domain-suffix-match -IEEE_8021X_PHASE2_DOMAIN_SUFFIX_MATCH(+) + group +CIPHER_GROUP(+) - Suffix to match domain of server certificate for phase 2 against. +Restrict group/broadcast encryption algorithms, specified as a space separated list. + +Allowed values: CCMP, TKIP, WEP40, WEP104 - phase2-domain-match -IEEE_8021X_PHASE2_DOMAIN_MATCH(+) + pmf +PMF(+) - Value to match domain of server certificate for phase 2 against. +Enables or disables PMF (802.11w) + +Example: PMF=required + +Allowed values: default, disable, optional, required - phase2-client-cert -IEEE_8021X_INNER_CLIENT_CERT(+) + leap-username +IEEE_8021X_IDENTITY(+) - Client certificate for inner EAP method. - -Example: IEEE_8021X_INNER_CLIENT_CERT=/home/joe/mycert.crt +Login name for LEAP. - password -IEEE_8021X_PASSWORD(+) + wep-key0 +KEY1, KEY_PASSPHRASE1(+) - UTF-8 encoded password used for EAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent. +The first WEP key (used in most networks). See also DEFAULTKEY for key index. - password-flags -IEEE_8021X_PASSWORD_FLAGS(+) + wep-key1 +KEY2, KEY_PASSPHRASE2(+) - Password flags for IEEE_8021X_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values) +WEP key with index 1. See also DEFAULTKEY for key index. - -password-raw -IEEE_8021X_PASSWORD_RAW(+) - -- password used for EAP, encoded as a hexadecimal string. It can also go to "key-" lookaside file. - -Example: IEEE_8021X_PASSWORD_RAW=041c8320083aa4bf -- -password-raw-flags -IEEE_8021X_PASSWORD_RAW_FLAGS(+) - -- The secret flags for password-raw. -- private-key -IEEE_8021X_PRIVATE_KEY(+) + wep-key2 +KEY3, KEY_PASSPHRASE3(+) - Private key for EAP-TLS. - -Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12 +WEP key with index 2. See also DEFAULTKEY for key index. - private-key-password -IEEE_8021X_PRIVATE_KEY_PASSWORD(+) + wep-key3 +KEY4, KEY_PASSPHRASE4(+) - Password for IEEE_8021X_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent. +WEP key with index 3. See also DEFAULTKEY for key index. - private-key-password-flags -IEEE_8021X_PRIVATE_KEY_PASSWORD_FLAGS(+) + wep-key-flags +WEP_KEY_FLAGS(+) - Password flags for IEEE_8021X_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values) +Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see the section called “Secret flag types:” for _FLAGS values) - phase2-private-key -IEEE_8021X_INNER_PRIVATE_KEY(+) - +psk +WPA_PSK - Private key for inner authentication method for EAP-TLS. +Pre-Shared-Key for WPA networks. - phase2-private-key-password -IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD(+) + psk-flags +WPA_PSK_FLAGS(+) - Password for IEEE_8021X_INNER_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent. +Password flags for WPA_PSK_FLAGS. (see the section called “Secret flag types:” for _FLAGS values) + +Example: WPA_PSK_FLAGS=user - phase2-private-key-password-flags -IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD_FLAGS(+) + leap-password +IEEE_8021X_PASSWORD(+) - Password flags for IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values) +Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent. - pin -IEEE_8021X_PIN(+) + leap-password-flags +IEEE_8021X_PASSWORD_FLAGS(+) - The pin secret used for EAP authentication methods. +Password flags for IEEE_8021X_PASSWORD_FLAGS. (see the section called “Secret flag types:” for _FLAGS values) - pin-flags -IEEE_8021X_PIN_FLAGS(+) + wep-key-type +KEY<i> or KEY_PASSPHRASE<i>(+); KEY_TYPE(+) - The secret flags for the pin property. +KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted. + +Example: KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey - system-ca-certs -IEEE_8021X_SYSTEM_CA_CERTS(+) - +wps-method +WPS_METHOD - a boolean value. +Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used. + +Example: WPS_METHOD=disabled, WPS_METHOD="pin pbc" - -auth-timeout -IEEE_8021X_AUTH_TIMEOUT(+) + fils +FILS(+) -0 -Timeout in seconds for the 802.1X authentication. Zero means the global default or 25. -- - -optional -IEEE_8021X_OPTIONAL(+) default=no - whether the 802.1X authentication is optional ---Table 13. bond-port setting
---
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- -queue-id -BONDING_OPTS: queue-id= -0 -Queue ID. + Enables or disables FILS (802.11ai) -Allowed values: 0 - 65535 --Table 14. bond setting
--
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- +Allowed values: default, disable, optional, required + +options -BONDING_OPTS -- Bonding options. +Example: FILS=required -Example: BONDING_OPTS="miimon=100 mode=broadcast" --Table 15. bridge-port setting
-+
Table 14. 802-1x setting
+- -
@@ -668,527 +629,441 @@ Example: BONDING_OPTS="miimon=100 mode=broadcast" - priority -BRIDGING_OPTS: priority= -32 -STP priority. + eap +IEEE_8021X_EAP_METHODS(+) + ++ EAP method for 802.1X authentication. -Allowed values: 0 - 63 +Example: IEEE_8021X_EAP_METHODS=PEAP + +Allowed values: "LEAP", "PWD", "TLS", "PEAP", "TTLS", "FAST"- path-cost -BRIDGING_OPTS: path_cost= -100 -STP cost. + identity +IEEE_8021X_IDENTITY(+) + ++ Identity for EAP authentication methods. -Allowed values: 1 - 65535 +Example: IEEE_8021X_IDENTITY=itsme- hairpin-mode -BRIDGING_OPTS: hairpin_mode= -yes -Hairpin mode of the bridge port. +anonymous-identity +IEEE_8021X_ANON_IDENTITY(+) + ++ Anonymous identity for EAP authentication methods. - - -vlans -BRIDGE_PORT_VLANS +pac-file +IEEE_8021X_PAC_FILE(+) + - List of VLANs on the bridge port + File with PAC (Protected Access Credential) for EAP-FAST. -Example: BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged" +Example: IEEE_8021X_PAC_FILE=/home/joe/my-fast.pac--Table 16. bridge setting
---
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- mac-address -BRIDGE_MACADDR(+) + ca-cert +IEEE_8021X_CA_CERT(+) - MAC address of the bridge. Note that this requires a recent kernel support, originally introduced in 3.15 upstream kernel) BRIDGE_MACADDR for bridges is an NM extension. +CA certificate for EAP. + +Example: IEEE_8021X_CA_CERT=/home/joe/cacert.crt - stp -STP -no -Span tree protocol participation. +ca-path +IEEE_8021X_CA_PATH(+) + ++ The search path for the certificate. - priority -BRIDGING_OPTS: priority= -32768 -STP priority. + subject-match +IEEE_8021X_SUBJECT_MATCH(+) + ++ Substring to match subject of server certificate against. -Allowed values: 0 - 32768 +Example: IEEE_8021X_SUBJECT_MATCH="Red Hat"- forward-delay -DELAY -15 -STP forwarding delay. + altsubject-matches +IEEE_8021X_ALTSUBJECT_MATCHES(+) + ++ List of strings to be matched against the altSubjectName. -Allowed values: 2 - 30 +Example: IEEE_8021X_ALTSUBJECT_MATCHES="s1.domain.cc"- hello-time -BRIDGING_OPTS: hello_time= -2 -STP hello time. - -Allowed values: 1 - 10 +domain-suffix-match +IEEE_8021X_DOMAIN_SUFFIX_MATCH(+) + ++ Suffix to match domain of server certificate against. - max-age -BRIDGING_OPTS: max_age= -20 -STP maximum message age. - -Allowed values: 6 - 40 +domain-match +IEEE_8021X_DOMAIN_MATCH(+) + ++ Value to match domain of server certificate against. - ageing-time -BRIDGING_OPTS: ageing_time= -300 -Ethernet MAC ageing time. + client-cert +IEEE_8021X_CLIENT_CERT(+) + ++ Client certificate for EAP. -Allowed values: 0 - 1000000 +Example: IEEE_8021X_CLIENT_CERT=/home/joe/mycert.crt- multicast-snooping -BRIDGING_OPTS: multicast_snooping= -1 -IGMP snooping support. + phase1-peapver +IEEE_8021X_PEAP_VERSION(+) + ++ Use to force a specific PEAP version. -Allowed values: 0 or 1 +Allowed values: 0, 1- vlan-filtering -BRIDGING_OPTS: vlan_filtering= -0 -VLAN filtering support. + phase1-peaplabel +IEEE_8021X_PEAP_FORCE_NEW_LABEL(+) + +no +Use to force the new PEAP label during key derivation. -Allowed values: 0 or 1 +Allowed values: yes, no- vlan-default-pvid -BRIDGING_OPTS: default_pvid= -1 -default VLAN PVID. + phase1-fast-provisioning +IEEE_8021X_FAST_PROVISIONING(+) + ++ Enable in-line provisioning of EAP-FAST credentials. -Allowed values: 0 - 4094 +Example: IEEE_8021X_FAST_PROVISIONING="allow-auth allow-unauth" + +Allowed values: space-separated list of these values [allow-auth, allow-unauth]- vlans -BRIDGE_VLANS +phase1-auth-flags +IEEE_8021X_PHASE1_AUTH_FLAGS(+) + - List of VLANs on the bridge + Authentication flags for the supplicant -Example: BRIDGE_VLANS="1 pvid untagged,20,300-400 untagged" +Example: IEEE_8021X_PHASE1_AUTH_FLAGS="tls-1-0-disable tls-1-1-disable" + +Allowed values: space-separated list of authentication flags names- group-address -BRIDGING_OPTS: group_address= +phase2-auth +IEEE_8021X_INNER_AUTH_METHODS(+) + - STP group address. + Inner non-EAP authentication methods for TTLS or the inner EAP authentication method for PEAP. IEEE_8021X_INNER_AUTH_METHODS can contain values both for 'phase2-auth' and 'phase2-autheap' properties. -Example: BRIDGING_OPTS="group_address=01:80:C2:00:00:0A" +Example: IEEE_8021X_INNER_AUTH_METHODS=PAP + +Allowed values: "PAP", "CHAP", "MSCHAP", "MSCHAPV2", "GTC", "OTP", "MD5" and "TLS"- vlan-protocol -BRIDGING_OPTS: vlan_protocol= +phase2-autheap +IEEE_8021X_INNER_AUTH_METHODS(+) + - VLAN filtering protocol. + Inner EAP-based authentication methods. Note that IEEE_8021X_INNER_AUTH_METHODS is also used for 'phase2-auth' values. -Example: BRIDGING_OPTS="vlan_protocol=802.1Q" +Example: IEEE_8021X_INNER_AUTH_METHODS="MSCHAPV2 EAP-TLS" + +Allowed values: "EAP-MD5", "EAP-MSCHAPV2", "EAP-GTC", "EAP-OTP" and "EAP-TLS"- vlan-stats-enabled -BRIDGING_OPTS: vlan_stats_enabled= -0 -- - -Example: BRIDGING_OPTS="vlan_stats_enabled=1" +phase2-ca-path +IEEE_8021X_PHASE2_CA_PATH(+) + ++ The search path for the certificate. - multicast-router -BRIDGING_OPTS: multicast_router= -auto -- - -Example: BRIDGING_OPTS="multicast_router=enabled" + phase2-subject-match +IEEE_8021X_PHASE2_SUBJECT_MATCH(+) + ++ Substring to match subject of server certificate against. -Allowed values: auto, enabled, disabled +Example: IEEE_8021X_PHASE2_SUBJECT_MATCH="Red Hat"- multicast-query-use-ifaddr -BRIDGING_OPTS: multicast_query_use_ifaddr= -0 -- - -Example: BRIDGING_OPTS="multicast_query-use_ifaddr=1" +phase2-altsubject-matches +IEEE_8021X_PHASE2_ALTSUBJECT_MATCHES(+) + ++ - multicast-querier -BRIDGING_OPTS: multicast_querier= -0 -- - -Example: BRIDGING_OPTS="multicast_querier=1" +phase2-domain-suffix-match +IEEE_8021X_PHASE2_DOMAIN_SUFFIX_MATCH(+) + ++ Suffix to match domain of server certificate for phase 2 against. - multicast-hash-max -BRIDGING_OPTS: multicast_hash_max= -4096 -- - -Example: BRIDGING_OPTS="multicast_hash_max=8192" +phase2-domain-match +IEEE_8021X_PHASE2_DOMAIN_MATCH(+) + ++ Value to match domain of server certificate for phase 2 against. - multicast-last-member-count -BRIDGING_OPTS: multicast_last_member_count= -2 -- + phase2-client-cert +IEEE_8021X_INNER_CLIENT_CERT(+) + ++ Client certificate for inner EAP method. -Example: BRIDGING_OPTS="multicast_last_member_count=4" +Example: IEEE_8021X_INNER_CLIENT_CERT=/home/joe/mycert.crt- multicast-last-member-interval -BRIDGING_OPTS: multicast_last_member_interval= -100 -- - -Example: BRIDGING_OPTS="multicast_last_member_interval=200" +password +IEEE_8021X_PASSWORD(+) + ++ UTF-8 encoded password used for EAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent. - multicast-membership-interval -BRIDGING_OPTS: multicast_membership_interval= -26000 -- - -Example: BRIDGING_OPTS="multicast_membership_interval=16000" +password-flags +IEEE_8021X_PASSWORD_FLAGS(+) + ++ Password flags for IEEE_8021X_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values) - multicast-querier-interval -BRIDGING_OPTS: multicast_querier_interval= -25500 -- + password-raw +IEEE_8021X_PASSWORD_RAW(+) + ++ password used for EAP, encoded as a hexadecimal string. It can also go to "key-" lookaside file. -Example: BRIDGING_OPTS="multicast_querier_interval=20000" +Example: IEEE_8021X_PASSWORD_RAW=041c8320083aa4bf- multicast-query-interval -BRIDGING_OPTS: multicast_query_interval= -12500 -- - -Example: BRIDGING_OPTS="multicast_query_interval=22500" +password-raw-flags +IEEE_8021X_PASSWORD_RAW_FLAGS(+) + ++ The secret flags for password-raw. - multicast-query-response-interval -BRIDGING_OPTS: multicast_query_response_interval= -1000 -- + private-key +IEEE_8021X_PRIVATE_KEY(+) + ++ Private key for EAP-TLS. -Example: BRIDGING_OPTS="multicast_query_response_interval=2000" +Example: IEEE_8021X_PRIVATE_KEY=/home/joe/mykey.p12- multicast-startup-query-count -BRIDGING_OPTS: multicast_startup_query_count= -2 -- - -Example: BRIDGING_OPTS="multicast_startup_query_count=4" +private-key-password +IEEE_8021X_PRIVATE_KEY_PASSWORD(+) + ++ Password for IEEE_8021X_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent. - - -multicast-startup-query-interval -BRIDGING_OPTS: multicast_startup_query_interval= -3125 -- - -Example: BRIDGING_OPTS="multicast_startup_query_interval=4000" +private-key-password-flags +IEEE_8021X_PRIVATE_KEY_PASSWORD_FLAGS(+) + ++ Password flags for IEEE_8021X_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values) -+Table 17. connection setting
-+-
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- id -NAME(+) + phase2-private-key +IEEE_8021X_INNER_PRIVATE_KEY(+) - User friendly name for the connection profile. +Private key for inner authentication method for EAP-TLS. - uuid -UUID(+) + phase2-private-key-password +IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD(+) - UUID for the connection profile. When missing, NetworkManager creates the UUID itself (by hashing the filename). +Password for IEEE_8021X_INNER_PRIVATE_KEY. It can also go to "key-" lookaside file, or it can be owned by a secret agent. - stable-id -STABLE_ID(+) + phase2-private-key-password-flags +IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD_FLAGS(+) - Token to generate stable IDs. +Password flags for IEEE_8021X_INNER_PRIVATE_KEY_PASSWORD password. (see the section called “Secret flag types:” for _FLAGS values) - interface-name -DEVICE +pin +IEEE_8021X_PIN(+) + - Interface name of the device this profile is bound to. The variable can be left out when the profile should apply for more devices. Note that DEVICE can be required for some connection types. +The pin secret used for EAP authentication methods. - type -TYPE (DEVICETYPE, DEVICE) +pin-flags +IEEE_8021X_PIN_FLAGS(+) + - Base type of the connection. DEVICETYPE is used for teaming connections. - -Example: TYPE=Ethernet; TYPE=Bond; TYPE=Bridge; DEVICETYPE=TeamPort - -Allowed values: Ethernet, Wireless, InfiniBand, Bridge, Bond, Vlan, Team, TeamPort +The secret flags for the pin property. - -permissions -USERS(+) + system-ca-certs +IEEE_8021X_SYSTEM_CA_CERTS(+) - Restrict to certain users the access to this connection, and allow the connection to be active only when at least one of the specified users is logged into an active session. - -Example: USERS="joe bob" -- autoconnect -ONBOOT -yes -Whether the connection should be autoconnected (not only while booting). +a boolean value. - autoconnect-priority -AUTOCONNECT_PRIORITY(+) + auth-timeout +IEEE_8021X_AUTH_TIMEOUT(+) 0 -Connection priority for automatic activation. Connections with higher numbers are preferred when selecting profiles for automatic activation. - -Example: AUTOCONNECT_PRIORITY=20 - -Allowed values: -999 to 999 +Timeout in seconds for the 802.1X authentication. Zero means the global default or 25. - + +autoconnect-retries -AUTOCONNECT_RETRIES(+) - +optional +IEEE_8021X_OPTIONAL(+) default=no - The number of times a connection should be autoactivated before giving up and switching to the next one. - -Example: AUTOCONNECT_RETRIES=1 - -Allowed values: -1 (use global default), 0 (forever) or a positive value +whether the 802.1X authentication is optional +Table 15. 802-3-ethernet setting
++
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description +- multi-connect -MULTI_CONNECT(+) - +port +(none) - whether the profile can be active on multiple devices at a given moment. The values are numbers corresponding to #NMConnectionMultiConnect enum. - -Example: MULTI_CONNECT=3 +The property is not saved by the plugin. - zone -ZONE(+) - +speed +ETHTOOL_OPTS - Trust level of this connection. The string is usually used for a firewall. - -Example: ZONE=Work +Fixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable. - master -MASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, BRIDGE, BRIDGE_UUID +duplex +ETHTOOL_OPTS - Reference to master connection. The variable used depends on the connection type and the value. In general, if the *_UUID variant is present, the variant without *_UUID is ignored. NetworkManager attempts to write both for compatibility with legacy tooling. +Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable. - -slave-type -MASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, DEVICETYPE, BRIDGE, BRIDGE_UUID +auto-negotiate +ETHTOOL_OPTS - Slave type doesn't map directly to a variable, but it is recognized using different variables. MASTER and MASTER_UUID for bonding, TEAM_MASTER, TEAM_MASTER_UUID and DEVICETYPE for teaming, BRIDGE and BRIDGE_UUID for bridging. -- autoconnect-slaves -AUTOCONNECT_SLAVES(+) - -missing variable means global default -Whether slaves of this connection should be auto-connected when this connection is activated. +Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration). - secondaries -SECONDARY_UUIDS(+) - +mac-address +HWADDR - UUID of VPN connections that should be activated together with this connection. +Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device. - gateway-ping-timeout -GATEWAY_PING_TIMEOUT(+) - -0 -If greater than zero, the IP connectivity will be checked by pinging the gateway and waiting for the specified timeout (in seconds). - -Example: GATEWAY_PING_TIMEOUT=5 +cloned-mac-address +MACADDR ++ Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99). - metered -CONNECTION_METERED(+) + generate-mac-address-mask +GENERATE_MAC_ADDRESS_MASK(+) - Whether the device is metered - -Example: CONNECTION_METERED=yes - -Allowed values: yes,no,unknown +the MAC address mask for generating randomized and stable cloned-mac-address. - lldp -LLDP(+) + mac-address-blacklist +HWADDR_BLACKLIST(+) -missing variable means global default -whether LLDP is enabled for the connection - -Example: LLDP=no + + It denies usage of the connection for any device whose address is listed. -Allowed values: boolean value or 'rx' +Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55"- auth-retries -AUTH_RETRIES(+) - -0 -Number of retries for authentication. +mtu +MTU ++ MTU of the interface. - mdns -MDNS(+) - -missing variable means global default -Whether or not mDNS is enabled for the connection - -Example: MDNS=yes + s390-subchannels +SUBCHANNELS ++ Subchannels for IBM S390 hosts. -Allowed values: yes,no,resolve +Example: SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c- llmnr -LLMNR(+) - -missing variable means global default -Whether or not LLMNR is enabled for the connection + s390-nettype +NETTYPE ++ Network type of the S390 host. -Example: LLMNR=yes +Example: NETTYPE=qeth -Allowed values: yes,no,resolve +Allowed values: "qeth", "lcs" or "ctc"- dns-over-tls -DNS_OVER_TLS(+) - -missing variable means global default -Whether or not DNSOverTls is enabled for the connection - -Allowed values: yes,no,opportunistic +s390-options +OPTIONS and PORTNAME, CTCPROTO, ++ S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables. - mptcp-flags -MPTCP_FLAGS(+) - -missing variable means global default -The MPTCP flags that indicate whether MPTCP is enabled and which flags to use for the address endpoints. - -Example: MPTCP_FLAGS="signal,subflow" +wake-on-lan +ETHTOOL_OPTS, ETHTOOL_WAKE_ON_LAN ++ Wake on Lan mode for ethernet. The setting "ignore" is expressed with "ETHTOOL_WAKE_ON_LAN=ignore". Otherwise, the "ETHTOOL_OPTS" variable is set with the value "wol" and several of the characters "p|u|m|b|a|g|s|f|d" as explained in the ethtool manual page. - wait-device-timeout -DEVTIMEOUT(+) - +wake-on-lan-password +ETHTOOL_OPTS - for initscripts compatibility, this variable must be a whole integer. If necessary, NetworkManager stores also a fractional component for the milliseconds. - -Example: DEVTIMEOUT=5 + Password for secure-on based Wake-on-Lan. It is added as "sopass" parameter in the ETHTOOL_OPTS variable. -Allowed values: timeout in seconds. +Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55"- -mud-url -MUD_URL +accept-all-mac-addresses +ACCEPT_ALL_MAC_ADDRESSES - MUD_URL to be sent by device (See RFC 8520). - -Example: https://yourdevice.example.com/model.json - -Allowed values: a valid URL that points to recommended policy for this device -- wait-activation-delay -WAIT_ACTIVATION_DELAY(+) - -- Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. - -Example: WAIT_ACTIVATION_DELAY=5000 - -Allowed values: delay in milliseconds. +Enforce the interface to accept all the packets. -Table 18. dcb setting
-+
Table 16. bond setting
+-
- @@ -1201,129 +1076,19 @@ Allowed values: delay in milliseconds. Default Description -- -app-fcoe-flags -DCB_APP_FCOE_ENABLE, DCB_APP_FCOE_ADVERTISE, DCB_APP_FCOE_WILLING -no -FCOE flags. - -Example: DCB_APP_FCOE_ENABLE=yes DCB_APP_FCOE_ADVERTISE=yes -- -app-fcoe-priority -DCB_APP_FCOE_PRIORITY -- Priority of FCoE frames. - -Allowed values: 0 - 7 -- -app-fcoe-mode -DCB_APP_FCOE_MODE -fabric -FCoE controller mode. - -Allowed values: fabric, vn2vn -- -app-iscsi-flags -DCB_APP_ISCSI_ENABLE, DCB_APP_ISCSI_ADVERTISE, DCB_APP_ISCSI_WILLING -no -iSCSI flags. -- -app-iscsi-priority -DCB_APP_ISCSI_PRIORITY -- Priority of iSCSI frames. - -Allowed values: 0 - 7 -- -app-fip-flags -DCB_APP_FIP_ENABLE, DCB_APP_FIP_ADVERTISE, DCB_APP_FIP_WILLING -no -FIP flags. -- -app-fip-priority -DCB_APP_FIP_PRIORITY -- Priority of FIP frames. - -Allowed values: 0 - 7 -- -priority-flow-control-flags -DCB_PFC_ENABLE, DCB_PFC_ADVERTISE, DCB_PFC_WILLING -no -Priority flow control flags. -- -priority-flow-control -DCB_PFC_UP -- Priority flow control values. String of 8 "0" and "1", where "0". means "do not transmit priority pause", "1" means "transmit pause". - -Example: DCB_PFC_UP=01101110 -- -priority-group-flags -DCB_PG_ENABLE, DCB_PG_ADVERTISE, DCB_PG_WILLING -no -Priority groups flags. -- -priority-group-id -DCB_PG_ID -- Priority groups values. String of eight priorities (0 - 7) or "f" (unrestricted). - -Example: DCB_PG_ID=1205f173 -- -priority-group-bandwidth -DCB_PG_PCT -- Priority groups values. Eight bandwidths (in percent), separated with commas. - -Example: DCB_PG_PCT=10,5,10,15,10,10,10,30 -- -priority-bandwidth -DCB_PG_UPPCT -- Priority values. Eight bandwidths (in percent), separated with commas. The sum of the numbers must be 100. - -Example: DCB_PG_UPPCT=7,13,10,10,15,15,10,20 -- -priority-strict-bandwidth -DCB_PG_STRICT -- Priority values. String of eight "0" or "1", where "0" means "may not utilize all bandwidth", "1" means "may utilize all bandwidth". - -Example: DCB_PG_STRICT=01101110 -- priority-traffic-class -DCB_PG_UP2TC ++ - +Example: BONDING_OPTS="miimon=100 mode=broadcast" +options +BONDING_OPTS - Priority values. String of eight traffic class values (0 - 7). + Bonding options. -Example: DCB_PG_UP2TC=01623701 -- All DCB related configuration is a NetworkManager extension. DCB=yes must be - used explicitly to enable DCB so that the rest of the DCB_* variables can apply. -
--Table 19. ethtool setting
-+
+Table 17. bond-port setting
+
+ @@ -1336,12 +1101,19 @@ Example: DCB_PG_UP2TC=01623701 Default Description -+ queue-id +BONDING_OPTS: queue-id= +0 +Queue ID. + +Allowed values: 0 - 65535 +-Table 20. hostname setting
-+
Table 18. bridge setting
+- -
@@ -1356,288 +1128,231 @@ Example: DCB_PG_UP2TC=01623701 - priority -HOSTNAME_PRIORITY(+) + mac-address +BRIDGE_MACADDR(+) -missing variable means global value or 100 -hostname priority - -Example: HOSTNAME_PRIORITY=50 ++ MAC address of the bridge. Note that this requires a recent kernel support, originally introduced in 3.15 upstream kernel) BRIDGE_MACADDR for bridges is an NM extension. - +from-dhcp -HOSTNAME_FROM_DHCP(+) - -missing variable means global default or 1 -whether the system hostname can be determined from DHCP + stp +STP +no +Span tree protocol participation. ++ priority +BRIDGING_OPTS: priority= +32768 +STP priority. -Example: HOSTNAME_FROM_DHCP=0,1 +Allowed values: 0 - 32768- from-dhcp -HOSTNAME_FROM_DNS_LOOKUP(+) - -missing variable means global default or 1 -whether the system hostname can be determined from reverse DNS lookup + forward-delay +DELAY +15 +STP forwarding delay. -Example: HOSTNAME_FROM_DNS_LOOKUP=0,1 +Allowed values: 2 - 30- - -only-best-device -HOSTNAME_ONLY_FROM_DEFAULT(+) - -missing variable means global default or 1 -whether the hostname can be determined only from devices with the default route + hello-time +BRIDGING_OPTS: hello_time= +2 +STP hello time. -Example: HOSTNAME_ONLY_FROM_DEFAULT=0,1 +Allowed values: 1 - 10--Table 21. infiniband setting
---
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- mac-address -HWADDR -- IBoIP 20-byte hardware address of the device (in traditional hex-digits-and-colons notation). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device. + max-age +BRIDGING_OPTS: max_age= +20 +STP maximum message age. -Example: HWADDR=01:02:03:04:05:06:07:08:09:0A:01:02:03:04:05:06:07:08:09:11 +Allowed values: 6 - 40- mtu -MTU -- MTU of the interface. +ageing-time +BRIDGING_OPTS: ageing_time= +300 +Ethernet MAC ageing time. + +Allowed values: 0 - 1000000 - transport-mode -CONNECTED_MODE -CONNECTED_MODE=no -CONNECTED_MODE=yes for "connected" mode, CONNECTED_MODE=no for "datagram" mode +multicast-snooping +BRIDGING_OPTS: multicast_snooping= +1 +IGMP snooping support. + +Allowed values: 0 or 1 - p-key -PKEY_ID (and PKEY=yes) -PKEY=no -InfiniBand P_Key. The value can be a hex number prefixed with "0x" or a decimal number. When PKEY_ID is specified, PHYSDEV and DEVICE also must be specified. + vlan-filtering +BRIDGING_OPTS: vlan_filtering= +0 +VLAN filtering support. -Example: PKEY=yes PKEY_ID=2 PHYSDEV=mlx4_ib0 DEVICE=mlx4_ib0.8002 +Allowed values: 0 or 1- - -parent -PHYSDEV (PKEY=yes) -PKEY=no -InfiniBand parent device. - -Example: PHYSDEV=ib0 --Table 22. ipv4 setting
--
- -- - - - - - -Property -Ifcfg-rh Variable -Default -Description -- method -BOOTPROTO -none -Method used for IPv4 protocol configuration. + vlan-default-pvid +BRIDGING_OPTS: default_pvid= +1 +default VLAN PVID. -Allowed values: none, dhcp (bootp), static, ibft, autoip, shared +Allowed values: 0 - 4094- -dns -DNS1, DNS2, ... +vlans +BRIDGE_VLANS - List of DNS servers. Even if NetworkManager supports many DNS servers, initscripts and resolver only care about the first three, usually. + List of VLANs on the bridge -Example: DNS1=1.2.3.4 DNS2=10.0.0.254 DNS3=8.8.8.8 -- dns-search -DOMAIN -- List of DNS search domains. +Example: BRIDGE_VLANS="1 pvid untagged,20,300-400 untagged"- addresses -IPADDR, PREFIX (NETMASK), IPADDR1, PREFIX1 (NETMASK1), ... +group-address +BRIDGING_OPTS: group_address= - List of static IP addresses. + STP group address. -Example: IPADDR=10.5.5.23 PREFIX=24 IPADDR1=1.1.1.2 PREFIX1=16 +Example: BRIDGING_OPTS="group_address=01:80:C2:00:00:0A"- -gateway -GATEWAY +vlan-protocol +BRIDGING_OPTS: vlan_protocol= - Gateway IP address. + VLAN filtering protocol. -Example: GATEWAY=10.5.5.1 -- -routes -ADDRESS1, NETMASK1, GATEWAY1, METRIC1, OPTIONS1, ... -- List of static routes. They are not stored in ifcfg-* file, but in route-* file instead. -- -ignore-auto-routes -PEERROUTES(+) - -yes -PEERROUTES has the opposite meaning as 'ignore-auto-routes' property. -- -ignore-auto-dns -PEERDNS -yes -PEERDNS has the opposite meaning as 'ignore-auto-dns' property. -- dhcp-send-hostname -DHCP_SEND_HOSTNAME(+) - -yes -Whether DHCP_HOSTNAME should be sent to the DHCP server. +Example: BRIDGING_OPTS="vlan_protocol=802.1Q"- dhcp-hostname -DHCP_HOSTNAME -- Hostname to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used. +vlan-stats-enabled +BRIDGING_OPTS: vlan_stats_enabled= +0 ++ + +Example: BRIDGING_OPTS="vlan_stats_enabled=1" - never-default -DEFROUTE (GATEWAYDEV in /etc/sysconfig/network) -yes -DEFROUTE=no tells NetworkManager that this connection should not be assigned the default route. DEFROUTE has the opposite meaning as 'never-default' property. +multicast-router +BRIDGING_OPTS: multicast_router= +auto ++ + +Example: BRIDGING_OPTS="multicast_router=enabled" + +Allowed values: auto, enabled, disabled - may-fail -IPV4_FAILURE_FATAL(+) - -no -IPV4_FAILURE_FATAL has the opposite meaning as 'may-fail' property. +multicast-query-use-ifaddr +BRIDGING_OPTS: multicast_query_use_ifaddr= +0 ++ + +Example: BRIDGING_OPTS="multicast_query-use_ifaddr=1" - route-metric -IPV4_ROUTE_METRIC(+) - --1 -IPV4_ROUTE_METRIC is the default IPv4 metric for routes on this connection. If set to -1, a default metric based on the device type is used. +multicast-querier +BRIDGING_OPTS: multicast_querier= +0 ++ + +Example: BRIDGING_OPTS="multicast_querier=1" - route-table -IPV4_ROUTE_TABLE(+) - -0 -IPV4_ROUTE_TABLE enables policy-routing and sets the default routing table. +multicast-hash-max +BRIDGING_OPTS: multicast_hash_max= +4096 ++ + +Example: BRIDGING_OPTS="multicast_hash_max=8192" - dns-options -RES_OPTIONS(+) - -- List of DNS options to be added to /etc/resolv.conf + multicast-last-member-count +BRIDGING_OPTS: multicast_last_member_count= +2 ++ -Example: RES_OPTIONS=ndots:2 timeout:3 +Example: BRIDGING_OPTS="multicast_last_member_count=4"- dns-priority -IPV4_DNS_PRIORITY(+) - -0 -The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used. + multicast-last-member-interval +BRIDGING_OPTS: multicast_last_member_interval= +100 ++ -Example: IPV4_DNS_PRIORITY=20 +Example: BRIDGING_OPTS="multicast_last_member_interval=200"- dhcp-client-id -DHCP_CLIENT_ID(+) - -- A string sent to the DHCP server to identify the local machine. A binary value can be specified using hex notation ('aa:bb:cc'). + multicast-membership-interval +BRIDGING_OPTS: multicast_membership_interval= +26000 ++ -Example: DHCP_CLIENT_ID=ax-srv-1; DHCP_CLIENT_ID=01:44:44:44:44:44:44 +Example: BRIDGING_OPTS="multicast_membership_interval=16000"- dad-timeout -ACD_TIMEOUT(+), ARPING_WAIT -missing variable means global default (config override or zero) -Timeout (in milliseconds for ACD_TIMEOUT or in seconds for ARPING_WAIT) for address conflict detection before configuring IPv4 addresses. 0 turns off the ACD completely, -1 means default value. + multicast-querier-interval +BRIDGING_OPTS: multicast_querier_interval= +25500 ++ -Example: ACD_TIMEOUT=2000 or ARPING_WAIT=2 +Example: BRIDGING_OPTS="multicast_querier_interval=20000"- dhcp-timeout -IPV4_DHCP_TIMEOUT(+) - -- A timeout after which the DHCP transaction fails in case of no response. + multicast-query-interval +BRIDGING_OPTS: multicast_query_interval= +12500 ++ -Example: IPV4_DHCP_TIMEOUT=10 +Example: BRIDGING_OPTS="multicast_query_interval=22500"- dhcp-fqdn -DHCP_FQDN -- FQDN to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used. + multicast-query-response-interval +BRIDGING_OPTS: multicast_query_response_interval= +1000 ++ -Example: DHCP_FQDN=foo.bar.com +Example: BRIDGING_OPTS="multicast_query_response_interval=2000"- dhcp-vendor-class-identifier -DHCP_VENDOR_CLASS_IDENTIFIER(+) - -- The Vendor Class Identifier DHCP option (60). + multicast-startup-query-count +BRIDGING_OPTS: multicast_startup_query_count= +2 ++ -Example: DHCP_VENDOR_CLASS_IDENTIFIER=foo +Example: BRIDGING_OPTS="multicast_startup_query_count=4"- link-local -IPV4_LINK_LOCAL(+) - -- Configure link-local IP address in interaction with method + multicast-startup-query-interval +BRIDGING_OPTS: multicast_startup_query_interval= +3125 ++ -Example: IPV4_LINK_LOCAL=auto +Example: BRIDGING_OPTS="multicast_startup_query_interval=4000"-Table 23. ipv6 setting
-+
Table 19. bridge-port setting
++ +
@@ -1652,181 +1367,288 @@ Example: IPV4_LINK_LOCAL=auto - -method -IPV6INIT, IPV6FORWARDING, IPV6_AUTOCONF, DHCPV6C, IPV6_DISABLED -IPV6INIT=yes; IPV6FORWARDING=no; IPV6_AUTOCONF=!IPV6FORWARDING, DHCPV6=no -Method used for IPv6 protocol configuration. ignore ~ IPV6INIT=no; auto ~ IPV6_AUTOCONF=yes; dhcp ~ IPV6_AUTOCONF=no and DHCPV6C=yes; disabled ~ IPV6_DISABLED=yes -- dns -DNS1, DNS2, ... -- List of DNS servers. NetworkManager uses the variables both for IPv4 and IPv6. +priority +BRIDGING_OPTS: priority= +32 +STP priority. + +Allowed values: 0 - 63 - +dns-search -IPV6_DOMAIN(+) + path-cost +BRIDGING_OPTS: path_cost= +100 +STP cost. + +Allowed values: 1 - 65535 ++ +hairpin-mode +BRIDGING_OPTS: hairpin_mode= +yes +Hairpin mode of the bridge port. ++ + +vlans +BRIDGE_PORT_VLANS ++ List of VLANs on the bridge port + +Example: BRIDGE_PORT_VLANS="1 pvid untagged,20,300-400 untagged" ++Table 20. connection setting
++
+ ++ + + + + + +Property +Ifcfg-rh Variable +Default +Description ++ id +NAME(+) - List of DNS search domains. +User friendly name for the connection profile. - addresses -IPV6ADDR, IPV6ADDR_SECONDARIES +uuid +UUID(+) + - List of static IP addresses. - -Example: IPV6ADDR=ab12:9876::1 IPV6ADDR_SECONDARIES="ab12:9876::2 ab12:9876::3" +UUID for the connection profile. When missing, NetworkManager creates the UUID itself (by hashing the filename). - gateway -IPV6_DEFAULTGW +stable-id +STABLE_ID(+) + - Gateway IP address. - -Example: IPV6_DEFAULTGW=abbe::1 +Token to generate stable IDs. - routes -(none) +interface-name +DEVICE - List of static routes. They are not stored in ifcfg-* file, but in route6-* file instead in the form of command line for 'ip route add'. +Interface name of the device this profile is bound to. The variable can be left out when the profile should apply for more devices. Note that DEVICE can be required for some connection types. - +ignore-auto-routes -IPV6_PEERROUTES(+) + type +TYPE (DEVICETYPE, DEVICE) ++ Base type of the connection. DEVICETYPE is used for teaming connections. + +Example: TYPE=Ethernet; TYPE=Bond; TYPE=Bridge; DEVICETYPE=TeamPort + +Allowed values: Ethernet, Wireless, InfiniBand, Bridge, Bond, Vlan, Team, TeamPort ++ +permissions +USERS(+) ++ Restrict to certain users the access to this connection, and allow the connection to be active only when at least one of the specified users is logged into an active session. + +Example: USERS="joe bob" ++ autoconnect +ONBOOT yes -IPV6_PEERROUTES has the opposite meaning as 'ignore-auto-routes' property. +Whether the connection should be autoconnected (not only while booting). - ignore-auto-dns -IPV6_PEERDNS(+) + autoconnect-priority +AUTOCONNECT_PRIORITY(+) -yes -IPV6_PEERDNS has the opposite meaning as 'ignore-auto-dns' property. +0 +Connection priority for automatic activation. Connections with higher numbers are preferred when selecting profiles for automatic activation. + +Example: AUTOCONNECT_PRIORITY=20 + +Allowed values: -999 to 999 - dhcp-hostname -DHCPV6_HOSTNAME +autoconnect-retries +AUTOCONNECT_RETRIES(+) + - Hostname to send the DHCP server. +The number of times a connection should be autoactivated before giving up and switching to the next one. + +Example: AUTOCONNECT_RETRIES=1 + +Allowed values: -1 (use global default), 0 (forever) or a positive value - dhcp-timeout -IPV6_DHCP_TIMEOUT(+) + multi-connect +MULTI_CONNECT(+) - A timeout after which the DHCP transaction fails in case of no response. + whether the profile can be active on multiple devices at a given moment. The values are numbers corresponding to #NMConnectionMultiConnect enum. -Example: IPV6_DHCP_TIMEOUT=10 +Example: MULTI_CONNECT=3- dhcp-hostname-flags -DHCPV6_HOSTNAME_FLAGS +zone +ZONE(+) + - flags for the DHCP hostname property + Trust level of this connection. The string is usually used for a firewall. -Example: DHCPV6_HOSTNAME_FLAGS=5 +Example: ZONE=Work- never-default -IPV6_DEFROUTE(+), (and IPV6_DEFAULTGW, IPV6_DEFAULTDEV in /etc/sysconfig/network) -IPV6_DEFROUTE=yes (when no variable specified) -IPV6_DEFROUTE=no tells NetworkManager that this connection should not be assigned the default IPv6 route. IPV6_DEFROUTE has the opposite meaning as 'never-default' property. +master +MASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, BRIDGE, BRIDGE_UUID ++ Reference to master connection. The variable used depends on the connection type and the value. In general, if the *_UUID variant is present, the variant without *_UUID is ignored. NetworkManager attempts to write both for compatibility with legacy tooling. - may-fail -IPV6_FAILURE_FATAL(+) - -no -IPV6_FAILURE_FATAL has the opposite meaning as 'may-fail' property. +slave-type +MASTER, MASTER_UUID, TEAM_MASTER, TEAM_MASTER_UUID, DEVICETYPE, BRIDGE, BRIDGE_UUID ++ Slave type doesn't map directly to a variable, but it is recognized using different variables. MASTER and MASTER_UUID for bonding, TEAM_MASTER, TEAM_MASTER_UUID and DEVICETYPE for teaming, BRIDGE and BRIDGE_UUID for bridging. - route-metric -IPV6_ROUTE_METRIC(+) + autoconnect-slaves +AUTOCONNECT_SLAVES(+) --1 -IPV6_ROUTE_METRIC is the default IPv6 metric for routes on this connection. If set to -1, a default metric based on the device type is used. +missing variable means global default +Whether slaves of this connection should be auto-connected when this connection is activated. - route-table -IPV6_ROUTE_TABLE(+) + secondaries +SECONDARY_UUIDS(+) -0 -IPV6_ROUTE_TABLE enables policy-routing and sets the default routing table. ++ UUID of VPN connections that should be activated together with this connection. - dns-priority -IPV6_DNS_PRIORITY(+) + gateway-ping-timeout +GATEWAY_PING_TIMEOUT(+) 0 -The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used. + If greater than zero, the IP connectivity will be checked by pinging the gateway and waiting for the specified timeout (in seconds). -Example: IPV6_DNS_PRIORITY=20 +Example: GATEWAY_PING_TIMEOUT=5- dns-options -IPV6_RES_OPTIONS(+) + metered +CONNECTION_METERED(+) - List of DNS options to be added to /etc/resolv.conf + Whether the device is metered -Example: IPV6_RES_OPTIONS=ndots:2 timeout:3 +Example: CONNECTION_METERED=yes + +Allowed values: yes,no,unknown- ip6-privacy -IPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP(+) + lldp +LLDP(+) -no -Configure IPv6 Privacy Extensions for SLAAC (RFC4941). + missing variable means global default +whether LLDP is enabled for the connection -Example: IPV6_PRIVACY=rfc3041 IPV6_PRIVACY_PREFER_PUBLIC_IP=yes +Example: LLDP=no -Allowed values: IPV6_PRIVACY: no, yes (rfc3041 or rfc4941); IPV6_PRIVACY_PREFER_PUBLIC_IP: yes, no +Allowed values: boolean value or 'rx'- +addr-gen-mode -IPV6_ADDR_GEN_MODE -"default-or-eui64" -Configure IPv6 Stable Privacy addressing for SLAAC (RFC7217). + auth-retries +AUTH_RETRIES(+) + +0 +Number of retries for authentication. ++ mdns +MDNS(+) + +missing variable means global default +Whether or not mDNS is enabled for the connection -Example: IPV6_ADDR_GEN_MODE=stable-privacy +Example: MDNS=yes -Allowed values: IPV6_ADDR_GEN_MODE: default, default-or-eui64, eui64, stable-privacy +Allowed values: yes,no,resolve- token -IPV6_TOKEN -- The IPv6 tokenized interface identifier token + llmnr +LLMNR(+) + +missing variable means global default +Whether or not LLMNR is enabled for the connection -Example: IPV6_TOKEN=::53 +Example: LLMNR=yes + +Allowed values: yes,no,resolve- dhcp-timeout -IPV6_RA_TIMEOUT(+) + dns-over-tls +DNS_OVER_TLS(+) -- A timeout for waiting Router Advertisements in seconds. + missing variable means global default +Whether or not DNSOverTls is enabled for the connection -Example: IPV6_RA_TIMEOUT=10 +Allowed values: yes,no,opportunistic- +dhcp-duid -DHCPV6_DUID(+) + mptcp-flags +MPTCP_FLAGS(+) -- A string sent to the DHCPv6 server to identify the local machine. Apart from the special values "lease", "stable-llt", "stable-ll", "stable-uuid", "llt" and "ll" a binary value in hex format is expected. An hex string where each octet is separated by a colon is also accepted. + +missing variable means global default +The MPTCP flags that indicate whether MPTCP is enabled and which flags to use for the address endpoints. -Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DUID=03:01:de:ad:be:ef:00:01 +Example: MPTCP_FLAGS="signal,subflow"+ +wait-device-timeout +DEVTIMEOUT(+) + ++ for initscripts compatibility, this variable must be a whole integer. If necessary, NetworkManager stores also a fractional component for the milliseconds. + +Example: DEVTIMEOUT=5 + +Allowed values: timeout in seconds. ++ +mud-url +MUD_URL ++ MUD_URL to be sent by device (See RFC 8520). + +Example: https://yourdevice.example.com/model.json + +Allowed values: a valid URL that points to recommended policy for this device ++ wait-activation-delay +WAIT_ACTIVATION_DELAY(+) + ++ Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event. + +Example: WAIT_ACTIVATION_DELAY=5000 + +Allowed values: delay in milliseconds. -Table 24. match setting
-+
Table 21. dcb setting
+-
@@ -1839,19 +1661,129 @@ Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DU Default Description -- +path -MATCH_PATH ++ +app-fcoe-flags +DCB_APP_FCOE_ENABLE, DCB_APP_FCOE_ADVERTISE, DCB_APP_FCOE_WILLING +no +FCOE flags. + +Example: DCB_APP_FCOE_ENABLE=yes DCB_APP_FCOE_ADVERTISE=yes ++ +Allowed values: 0 - 7 + +app-fcoe-priority +DCB_APP_FCOE_PRIORITY - space-separated list of paths to match against the udev property ID_PATHS of devices + Priority of FCoE frames. -Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0" -+ +app-fcoe-mode +DCB_APP_FCOE_MODE +fabric +FCoE controller mode. + +Allowed values: fabric, vn2vn ++ +app-iscsi-flags +DCB_APP_ISCSI_ENABLE, DCB_APP_ISCSI_ADVERTISE, DCB_APP_ISCSI_WILLING +no +iSCSI flags. ++ +app-iscsi-priority +DCB_APP_ISCSI_PRIORITY ++ Priority of iSCSI frames. + +Allowed values: 0 - 7 ++ +app-fip-flags +DCB_APP_FIP_ENABLE, DCB_APP_FIP_ADVERTISE, DCB_APP_FIP_WILLING +no +FIP flags. ++ +app-fip-priority +DCB_APP_FIP_PRIORITY ++ Priority of FIP frames. + +Allowed values: 0 - 7 ++ +priority-flow-control-flags +DCB_PFC_ENABLE, DCB_PFC_ADVERTISE, DCB_PFC_WILLING +no +Priority flow control flags. ++ +priority-flow-control +DCB_PFC_UP ++ Priority flow control values. String of 8 "0" and "1", where "0". means "do not transmit priority pause", "1" means "transmit pause". + +Example: DCB_PFC_UP=01101110 ++ +priority-group-flags +DCB_PG_ENABLE, DCB_PG_ADVERTISE, DCB_PG_WILLING +no +Priority groups flags. ++ +priority-group-id +DCB_PG_ID ++ Priority groups values. String of eight priorities (0 - 7) or "f" (unrestricted). + +Example: DCB_PG_ID=1205f173 ++ +priority-group-bandwidth +DCB_PG_PCT ++ Priority groups values. Eight bandwidths (in percent), separated with commas. + +Example: DCB_PG_PCT=10,5,10,15,10,10,10,30 ++ +priority-bandwidth +DCB_PG_UPPCT ++ Priority values. Eight bandwidths (in percent), separated with commas. The sum of the numbers must be 100. + +Example: DCB_PG_UPPCT=7,13,10,10,15,15,10,20 ++ +priority-strict-bandwidth +DCB_PG_STRICT ++ Priority values. String of eight "0" or "1", where "0" means "may not utilize all bandwidth", "1" means "may utilize all bandwidth". + +Example: DCB_PG_STRICT=01101110 ++ +priority-traffic-class +DCB_PG_UP2TC ++ Priority values. String of eight traffic class values (0 - 7). + +Example: DCB_PG_UP2TC=01623701 +-Table 25. ovs-bridge setting
-+
+ All DCB related configuration is a NetworkManager extension. DCB=yes must be + used explicitly to enable DCB so that the rest of the DCB_* variables can apply. +
++Table 22. ethtool setting
+
@@ -1868,8 +1800,8 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0" -Table 26. ovs-dpdk setting
-+
Table 23. hostname setting
+
+ + @@ -1882,12 +1814,49 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0" Default Description -+ +priority +HOSTNAME_PRIORITY(+) + +missing variable means global value or 100 +hostname priority + +Example: HOSTNAME_PRIORITY=50 ++ +from-dhcp +HOSTNAME_FROM_DHCP(+) + +missing variable means global default or 1 +whether the system hostname can be determined from DHCP + +Example: HOSTNAME_FROM_DHCP=0,1 ++ +from-dns-lookup +HOSTNAME_FROM_DNS_LOOKUP(+) + +missing variable means global default or 1 +whether the system hostname can be determined from reverse DNS lookup + +Example: HOSTNAME_FROM_DNS_LOOKUP=0,1 ++ +only-best-device +HOSTNAME_ONLY_FROM_DEFAULT(+) + +missing variable means global default or 1 +whether the hostname can be determined only from devices with the default route + +Example: HOSTNAME_ONLY_FROM_DEFAULT=0,1 +-Table 27. ovs-external-ids setting
-+
Table 24. infiniband setting
+
+ + @@ -1900,66 +1869,49 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0" Default Description -+ +mac-address +HWADDR ++ IBoIP 20-byte hardware address of the device (in traditional hex-digits-and-colons notation). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device. + +Example: HWADDR=01:02:03:04:05:06:07:08:09:0A:01:02:03:04:05:06:07:08:09:11 ++ +mtu +MTU ++ MTU of the interface. ++ +transport-mode +CONNECTED_MODE +CONNECTED_MODE=no +CONNECTED_MODE=yes for "connected" mode, CONNECTED_MODE=no for "datagram" mode ++ +p-key +PKEY_ID (and PKEY=yes) +PKEY=no +InfiniBand P_Key. The value can be a hex number prefixed with "0x" or a decimal number. When PKEY_ID is specified, PHYSDEV and DEVICE also must be specified. + +Example: PKEY=yes PKEY_ID=2 PHYSDEV=mlx4_ib0 DEVICE=mlx4_ib0.8002 ++ +parent +PHYSDEV (PKEY=yes) +PKEY=no +InfiniBand parent device. + +Example: PHYSDEV=ib0 +--Table 28. ovs-interface setting
---
- -- - - - - - -Property -Ifcfg-rh Variable -Default -Description ---Table 29. ovs-patch setting
---
- -- - - - - - -Property -Ifcfg-rh Variable -Default -Description ---Table 30. ovs-port setting
---
- -- - - - - - -Property -Ifcfg-rh Variable -Default -Description --Table 31. proxy setting
-+
Table 25. ipv4 setting
+- -
@@ -1975,126 +1927,192 @@ Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0" method -PROXY_METHOD(+) - +BOOTPROTO none -Method for proxy configuration. For "auto", WPAD is used for proxy configuration, or set the PAC file via PAC_URL or PAC_SCRIPT. + Method used for IPv4 protocol configuration. -Allowed values: none, auto +Allowed values: none, dhcp (bootp), static, ibft, autoip, shared- +browser-only -BROWSER_ONLY(+) + dns +DNS1, DNS2, ... ++ List of DNS servers. Even if NetworkManager supports many DNS servers, initscripts and resolver only care about the first three, usually. + +Example: DNS1=1.2.3.4 DNS2=10.0.0.254 DNS3=8.8.8.8 ++ +dns-search +DOMAIN ++ List of DNS search domains. ++ +addresses +IPADDR, PREFIX (NETMASK), IPADDR1, PREFIX1 (NETMASK1), ... ++ List of static IP addresses. + +Example: IPADDR=10.5.5.23 PREFIX=24 IPADDR1=1.1.1.2 PREFIX1=16 ++ +gateway +GATEWAY ++ Gateway IP address. + +Example: GATEWAY=10.5.5.1 ++ +routes +ADDRESS1, NETMASK1, GATEWAY1, METRIC1, OPTIONS1, ... ++ List of static routes. They are not stored in ifcfg-* file, but in route-* file instead. ++ +ignore-auto-routes +PEERROUTES(+) + +yes +PEERROUTES has the opposite meaning as 'ignore-auto-routes' property. ++ +ignore-auto-dns +PEERDNS +yes +PEERDNS has the opposite meaning as 'ignore-auto-dns' property. ++ +dhcp-send-hostname +DHCP_SEND_HOSTNAME(+) + +yes +Whether DHCP_HOSTNAME should be sent to the DHCP server. ++ +dhcp-hostname +DHCP_HOSTNAME ++ Hostname to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used. ++ +never-default +DEFROUTE (GATEWAYDEV in /etc/sysconfig/network) +yes +DEFROUTE=no tells NetworkManager that this connection should not be assigned the default route. DEFROUTE has the opposite meaning as 'never-default' property. ++ may-fail +IPV4_FAILURE_FATAL(+) no -Whether the proxy configuration is for browser only. +IPV4_FAILURE_FATAL has the opposite meaning as 'may-fail' property. - +pac-url -PAC_URL(+) + route-metric +IPV4_ROUTE_METRIC(+) + +-1 +IPV4_ROUTE_METRIC is the default IPv4 metric for routes on this connection. If set to -1, a default metric based on the device type is used. ++ +route-table +IPV4_ROUTE_TABLE(+) + +0 +IPV4_ROUTE_TABLE enables policy-routing and sets the default routing table. ++ dns-options +RES_OPTIONS(+) - URL for PAC file. + List of DNS options to be added to /etc/resolv.conf -Example: PAC_URL=http://wpad.mycompany.com/wpad.dat +Example: RES_OPTIONS=ndots:2 timeout:3- +pac-script -PAC_SCRIPT(+) + dns-priority +IPV4_DNS_PRIORITY(+) + +0 +The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used. + +Example: IPV4_DNS_PRIORITY=20 ++ +auto-route-ext-gw +IPV4_AUTO_ROUTE_EXT_GW(+) + +yes +VPN connections will default to add the route automatically unless this setting is set to %FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to %TRUE has no effect. ++ - -dhcp-client-id +DHCP_CLIENT_ID(+) - The PAC script. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function. + A string sent to the DHCP server to identify the local machine. A binary value can be specified using hex notation ('aa:bb:cc'). -Example: PAC_SCRIPT="function FindProxyForURL (url, host) { return 'PROXY proxy.example.com:8080; DIRECT'; }" +Example: DHCP_CLIENT_ID=ax-srv-1; DHCP_CLIENT_ID=01:44:44:44:44:44:44--Table 32. sriov setting
---
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- +total-vfs -SRIOV_TOTAL_VFS(+) + dad-timeout +ACD_TIMEOUT(+), ARPING_WAIT +missing variable means global default (config override or zero) +Timeout (in milliseconds for ACD_TIMEOUT or in seconds for ARPING_WAIT) for address conflict detection before configuring IPv4 addresses. 0 turns off the ACD completely, -1 means default value. + +Example: ACD_TIMEOUT=2000 or ARPING_WAIT=2 ++ dhcp-timeout +IPV4_DHCP_TIMEOUT(+) - The total number of virtual functions to create + A timeout after which the DHCP transaction fails in case of no response. -Example: SRIOV_TOTAL_VFS=16 +Example: IPV4_DHCP_TIMEOUT=10- vfs -SRIOV_VF1(+), SRIOV_VF2(+), ... +dhcp-hostname-flags +DHCP_HOSTNAME_FLAGS - SR-IOV virtual function descriptors + flags for the DHCP hostname and FQDN properties -Example: SRIOV_VF10="mac=00:11:22:33:44:55", ... +Example: DHCP_HOSTNAME_FLAGS=5- - -autoprobe-drivers -SRIOV_AUTOPROBE_DRIVERS(+) - -missing variable means global default -Whether to autoprobe virtual functions by a compatible driver + dhcp-fqdn +DHCP_FQDN ++ FQDN to send to the DHCP server. When both DHCP_HOSTNAME and DHCP_FQDN are specified only the latter is used. -Example: SRIOV_AUTOPROBE_DRIVERS=0,1 +Example: DHCP_FQDN=foo.bar.com-Table 33. tc setting
--
- -- - - - - -Property -Ifcfg-rh Variable -Default -Description -- qdiscs -QDISC1(+), QDISC2(+), ..., TC_COMMIT(+) + dhcp-vendor-class-identifier +DHCP_VENDOR_CLASS_IDENTIFIER(+) - Queueing disciplines to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'. + The Vendor Class Identifier DHCP option (60). -Example: QDISC1=ingress, QDISC2="root handle 1234: fq_codel" +Example: DHCP_VENDOR_CLASS_IDENTIFIER=foo- qdiscs -FILTER1(+), FILTER2(+), ..., TC_COMMIT(+) + link-local +IPV4_LINK_LOCAL(+) - Traffic filters to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'. + Configure link-local IP address in interaction with method -Example: FILTER1="parent ffff: matchall action simple sdata Input", ... +Example: IPV4_LINK_LOCAL=auto-Table 34. team-port setting
-+
Table 26. ipv6 setting
++ +
@@ -2107,17 +2125,190 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu Default Description -- -config -TEAM_PORT_CONFIG -- Team port configuration in JSON. See man teamd.conf for details. -+ +method +IPV6INIT, IPV6FORWARDING, IPV6_AUTOCONF, DHCPV6C, IPV6_DISABLED +IPV6INIT=yes; IPV6FORWARDING=no; IPV6_AUTOCONF=!IPV6FORWARDING, DHCPV6=no +Method used for IPv6 protocol configuration. ignore ~ IPV6INIT=no; auto ~ IPV6_AUTOCONF=yes; dhcp ~ IPV6_AUTOCONF=no and DHCPV6C=yes; disabled ~ IPV6_DISABLED=yes ++ +dns +DNS1, DNS2, ... ++ List of DNS servers. NetworkManager uses the variables both for IPv4 and IPv6. ++ +dns-search +IPV6_DOMAIN(+) + ++ List of DNS search domains. ++ +addresses +IPV6ADDR, IPV6ADDR_SECONDARIES ++ List of static IP addresses. + +Example: IPV6ADDR=ab12:9876::1 IPV6ADDR_SECONDARIES="ab12:9876::2 ab12:9876::3" ++ +gateway +IPV6_DEFAULTGW ++ Gateway IP address. + +Example: IPV6_DEFAULTGW=abbe::1 ++ +routes +(none) ++ List of static routes. They are not stored in ifcfg-* file, but in route6-* file instead in the form of command line for 'ip route add'. ++ +ignore-auto-routes +IPV6_PEERROUTES(+) + +yes +IPV6_PEERROUTES has the opposite meaning as 'ignore-auto-routes' property. ++ +ignore-auto-dns +IPV6_PEERDNS(+) + +yes +IPV6_PEERDNS has the opposite meaning as 'ignore-auto-dns' property. ++ +dhcp-hostname +DHCPV6_HOSTNAME ++ Hostname to send the DHCP server. ++ +dhcp-timeout +IPV6_DHCP_TIMEOUT(+) + ++ A timeout after which the DHCP transaction fails in case of no response. + +Example: IPV6_DHCP_TIMEOUT=10 ++ +dhcp-hostname-flags +DHCPV6_HOSTNAME_FLAGS ++ flags for the DHCP hostname property + +Example: DHCPV6_HOSTNAME_FLAGS=5 ++ +never-default +IPV6_DEFROUTE(+), (and IPV6_DEFAULTGW, IPV6_DEFAULTDEV in /etc/sysconfig/network) +IPV6_DEFROUTE=yes (when no variable specified) +IPV6_DEFROUTE=no tells NetworkManager that this connection should not be assigned the default IPv6 route. IPV6_DEFROUTE has the opposite meaning as 'never-default' property. ++ +may-fail +IPV6_FAILURE_FATAL(+) + +no +IPV6_FAILURE_FATAL has the opposite meaning as 'may-fail' property. ++ +route-metric +IPV6_ROUTE_METRIC(+) + +-1 +IPV6_ROUTE_METRIC is the default IPv6 metric for routes on this connection. If set to -1, a default metric based on the device type is used. ++ +route-table +IPV6_ROUTE_TABLE(+) + +0 +IPV6_ROUTE_TABLE enables policy-routing and sets the default routing table. ++ +dns-priority +IPV6_DNS_PRIORITY(+) + +0 +The priority for DNS servers of this connection. Lower values have higher priority. If zero, the default value will be used (50 for VPNs, 100 for other connections). A negative value prevents DNS from other connections with greater values to be used. + +Example: IPV6_DNS_PRIORITY=20 ++ +dns-options +IPV6_RES_OPTIONS(+) + ++ List of DNS options to be added to /etc/resolv.conf + +Example: IPV6_RES_OPTIONS=ndots:2 timeout:3 ++ +auto-route-ext-gw +IPV6_AUTO_ROUTE_EXT_GW(+) + +yes +VPN connections will default to add the route automatically unless this setting is set to %FALSE. For other connection types, adding such an automatic route is currently not supported and setting this to %TRUE has no effect. ++ +ip6-privacy +IPV6_PRIVACY, IPV6_PRIVACY_PREFER_PUBLIC_IP(+) + +no +Configure IPv6 Privacy Extensions for SLAAC (RFC4941). + +Example: IPV6_PRIVACY=rfc3041 IPV6_PRIVACY_PREFER_PUBLIC_IP=yes + +Allowed values: IPV6_PRIVACY: no, yes (rfc3041 or rfc4941); IPV6_PRIVACY_PREFER_PUBLIC_IP: yes, no ++ +addr-gen-mode +IPV6_ADDR_GEN_MODE +"default-or-eui64" +Configure IPv6 Stable Privacy addressing for SLAAC (RFC7217). + +Example: IPV6_ADDR_GEN_MODE=stable-privacy + +Allowed values: IPV6_ADDR_GEN_MODE: default, default-or-eui64, eui64, stable-privacy ++ +token +IPV6_TOKEN ++ The IPv6 tokenized interface identifier token + +Example: IPV6_TOKEN=::53 ++ +ra-timeout +IPV6_RA_TIMEOUT(+) + ++ A timeout for waiting Router Advertisements in seconds. + +Example: IPV6_RA_TIMEOUT=10 ++ + +dhcp-duid +DHCPV6_DUID(+) + ++ A string sent to the DHCPv6 server to identify the local machine. Apart from the special values "lease", "stable-llt", "stable-ll", "stable-uuid", "llt" and "ll" a binary value in hex format is expected. An hex string where each octet is separated by a colon is also accepted. + +Example: DHCPV6_DUID=LL; DHCPV6_DUID=0301deadbeef0001; DHCPV6_DUID=03:01:de:ad:be:ef:00:01 +-Table 35. team setting
-+
Table 27. loopback setting
+
@@ -2131,16 +2322,16 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu Description - config -TEAM_CONFIG +mtu +MTU - Team configuration in JSON. See man teamd.conf for details. +MTU of the interface. -Table 36. user setting
-+
Table 28. match setting
+
@@ -2154,18 +2345,18 @@ Example: FILTER1="parent ffff: matchall action simple sdata Inpu Description - data -NM_USER_* +path +MATCH_PATH - each key/value pair is stored as a separate variable with name composed by concatenating NM_USER_ with the encoded key. The key is encoded by substituting lowercase letters with uppercase and prepending uppercase letters with an underscore. A dot is encoded as a double underscore. Remaining characters are encoded as underscore followed by a 3 digit octal representation of the character. + space-separated list of paths to match against the udev property ID_PATHS of devices -Example: NM_USER_FOO__BAR=something +Example: MATCH_PATH="pci-0000:01:00.0 pci-0000:0c:00.0"-Table 37. veth setting
-+
Table 29. ovs-bridge setting
+
@@ -2182,8 +2373,8 @@ Example: NM_USER_FOO__BAR=something -Table 38. vlan setting
-+
Table 30. ovs-dpdk setting
+
- @@ -2196,57 +2387,12 @@ Example: NM_USER_FOO__BAR=something Default Description -- -parent -DEVICE or PHYSDEV -- Parent interface of the VLAN. -- -id -VLAN_ID, DEVICE. -- VLAN identifier. If VLAN_ID is not set, it is attempted to be detected from the suffix of DEVICE=. Note that older versions of NetworkManager had a bug where they would prefer the detected ID from the DEVICE over VLAN_ID. -- -flags -GVRP, MVRP, VLAN_FLAGS -- VLAN flags. - -Allowed values: "yes or "no" for GVRP and MVRP; "LOOSE_BINDING" and "NO_REORDER_HDR" for VLAN_FLAGS -- -ingress-priority-map -VLAN_INGRESS_PRIORITY_MAP -- Ingress priority mapping. - -Example: VLAN_INGRESS_PRIORITY_MAP=4:2,3:5 -- -egress-priority-map -VLAN_EGRESS_PRIORITY_MAP -- Egress priority mapping. - -Example: VLAN_EGRESS_PRIORITY_MAP=5:4,4:1,3:7 -- - +interface-name -PHYSDEV and VLAN_ID, or DEVICE -- VLAN interface name. If all variables are set, parent device from PHYSDEV takes precedence over DEVICE, but VLAN id from DEVICE takes precedence over VLAN_ID. - -Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12 --Table 39. vrf setting
-+
Table 31. ovs-external-ids setting
+
@@ -2263,8 +2409,8 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12 -Table 40. wifi-p2p setting
-+
Table 32. ovs-interface setting
+
@@ -2281,8 +2427,8 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12 -Table 41. 802-3-ethernet setting
-+
Table 33. ovs-other-config setting
+
- @@ -2295,115 +2441,12 @@ Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12 Default Description -- -port -(none) -- The property is not saved by the plugin. -- -speed -ETHTOOL_OPTS -- Fixed speed for the ethernet link. It is added as "speed" parameter in the ETHTOOL_OPTS variable. -- -duplex -ETHTOOL_OPTS -- Fixed duplex mode for the ethernet link. It is added as "duplex" parameter in the ETHOOL_OPTS variable. -- -auto-negotiate -ETHTOOL_OPTS -- Whether link speed and duplex autonegotiation is enabled. It is not saved only if disabled and no values are provided for the "speed" and "duplex" parameters (skips link configuration). -- -mac-address -HWADDR -- Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device. -- -cloned-mac-address -MACADDR -- Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99). -- -generate-mac-address-mask -GENERATE_MAC_ADDRESS_MASK(+) - -- the MAC address mask for generating randomized and stable cloned-mac-address. -- -mac-address-blacklist -HWADDR_BLACKLIST(+) - -- It denies usage of the connection for any device whose address is listed. - -Example: HWADDR_BLACKLIST="00:22:68:11:69:08 00:11:22:11:44:55" -- -mtu -MTU -- MTU of the interface. -- -s390-subchannels -SUBCHANNELS -- Subchannels for IBM S390 hosts. - -Example: SUBCHANNELS=0.0.b00a,0.0.b00b,0.0.b00c -- -s390-nettype -NETTYPE -- Network type of the S390 host. - -Example: NETTYPE=qeth - -Allowed values: "qeth", "lcs" or "ctc" -- -s390-options -OPTIONS and PORTNAME, CTCPROTO, -- S390 device options. All options go to OPTIONS, except for "portname" and "ctcprot" that have their own variables. -- -wake-on-lan -ETHTOOL_OPTS, ETHTOOL_WAKE_ON_LAN -- Wake on Lan mode for ethernet. The setting "ignore" is expressed with "ETHTOOL_WAKE_ON_LAN=ignore". Otherwise, the "ETHTOOL_OPTS" variable is set with the value "wol" and several of the characters "p|u|m|b|a|g|s|f|d" as explained in the ethtool manual page. -- -wake-on-lan-password -ETHTOOL_OPTS -- Password for secure-on based Wake-on-Lan. It is added as "sopass" parameter in the ETHTOOL_OPTS variable. - -Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55" -- - +accept-all-mac-addresses -ACCEPT_ALL_MAC_ADDRESSES -- Enforce the interface to accept all the packets. --Table 42. wireguard setting
-+
Table 34. ovs-patch setting
+
@@ -2420,8 +2463,26 @@ Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55" -Table 43. 802-11-wireless-security setting
-+
Table 35. ovs-port setting
++ ++
+ ++ + + + + + +Property +Ifcfg-rh Variable +Default +Description +++Table 36. proxy setting
++
@@ -2436,174 +2497,216 @@ Example: ETHTOOL_OPTS="wol gs sopass 00:11:22:33:44:55" - -key-mgmt -KEY_MGMT(+) - -- Key management method. - -Allowed values: none, ieee8021x, owe, wpa-psk, sae, wpa-eap, wpa-eap-suite-b-192 -- -wep-tx-keyidx -DEFAULTKEY -1 -Index of active WEP key. Note that in ifcfg format the index starts counting at 1, while NetworkManager API otherwise is zero based. - -Allowed values: 1, 2, 3, 4 -- auth-alg -SECURITYMODE(+) + method +PROXY_METHOD(+) -- Authentication algorithm for WEP. + none +Method for proxy configuration. For "auto", WPAD is used for proxy configuration, or set the PAC file via PAC_URL or PAC_SCRIPT. -Allowed values: restricted, open, leap +Allowed values: none, auto- proto -WPA_ALLOW_WPA(+), WPA_ALLOW_WPA2(+) + browser-only +BROWSER_ONLY(+) no -Allowed WPA protocols, WPA and WPA2 (RSN). - -Allowed values: yes, no +Whether the proxy configuration is for browser only. - pairwise -CIPHER_PAIRWISE(+) + pac-url +PAC_URL(+) - Restrict pairwise encryption algorithms, specified as a space separated list. + URL for PAC file. -Allowed values: CCMP, TKIP +Example: PAC_URL=http://wpad.mycompany.com/wpad.dat- + +group -CIPHER_GROUP(+) + pac-script +PAC_SCRIPT(+) - Restrict group/broadcast encryption algorithms, specified as a space separated list. + The PAC script. This is an UTF-8 encoded javascript code that defines a FindProxyForURL() function. -Allowed values: CCMP, TKIP, WEP40, WEP104 +Example: PAC_SCRIPT="function FindProxyForURL (url, host) { return 'PROXY proxy.example.com:8080; DIRECT'; }"++Table 37. sriov setting
+++
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description +- pmf -PMF(+) + total-vfs +SRIOV_TOTAL_VFS(+) - Enables or disables PMF (802.11w) - -Example: PMF=required + The total number of virtual functions to create -Allowed values: default, disable, optional, required +Example: SRIOV_TOTAL_VFS=16- leap-username -IEEE_8021X_IDENTITY(+) - +vfs +SRIOV_VF1(+), SRIOV_VF2(+), ... - Login name for LEAP. +SR-IOV virtual function descriptors + +Example: SRIOV_VF10="mac=00:11:22:33:44:55", ... - + +wep-key0 -KEY1, KEY_PASSPHRASE1(+) + autoprobe-drivers +SRIOV_AUTOPROBE_DRIVERS(+) -- The first WEP key (used in most networks). See also DEFAULTKEY for key index. +missing variable means global default +Whether to autoprobe virtual functions by a compatible driver + +Example: SRIOV_AUTOPROBE_DRIVERS=0,1 ++Table 38. tc setting
+++
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description +- wep-key1 -KEY2, KEY_PASSPHRASE2(+) + qdiscs +QDISC1(+), QDISC2(+), ..., TC_COMMIT(+) - WEP key with index 1. See also DEFAULTKEY for key index. +Queueing disciplines to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'. + +Example: QDISC1=ingress, QDISC2="root handle 1234: fq_codel" - -wep-key2 -KEY3, KEY_PASSPHRASE3(+) + tfilters +FILTER1(+), FILTER2(+), ..., TC_COMMIT(+) - WEP key with index 2. See also DEFAULTKEY for key index. +Traffic filters to set on the interface. When no QDISC1, QDISC2, ..., FILTER1, FILTER2, ... keys are present, NetworkManager doesn't touch qdiscs and filters present on the interface, unless TC_COMMIT is set to 'yes'. + +Example: FILTER1="parent ffff: matchall action simple sdata Input", ... - -wep-key3 -KEY4, KEY_PASSPHRASE4(+) - -- WEP key with index 3. See also DEFAULTKEY for key index. -- -wep-key-flags -WEP_KEY_FLAGS(+) - -- Password flags for KEY<i>, KEY_PASSPHRASE<i> password. (see the section called “Secret flag types:” for _FLAGS values) -- -psk -WPA_PSK -- Pre-Shared-Key for WPA networks. -- -psk-flags -WPA_PSK_FLAGS(+) - -- Password flags for WPA_PSK_FLAGS. (see the section called “Secret flag types:” for _FLAGS values) - -Example: WPA_PSK_FLAGS=user -- -leap-password -IEEE_8021X_PASSWORD(+) - -- Password for LEAP. It can also go to "key-" lookaside file, or it can be owned by a secret agent. -- -leap-password-flags -IEEE_8021X_PASSWORD_FLAGS(+) - -- Password flags for IEEE_8021X_PASSWORD_FLAGS. (see the section called “Secret flag types:” for _FLAGS values) -- +wep-key-type -KEY<i> or KEY_PASSPHRASE<i>(+); KEY_TYPE(+) - +++Table 39. team setting
+++
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description ++ -config +TEAM_CONFIG - KEY is used for "key" type (10 or 26 hexadecimal characters, or 5 or 13 character string prefixed with "s:"). KEY_PASSPHRASE is used for WEP passphrases. KEY_TYPE specifies the key type and can be either 'key' or 'passphrase'. KEY_TYPE is redundant and can be omitted. - -Example: KEY1=s:ahoj, KEY1=0a1c45bc02, KEY_PASSPHRASE1=mysupersecretkey -- +wps-method -WPS_METHOD +Team configuration in JSON. See man teamd.conf for details. +++Table 40. team-port setting
+++
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description ++ -config +TEAM_PORT_CONFIG - Used to control the WPS methods to be used Valid values are "default", "auto", "disabled", "pin" and "pbc". If omitted, whatver the AP announces is used. - -Example: WPS_METHOD=disabled, WPS_METHOD="pin pbc" -- +fils -FILS(+) - +Team port configuration in JSON. See man teamd.conf for details. ++Table 41. user setting
++
+ ++ + + + + +Property +Ifcfg-rh Variable +Default +Description ++ - +Example: NM_USER_FOO__BAR=something +data +NM_USER_* - Enables or disables FILS (802.11ai) - -Example: FILS=required + each key/value pair is stored as a separate variable with name composed by concatenating NM_USER_ with the encoded key. The key is encoded by substituting lowercase letters with uppercase and prepending uppercase letters with an underscore. A dot is encoded as a double underscore. Remaining characters are encoded as underscore followed by a 3 digit octal representation of the character. -Allowed values: default, disable, optional, required --Table 44. 802-11-wireless setting
-+
Table 42. veth setting
++ ++
+ ++ + + + + + +Property +Ifcfg-rh Variable +Default +Description ++Table 43. vlan setting
+
@@ -2618,148 +2721,116 @@ Allowed values: default, disable, optional, required - -ssid -ESSID -- SSID of Wi-Fi network. - -Example: ESSID="Quick Net" -- mode -MODE +parent +DEVICE or PHYSDEV - Wi-Fi network mode. - -Allowed values: Ad-Hoc, Managed (Auto) [case insensitive] +Parent interface of the VLAN. - band -BAND(+) - +id +VLAN_ID, DEVICE. - BAND alone is honored, but CHANNEL overrides BAND since it implies a band. - -Example: BAND=bg - -Allowed values: a, bg +VLAN identifier. If VLAN_ID is not set, it is attempted to be detected from the suffix of DEVICE=. Note that older versions of NetworkManager had a bug where they would prefer the detected ID from the DEVICE over VLAN_ID. - channel -CHANNEL +flags +GVRP, MVRP, VLAN_FLAGS - Channel used for the Wi-Fi communication. Channels greater than 14 mean "a" band, otherwise the band is "bg". + VLAN flags. -Example: CHANNEL=6 +Allowed values: "yes or "no" for GVRP and MVRP; "LOOSE_BINDING" and "NO_REORDER_HDR" for VLAN_FLAGS- -bssid -BSSID(+) - +protocol +VLAN_PROTOCOL - Restricts association only to a single AP. + VLAN protocol. -Example: BSSID=00:1E:BD:64:83:21 -- -rate -(none) -- This property is not handled by ifcfg-rh plugin. -- tx-power -(none) -- This property is not handled by ifcfg-rh plugin. +Example: VLAN_PROTOCOL="802.1ad"- -mac-address -HWADDR -- Hardware address of the device in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:05). Note that for initscripts this is the current MAC address of the device as found during ifup. For NetworkManager this is the permanent MAC address. Or in case no permanent MAC address exists, the MAC address initially configured on the device. -- -cloned-mac-address -MACADDR -- Cloned (spoofed) MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:14:5A:99). -- -generate-mac-address-mask -GENERATE_MAC_ADDRESS_MASK(+) - -- the MAC address mask for generating randomized and stable cloned-mac-address. -- -mac-address-blacklist -HWADDR_BLACKLIST(+) - -- It denies usage of the connection for any device whose address is listed. -- -seen-bssids -(none) -- This property is not handled by ifcfg-rh plugin. -- -mtu -MTU -- MTU of the wireless interface. -- -hidden -SSID_HIDDEN(+) - -- Whether the network hides the SSID. -- powersave -POWERSAVE(+) - +ingress-priority-map +VLAN_INGRESS_PRIORITY_MAP - Enables or disables Wi-Fi power saving. - -Example: POWERSAVE=enable + Ingress priority mapping. -Allowed values: default, ignore, enable, disable +Example: VLAN_INGRESS_PRIORITY_MAP=4:2,3:5- mac-address-randomization -MAC_ADDRESS_RANDOMIZATION(+) - +egress-priority-map +VLAN_EGRESS_PRIORITY_MAP - Enables or disables Wi-Fi MAC address randomization. - -Example: MAC_ADDRESS_RANDOMIZATION=always + Egress priority mapping. -Allowed values: default, never, always +Example: VLAN_EGRESS_PRIORITY_MAP=5:4,4:1,3:7- -security -(none) +interface-name +PHYSDEV and VLAN_ID, or DEVICE - This property is deprecated and not handled by ifcfg-rh-plugin. -- ap-isolation -AP_ISOLATION(+) - -missing variable means global default -Whether AP isolation is enabled + VLAN interface name. If all variables are set, parent device from PHYSDEV takes precedence over DEVICE, but VLAN id from DEVICE takes precedence over VLAN_ID. -Allowed values: "yes", "no" +Example: PHYSDEV=eth0, VLAN_ID=12; or DEVICE=eth0.12-+Table 45. wpan setting
+Table 44. vrf setting
+++
+ ++ + + + + + +Property +Ifcfg-rh Variable +Default +Description +++Table 45. wifi-p2p setting
+++
+ ++ + + + + + +Property +Ifcfg-rh Variable +Default +Description +++Table 46. wireguard setting
+++
+ ++ + + + + + +Property +Ifcfg-rh Variable +Default +Description ++Table 47. wpan setting
diff --git a/docs/api/html/nm-settings-keyfile.html b/docs/api/html/nm-settings-keyfile.html index 69bb333c..12b405b1 100644 --- a/docs/api/html/nm-settings-keyfile.html +++ b/docs/api/html/nm-settings-keyfile.html @@ -189,7 +189,93 @@ id=4 802-11-wireless-security = wifi-security -+Table 1. bridge setting (section)
+Table 1. 802-11-wireless setting (section)
+++
+ ++ + + + + + +Property +Keyfile Variable +Format +Description ++ +ssid ++ string (or decimal-byte list - obsolete) +SSID of Wi-Fi network. + +Example: ssid=Quick Net ++ +mac-address ++ usual hex-digits-and-colons notation +MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162). ++ +cloned-mac-address ++ usual hex-digits-and-colons notation +Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178). ++ + +mac-address-blacklist ++ list of MACs (separated with semicolons) +MAC address blacklist. + +Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 +++Table 2. 802-3-ethernet setting (section)
+++
+ ++ + + + + + +Property +Keyfile Variable +Format +Description ++ +mac-address ++ usual hex-digits-and-colons notation +MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162) ++ +cloned-mac-address ++ usual hex-digits-and-colons notation +Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178). ++ + +mac-address-blacklist ++ list of MACs (separated with semicolons) +MAC address blacklist. + +Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 ++Table 3. bridge setting (section)
@@ -205,7 +291,7 @@ id=4 mac-address -mac-address +usual hex-digits-and-colons notation MAC address in traditional hex-digits-and-colons notation, or semicolon separated list of 6 decimal bytes (obsolete) @@ -214,7 +300,7 @@ Example: mac-address=00:22:68:12:79:A2 mac-address=0;34;104;18;1 -Table 2. infiniband setting (section)
+Table 4. infiniband setting (section)
@@ -230,7 +316,7 @@ Example: mac-address=00:22:68:12:79:A2 mac-address=0;34;104;18;1 mac-address -mac-address +usual hex-digits-and-colons notation MAC address in traditional hex-digits-and-colons notation, or or semicolon separated list of 20 decimal bytes (obsolete) @@ -239,7 +325,7 @@ Example: mac-address= 80:00:00:6d:fe:80:00:00:00:00:00:00:00:02: -Table 3. ipv4 setting (section)
+Table 5. ipv4 setting (section)
@@ -256,7 +342,7 @@ Example: mac-address= 80:00:00:6d:fe:80:00:00:00:00:00:00:00:02: dns -dns +list of DNS IP addresses List of DNS servers. @@ -290,7 +376,7 @@ Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16 -Table 4. ipv6 setting (section)
+Table 6. ipv6 setting (section)
@@ -307,7 +393,7 @@ Example: route1=8.8.8.0/24,10.1.1.1,77 route2=7.7.0.0/16 dns -dns +list of DNS IP addresses List of DNS servers. @@ -341,7 +427,7 @@ Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11 -Table 5. serial setting (section)
+Table 7. serial setting (section)
@@ -357,7 +443,7 @@ Example: route1=2001:4860:4860::/64,2620:52:0:2219:222:68ff:fe11 parity -parity +'e', 'o', or 'n' The connection parity; even, odd, or none. Note that older versions of NetworkManager stored this as an integer: 69 ('E') for even, 111 ('o') for odd, or 110 ('n') for none. @@ -366,7 +452,7 @@ Example: parity=n -Table 6. vpn setting (section)
+Table 8. vpn setting (section)
@@ -401,7 +487,7 @@ Example: password=Popocatepetl -Table 7. wifi-p2p setting (section)
+Table 9. wifi-p2p setting (section)
@@ -417,99 +503,13 @@ Example: password=Popocatepetl peer -peer +usual hex-digits-and-colons notation MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162). --Table 8. 802-3-ethernet setting (section)
---
- -- - - - - - -Property -Keyfile Variable -Format -Description -- -mac-address -mac-address -usual hex-digits-and-colons notation -MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162) -- -cloned-mac-address -cloned-mac-address -usual hex-digits-and-colons notation -Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178). -- - -mac-address-blacklist -mac-address-blacklist -list of MACs (separated with semicolons) -MAC address blacklist. - -Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 ---Table 9. 802-11-wireless setting (section)
---
- -- - - - - - -Property -Keyfile Variable -Format -Description -- -ssid -ssid -string (or decimal-byte list - obsolete) -SSID of Wi-Fi network. - -Example: ssid=Quick Net -- -mac-address -mac-address -usual hex-digits-and-colons notation -MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:A2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;162). -- -cloned-mac-address -cloned-mac-address -usual hex-digits-and-colons notation -Cloned MAC address in traditional hex-digits-and-colons notation (e.g. 00:22:68:12:79:B2), or semicolon separated list of 6 bytes (obsolete) (e.g. 0;34;104;18;121;178). -- - -mac-address-blacklist -mac-address-blacklist -list of MACs (separated with semicolons) -MAC address blacklist. - -Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79:78 -Table 10. wpan setting (section)
@@ -526,7 +526,7 @@ Example: mac-address-blacklist= 00:22:68:12:79:A6;00:22:68:12:79 diff --git a/docs/api/html/nm-settings-nmcli.html b/docs/api/html/nm-settings-nmcli.html index e2f76d6a..2c7ef708 100644 --- a/docs/api/html/nm-settings-nmcli.html +++ b/docs/api/html/nm-settings-nmcli.html @@ -68,7 +68,7 @@ mac-address -mac-address +usual hex-digits-and-colons notation MAC address in hex-digits-and-colons notation (e.g. 76:d8:9b:87:66:60:84:ee). connection setting
-General Connection Profile Settings.
+General Connection Profile Settings.
Properties:
@@ -81,8 +81,8 @@- @@ -92,11 +92,11 @@The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.
-Currently, this only applies to 802-1x authentication.
+The number of retries for the authentication. Zero means to try indefinitely; -1 means to use a global default. If the global default is not set, the authentication retries for 3 times before failing the connection.
+Currently, this only applies to 802-1x authentication.
Format: int32
@@ -104,7 +104,7 @@ Alias: autoconnect
-Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.
-Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.
-Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.
-If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.
-Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.
+Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.
+Autoconnect happens when the circumstances are suitable. That means for example that the device is currently managed and not active. Autoconnect thus never replaces or competes with an already active profile.
+Note that autoconnect is not implemented for VPN profiles. See "secondaries" as an alternative to automatically connect VPN profiles.
+If multiple profiles are ready to autoconnect on the same device, the one with the better "connection.autoconnect-priority" is chosen. If the priorities are equal, then the most recently connected profile is activated. If the profiles were not connected earlier or their "connection.timestamp" is identical, the choice is undefined.
+Depending on "connection.multi-connect", a profile can (auto)connect only once at a time or multiple times.
Format: boolean
- @@ -112,7 +112,7 @@The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.
+The autoconnect priority in range -999 to 999. If the connection is set to autoconnect, connections with higher priority will be preferred. The higher number means higher priority. Defaults to 0. Note that this property only matters if there are more than one candidate profile to select for autoconnect. In case of equal priority, the profile used most recently is chosen.
Format: int32
- @@ -120,7 +120,7 @@The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.
+The number of times a connection should be tried when autoactivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden). Setting this to 1 means to try activation only once before blocking autoconnect. Note that after a timeout, NetworkManager will try to autoconnect again.
Format: int32
- @@ -128,9 +128,9 @@Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
+Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The properties "autoconnect", "autoconnect-priority" and "autoconnect-retries" are unrelated to this setting. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.
Format: NMSettingConnectionAutoconnectSlaves (int32)
- @@ -138,7 +138,7 @@Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
-The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.
-This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
+Whether DNSOverTls (dns-over-tls) is enabled for the connection. DNSOverTls is a technology which uses TLS to encrypt dns traffic.
+The permitted values are: "yes" (2) use DNSOverTls and disabled fallback, "opportunistic" (1) use DNSOverTls but allow fallback to unencrypted resolution, "no" (0) don't ever use DNSOverTls. If unspecified "default" depends on the plugin used. Systemd-resolved uses global setting.
+This feature requires a plugin which supports DNSOverTls. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
Format: int32
- @@ -148,7 +148,7 @@If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.
+If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.
Format: uint32
@@ -158,9 +158,9 @@ Alias: con-name
-A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".
+A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".
Format: string
@@ -168,7 +168,7 @@ Alias: ifname
-The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).
-For software devices this specifies the name of the created device.
-For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.
+The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings).
+For software devices this specifies the name of the created device.
+For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.
Format: string
- @@ -176,9 +176,9 @@Whether LLDP is enabled for the connection.
+Whether LLDP is enabled for the connection.
Format: int32
- @@ -188,7 +188,7 @@Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.
-The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").
-This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
+Whether Link-Local Multicast Name Resolution (LLMNR) is enabled for the connection. LLMNR is a protocol based on the Domain Name System (DNS) packet format that allows both IPv4 and IPv6 hosts to perform name resolution for hosts on the same local link.
+The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable LLMNR for the interface, "resolve" (1) do not register hostname but allow resolving of LLMNR host names If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "yes").
+This feature requires a plugin which supports LLMNR. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
Format: int32
@@ -196,9 +196,9 @@ Alias: master
-Interface name of the master device or UUID of the master connection.
+Interface name of the master device or UUID of the master connection.
Format: string
- @@ -206,8 +206,8 @@Whether mDNS is enabled for the connection.
-The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
-This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
+Whether mDNS is enabled for the connection.
+The permitted values are: "yes" (2) register hostname and resolving for the connection, "no" (0) disable mDNS for the interface, "resolve" (1) do not register hostname but allow resolving of mDNS host names and "default" (-1) to allow lookup of a global default in NetworkManager.conf. If unspecified, "default" ultimately depends on the DNS plugin (which for systemd-resolved currently means "no").
+This feature requires a plugin which supports mDNS. Otherwise, the setting has no effect. One such plugin is dns-systemd-resolved.
Format: int32
- @@ -215,15 +215,15 @@Whether the connection is metered.
-When updating this property on a currently activated connection, the change takes effect immediately.
+Whether the connection is metered.
+When updating this property on a currently activated connection, the change takes effect immediately.
Format: NMMetered (int32)
- @@ -231,9 +231,9 @@Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.
-If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.
-The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.
-Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.
-Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.
-When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.
-If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.
-NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.
-Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).
+Whether to configure MPTCP endpoints and the address flags. If MPTCP is enabled in NetworkManager, it will configure the addresses of the interface as MPTCP endpoints. Note that IPv4 loopback addresses (127.0.0.0/8), IPv4 link local addresses (169.254.0.0/16), the IPv6 loopback address (::1), IPv6 link local addresses (fe80::/10), IPv6 unique local addresses (ULA, fc00::/7) and IPv6 privacy extension addresses (rfc3041, ipv6.ip6-privacy) will be excluded from being configured as endpoints.
+If "disabled" (0x1), MPTCP handling for the interface is disabled and no endpoints are registered.
+The "enabled" (0x2) flag means that MPTCP handling is enabled. This flag can also be implied from the presence of other flags.
+Even when enabled, MPTCP handling will by default still be disabled unless "/proc/sys/net/mptcp/enabled" sysctl is on. NetworkManager does not change the sysctl and this is up to the administrator or distribution. To configure endpoints even if the sysctl is disabled, "also-without-sysctl" (0x4) flag can be used. In that case, NetworkManager doesn't look at the sysctl and configures endpoints regardless.
+Even when enabled, NetworkManager will only configure MPTCP endpoints for a certain address family, if there is a unicast default route (0.0.0.0/0 or ::/0) in the main routing table. The flag "also-without-default-route" (0x8) can override that.
+When MPTCP handling is enabled then endpoints are configured with the specified address flags "signal" (0x10), "subflow" (0x20), "backup" (0x40), "fullmesh" (0x80). See ip-mptcp(8) manual for additional information about the flags.
+If the flags are zero (0x0), the global connection default from NetworkManager.conf is honored. If still unspecified, the fallback is "enabled,subflow". Note that this means that MPTCP is by default done depending on the "/proc/sys/net/mptcp/enabled" sysctl.
+NetworkManager does not change the MPTCP limits nor enable MPTCP via "/proc/sys/net/mptcp/enabled". That is a host configuration which the admin can change via sysctl and ip-mptcp.
+Strict reverse path filtering (rp_filter) breaks many MPTCP use cases, so when MPTCP handling for IPv4 addresses on the interface is enabled, NetworkManager would loosen the strict reverse path filtering (1) to the loose setting (2).
Format: uint32
- @@ -241,7 +241,7 @@If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".
-The special value "none" is allowed to indicate that no MUD URL is used.
-If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".
+If configured, set to a Manufacturer Usage Description (MUD) URL that points to manufacturer-recommended network policies for IoT devices. It is transmitted as a DHCPv4 or DHCPv6 option. The value must be a valid URL starting with "https://".
+The special value "none" is allowed to indicate that no MUD URL is used.
+If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the ultimate default is "none".
Format: string
- @@ -249,8 +249,8 @@Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.
+Specifies whether the profile can be active multiple times at a particular moment. The value is of type NMConnectionMultiConnect.
Format: int32
- @@ -258,7 +258,7 @@An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".
-At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.
+An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection; otherwise users are allowed if and only if they are in this list. When this is not empty, the connection can be active only when one of the specified users is logged into an active session. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah".
+At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.
Format: array of string
- @@ -266,7 +266,7 @@FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.
+FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.
Format: boolean
- @@ -276,7 +276,7 @@List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.
+List of connection UUIDs that should be activated when the base connection itself is activated. Currently, only VPN connections are supported.
Format: array of string
@@ -284,11 +284,11 @@ Alias: slave-type
-Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
+Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.
Format: string
- @@ -296,8 +296,8 @@This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
-The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid].
-Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
-The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
-If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.
+This represents the identity of the connection used for various purposes. It allows to configure multiple profiles to share the identity. Also, the stable-id can contain placeholders that are substituted dynamically and deterministically depending on the context.
+The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. It is also used as DHCP client identifier with ipv4.dhcp-client-id=stable and to derive the DHCP DUID with ipv6.dhcp-duid=stable-[llt,ll,uuid].
+Note that depending on the context where it is used, other parameters are also seeded into the generation algorithm. For example, a per-host key is commonly also included, so that different systems end up generating different IDs. Or with ipv6.addr-gen-mode=stable-privacy, also the device's name is included, so that different interfaces yield different addresses. The per-host key is the identity of your machine and stored in /var/lib/NetworkManager/secret_key. See NetworkManager(8) manual about the secret-key and the host identity.
+The '$' character is treated special to perform dynamic substitutions at runtime. Currently, supported are "${CONNECTION}", "${DEVICE}", "${MAC}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-device, per-boot, or every time. Note that "${DEVICE}" corresponds to the interface name of the device and "${MAC}" is the permanent MAC address of the device. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}-${BOOT}-${DEVICE}" to create a unique id for this connection that changes with every reboot and differs depending on the interface where the profile activates.
+If the value is unset, a global connection default is consulted. If the value is still unset, the default is similar to "${CONNECTION}" and uses a unique, fixed ID for the connection.
Format: string
- @@ -307,7 +307,7 @@The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.
-NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).
+The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated.
+NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).
Format: uint64
@@ -315,17 +315,17 @@ Alias: type
-Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).
+Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).
Format: string
- A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.
-The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").
+A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes.
+The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").
- Format: string
+ Format: a valid RFC4122 universally unique identifier (UUID).- @@ -333,8 +333,8 @@Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.
-The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
+Time in milliseconds to wait for connection to be considered activated. The wait will start after the pre-up dispatcher event.
+The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
Format: int32
- @@ -342,8 +342,8 @@Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed.
-The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
+Timeout in milliseconds to wait for device at startup. During boot, devices may take a while to be detected by the driver. This property will cause to delay NetworkManager-wait-online.service and nm-online to give the device a chance to appear. This works by waiting for the given timeout until a compatible device for the profile is available and managed.
+The value 0 means no wait time. The default value is -1, which currently has the same meaning as no wait time.
Format: int32
- @@ -354,7 +354,7 @@The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.
-When updating this property on a currently activated connection, the change takes effect immediately.
+The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall.
+When updating this property on a currently activated connection, the change takes effect immediately.
Format: string
6lowpan setting
-6LoWPAN Settings.
+6LoWPAN Settings.
Properties:
@@ -368,7 +368,7 @@@@ -378,7 +378,7 @@ Alias: dev
-If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.
+If given, specifies the parent interface name or parent connection UUID from which this 6LowPAN interface should be created.
Format: string
802-1x setting
-IEEE 802.1x Authentication Settings.
+IEEE 802.1x Authentication Settings.
Properties:
@@ -391,7 +391,7 @@- @@ -399,7 +399,7 @@List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.
+List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.
Format: array of string
- @@ -407,7 +407,7 @@Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.
+Anonymous identity string for EAP authentication methods. Used as the unencrypted identity with EAP types that support different tunneled identity like EAP-TTLS.
Format: string
- @@ -415,9 +415,9 @@A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.
+A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.
Format: int32
- @@ -425,7 +425,7 @@Contains the CA certificate if used by the EAP method specified in the "eap" property.
-Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
-Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.
+Contains the CA certificate if used by the EAP method specified in the "eap" property.
+Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
+Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.
Format: byte array
- @@ -433,7 +433,7 @@The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
+The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
Format: string
- @@ -441,8 +441,8 @@Flags indicating how to handle the "ca-cert-password" property.
+Flags indicating how to handle the "ca-cert-password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -450,8 +450,8 @@UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.
-If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.
+UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.
+If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.
Format: string
- @@ -459,7 +459,7 @@Contains the client certificate if used by the EAP method specified in the "eap" property.
-Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.
+Contains the client certificate if used by the EAP method specified in the "eap" property.
+Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte.
Format: byte array
- @@ -467,7 +467,7 @@The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
+The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
Format: string
- @@ -475,7 +475,7 @@Flags indicating how to handle the "client-cert-password" property.
+Flags indicating how to handle the "client-cert-password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -483,7 +483,7 @@Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.
+Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.
Format: string
- @@ -491,7 +491,7 @@Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.
+Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.
Format: string
- @@ -499,7 +499,7 @@The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.
+The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: "leap", "md5", "tls", "peap", "ttls", "pwd", and "fast". Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.
Format: array of string
- @@ -507,7 +507,7 @@Identity string for EAP authentication methods. Often the user's user or login name.
+Identity string for EAP authentication methods. Often the user's user or login name.
Format: string
- @@ -515,7 +515,7 @@Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.
+Whether the 802.1X authentication is optional. If TRUE, the activation will continue even after a timeout or an authentication failure. Setting the property to TRUE is currently allowed only for Ethernet connections. If set to FALSE, the activation can continue only after a successful authentication.
Format: boolean
- @@ -523,7 +523,7 @@UTF-8 encoded file path containing PAC for EAP-FAST.
+UTF-8 encoded file path containing PAC for EAP-FAST.
Format: string
- @@ -531,7 +531,7 @@UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.
+UTF-8 encoded password used for EAP authentication methods. If both the "password" property and the "password-raw" property are specified, "password" is preferred.
Format: string
- @@ -539,7 +539,7 @@Flags indicating how to handle the "password" property.
+Flags indicating how to handle the "password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -547,7 +547,7 @@Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.
+Password used for EAP authentication methods, given as a byte array to allow passwords in other encodings than UTF-8 to be used. If both the "password" property and the "password-raw" property are specified, "password" is preferred.
Format: byte array
- @@ -555,7 +555,7 @@Flags indicating how to handle the "password-raw" property.
+Flags indicating how to handle the "password-raw" property.
Format: NMSettingSecretFlags (uint32)
- @@ -563,7 +563,7 @@Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.
+Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The individual TLS versions can be explicitly disabled. TLS time checks can be also disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x and tls_disable_time_checks settings. See the wpa_supplicant documentation for more details.
Format: uint32
- @@ -571,7 +571,7 @@Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.
+Enables or disables in-line provisioning of EAP-FAST credentials when FAST is specified as the EAP method in the "eap" property. Recognized values are "0" (disabled), "1" (allow unauthenticated provisioning), "2" (allow authenticated provisioning), and "3" (allow both authenticated and unauthenticated provisioning). See the wpa_supplicant documentation for more details.
Format: string
- @@ -579,7 +579,7 @@Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.
+Forces use of the new PEAP label during key derivation. Some RADIUS servers may require forcing the new PEAP label to interoperate with PEAPv1. Set to "1" to force use of the new PEAP label. See the wpa_supplicant documentation for more details.
Format: string
- @@ -587,7 +587,7 @@Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.
+Forces which PEAP version is used when PEAP is set as the EAP method in the "eap" property. When unset, the version reported by the server will be used. Sometimes when using older RADIUS servers, it is necessary to force the client to use a particular PEAP version. To do so, this property may be set to "0" or "1" to force that specific PEAP version.
Format: string
- @@ -595,7 +595,7 @@List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.
+List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner "phase 2" authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.
Format: array of string
- @@ -603,7 +603,7 @@Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.
+Specifies the allowed "phase 2" inner authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property. For TTLS this property selects one of the supported non-EAP inner methods: "pap", "chap", "mschap", "mschapv2" while "phase2-autheap" selects an EAP inner method. For PEAP this selects an inner EAP method, one of: "gtc", "otp", "md5" and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details. Both "phase2-auth" and "phase2-autheap" cannot be specified.
Format: string
- @@ -611,9 +611,9 @@Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.
+Specifies the allowed "phase 2" inner EAP-based authentication method when TTLS is specified in the "eap" property. Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.
Format: string
- @@ -621,7 +621,7 @@Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
-Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
-Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.
+Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
+Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
+Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.
Format: byte array
- @@ -629,7 +629,7 @@The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
+The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
Format: string
- @@ -637,8 +637,8 @@Flags indicating how to handle the "phase2-ca-cert-password" property.
+Flags indicating how to handle the "phase2-ca-cert-password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -646,8 +646,8 @@UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.
-If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.
+UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.
+If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.
Format: string
- @@ -655,7 +655,7 @@Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
-Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
+Contains the "phase 2" client certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties.
+Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.
Format: byte array
- @@ -663,7 +663,7 @@The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
+The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.
Format: string
- @@ -671,7 +671,7 @@Flags indicating how to handle the "phase2-client-cert-password" property.
+Flags indicating how to handle the "phase2-client-cert-password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -679,7 +679,7 @@Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.
+Constraint for server domain name. If set, this list of FQDNs is used as a match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using the same comparison. Multiple valid FQDNs can be passed as a ";" delimited list.
Format: string
- @@ -687,8 +687,8 @@Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.
+Constraint for server domain name. If set, this FQDN is used as a suffix match requirement for dNSName element(s) of the certificate presented by the authentication server during the inner "phase 2" authentication. If a matching dNSName is found, this constraint is met. If no dNSName values are present, this constraint is matched against SubjectName CN using same suffix match comparison. Since version 1.24, multiple valid FQDNs can be passed as a ";" delimited list.
Format: string
- @@ -696,7 +696,7 @@Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".
-Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.
+Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls".
+Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.
Format: byte array
- @@ -704,7 +704,7 @@The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.
+The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.
Format: string
- @@ -712,7 +712,10 @@Flags indicating how to handle the "phase2-private-key-password" property.
+Flags indicating how to handle the "phase2-private-key-password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -720,7 +723,7 @@Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:phase2-domain-suffix-match.
+Substring to be matched against the subject of the certificate presented by the authentication server during the inner "phase 2" authentication. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.
++ This property is deprecated since version 1.2. + Use "phase2-domain-suffix-match" instead.
Format: string
- @@ -728,7 +731,7 @@PIN used for EAP authentication methods.
+PIN used for EAP authentication methods.
Format: string
- @@ -736,9 +739,9 @@Flags indicating how to handle the "pin" property.
+Flags indicating how to handle the "pin" property.
Format: NMSettingSecretFlags (uint32)
- @@ -746,7 +749,7 @@Contains the private key when the "eap" property is set to "tls".
-Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.
-WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.
+Contains the private key when the "eap" property is set to "tls".
+Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.
+WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.
Format: byte array
- @@ -754,7 +757,7 @@The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.
+The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.
Format: string
- @@ -762,7 +765,10 @@Flags indicating how to handle the "private-key-password" property.
+Flags indicating how to handle the "private-key-password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -770,7 +776,7 @@Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and its use is deprecated in favor of NMSetting8021x:domain-suffix-match.
+Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed. This property provides little security, if any, and should not be used.
++ This property is deprecated since version 1.2. + Use "phase2-domain-suffix-match" instead.
Format: string
- @@ -781,7 +787,7 @@When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).
+When TRUE, overrides the "ca-path" and "phase2-ca-path" properties using the system CA directory specified at configure time with the --system-ca-path switch. The certificates in this directory are added to the verification chain in addition to any certificates specified by the "ca-cert" and "phase2-ca-cert" properties. If the path provided with --system-ca-path is rather a file name (bundle of trusted CA certificates), it overrides "ca-cert" and "phase2-ca-cert" properties instead (sets ca_cert/ca_cert2 options for wpa_supplicant).
Format: boolean
adsl setting
-ADSL Settings.
+ADSL Settings.
Properties:
@@ -796,7 +802,7 @@@@ -806,7 +812,7 @@ Alias: encapsulation
-Encapsulation of ADSL connection. Can be "vcmux" or "llc".
+Encapsulation of ADSL connection. Can be "vcmux" or "llc".
Format: string
@@ -814,7 +820,7 @@ Alias: password
-Password used to authenticate with the ADSL service.
+Password used to authenticate with the ADSL service.
Format: string
- @@ -824,7 +830,7 @@Flags indicating how to handle the "password" property.
+Flags indicating how to handle the "password" property.
Format: NMSettingSecretFlags (uint32)
@@ -834,7 +840,7 @@ Alias: protocol
-ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".
+ADSL connection protocol. Can be "pppoa", "pppoe" or "ipoatm".
Format: string
@@ -842,7 +848,7 @@ Alias: username
-Username used to authenticate with the ADSL service.
+Username used to authenticate with the ADSL service.
Format: string
- @@ -850,7 +856,7 @@VCI of ADSL connection
+VCI of ADSL connection
Format: uint32
- @@ -861,7 +867,7 @@VPI of ADSL connection
+VPI of ADSL connection
Format: uint32
bluetooth setting
-Bluetooth Settings.
+Bluetooth Settings.
Properties:
@@ -876,7 +882,7 @@@@ -886,7 +892,7 @@ Alias: addr
-The Bluetooth address of the device.
+The Bluetooth address of the device.
Format: byte array
@@ -897,7 +903,7 @@ Alias: bt-type
-Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.
+Either "dun" for Dial-Up Networking connections or "panu" for Personal Area Networking connections to devices supporting the NAP profile.
Format: string
bond setting
-Bonding Settings.
+Bonding Settings.
Properties:
@@ -909,7 +915,7 @@- @@ -919,7 +925,7 @@Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).
+Dictionary of key/value pairs of bonding options. Both keys and values must be strings. Option names must contain only alphanumeric characters (ie, [a-zA-Z0-9]).
Format: dict of string to string
bridge setting
-Bridging Settings.
+Bridging Settings.
Properties:
@@ -934,7 +940,7 @@@@ -944,7 +950,7 @@ Alias: ageing-time
-The Ethernet MAC address aging time, in seconds.
+The Ethernet MAC address aging time, in seconds.
Format: uint32
@@ -952,8 +958,8 @@ Alias: forward-delay
-The Spanning Tree Protocol (STP) forwarding delay, in seconds.
+The Spanning Tree Protocol (STP) forwarding delay, in seconds.
Format: uint32
- @@ -963,7 +969,7 @@If specified, The MAC address of the multicast group this bridge uses for STP.
-The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.
+If specified, The MAC address of the multicast group this bridge uses for STP.
+The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X in [0, 4..F]. If not specified the default value is 01:80:C2:00:00:00.
Format: byte array
@@ -973,7 +979,7 @@ Alias: group-forward-mask
-A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.
+A mask of group addresses to forward. Usually, group addresses in the range from 01:80:C2:00:00:00 to 01:80:C2:00:00:0F are not forwarded according to standards. This property is a mask of 16 bits, each corresponding to a group address in that range that must be forwarded. The mask can't have bits 0, 1 or 2 set because they are used for STP, MAC pause frames and LACP.
Format: uint32
@@ -983,8 +989,11 @@ Alias: hello-time
-The Spanning Tree Protocol (STP) hello time, in seconds.
+The Spanning Tree Protocol (STP) hello time, in seconds.
Format: uint32
@@ -994,7 +1003,7 @@ Alias: mac
-If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.
-If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge. Hence, this property is deprecated. Deprecated: 1
+If specified, the MAC address of bridge. When creating a new bridge, this MAC address will be set.
+If this field is left unspecified, the "ethernet.cloned-mac-address" is referred instead to generate the initial MAC address. Note that setting "ethernet.cloned-mac-address" anyway overwrites the MAC address of the bridge later while activating the bridge.
++ This property is deprecated since version 1.12. + Use the "cloned-mac-address" property instead.
Format: byte array
@@ -1002,7 +1011,7 @@ Alias: max-age
-The Spanning Tree Protocol (STP) maximum message age, in seconds.
+The Spanning Tree Protocol (STP) maximum message age, in seconds.
Format: uint32
- @@ -1010,7 +1019,7 @@Set maximum size of multicast hash table (value must be a power of 2).
+Set maximum size of multicast hash table (value must be a power of 2).
Format: uint32
- @@ -1018,7 +1027,7 @@Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.
+Set the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received.
Format: uint32
- @@ -1026,7 +1035,7 @@Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.
+Set interval (in deciseconds) between queries to find remaining members of a group, after a "leave" message is received.
Format: uint64
- @@ -1034,7 +1043,7 @@Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.
+Set delay (in deciseconds) after which the bridge will leave a group, if no membership reports for this group are received.
Format: uint64
- @@ -1042,7 +1051,7 @@Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.
+Enable or disable sending of multicast queries by the bridge. If not specified the option is disabled.
Format: boolean
- @@ -1050,7 +1059,7 @@If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.
+If no queries are seen after this delay (in deciseconds) has passed, the bridge will start to send its own queries.
Format: uint64
- @@ -1058,7 +1067,7 @@Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.
+Interval (in deciseconds) between queries sent by the bridge after the end of the startup phase.
Format: uint64
- @@ -1066,7 +1075,7 @@Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.
+Set the Max Response Time/Max Response Delay (in deciseconds) for IGMP/MLD queries sent by the bridge.
Format: uint64
- @@ -1074,8 +1083,8 @@If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.
+If enabled the bridge's own IP address is used as the source address for IGMP queries otherwise the default of 0.0.0.0 is used.
Format: boolean
- @@ -1085,7 +1094,7 @@Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.
-Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).
+Sets bridge's multicast router. Multicast-snooping must be enabled for this option to work.
+Supported values are: 'auto', 'disabled', 'enabled' to which kernel assigns the numbers 1, 0, and 2, respectively. If not specified the default value is 'auto' (1).
Format: string
@@ -1093,7 +1102,7 @@ Alias: multicast-snooping
-Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.
+Controls whether IGMP snooping is enabled for this bridge. Note that if snooping was automatically disabled due to hash collisions, the system may refuse to enable the feature until the collisions are resolved.
Format: boolean
- @@ -1101,7 +1110,7 @@Set the number of IGMP queries to send during startup phase.
+Set the number of IGMP queries to send during startup phase.
Format: uint32
- @@ -1111,7 +1120,7 @@Sets the time (in deciseconds) between queries sent out at startup to determine membership information.
+Sets the time (in deciseconds) between queries sent out at startup to determine membership information.
Format: uint64
@@ -1121,7 +1130,7 @@ Alias: priority
-Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.
+Sets the Spanning Tree Protocol (STP) priority for this bridge. Lower values are "better"; the lowest priority bridge will be elected the root bridge.
Format: uint32
@@ -1129,7 +1138,7 @@ Alias: stp
-Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.
+Controls whether Spanning Tree Protocol (STP) is enabled for this bridge.
Format: boolean
- @@ -1137,7 +1146,7 @@The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.
+The default PVID for the ports of the bridge, that is the VLAN id assigned to incoming untagged frames.
Format: uint32
- @@ -1145,8 +1154,8 @@Control whether VLAN filtering is enabled on the bridge.
+Control whether VLAN filtering is enabled on the bridge.
Format: boolean
- @@ -1154,7 +1163,7 @@If specified, the protocol used for VLAN filtering.
-Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
+If specified, the protocol used for VLAN filtering.
+Supported values are: '802.1Q', '802.1ad'. If not specified the default value is '802.1Q'.
Format: string
- @@ -1162,10 +1171,10 @@Controls whether per-VLAN stats accounting is enabled.
+Controls whether per-VLAN stats accounting is enabled.
Format: boolean
- @@ -1176,7 +1185,7 @@Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property.
-In nmcli the VLAN list can be specified with the following syntax:
-$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
-where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.
+Array of bridge VLAN objects. In addition to the VLANs specified here, the bridge will also have the default-pvid VLAN configured by the bridge.vlan-default-pvid property.
+In nmcli the VLAN list can be specified with the following syntax:
+$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
+where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.
Format: array of vardict
bridge-port setting
-Bridge Port Settings.
+Bridge Port Settings.
Properties:
@@ -1191,7 +1200,7 @@@@ -1201,7 +1210,7 @@ Alias: hairpin
-Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.
+Enables or disables "hairpin mode" for the port, which allows frames to be sent back out through the port the frame was received on.
Format: boolean
@@ -1211,7 +1220,7 @@ Alias: path-cost
-The Spanning Tree Protocol (STP) port cost for destinations via this port.
+The Spanning Tree Protocol (STP) port cost for destinations via this port.
Format: uint32
@@ -1219,10 +1228,10 @@ Alias: priority
-The Spanning Tree Protocol (STP) priority of this bridge port.
+The Spanning Tree Protocol (STP) priority of this bridge port.
Format: uint32
- @@ -1233,7 +1242,7 @@Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.
-In nmcli the VLAN list can be specified with the following syntax:
-$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
-where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.
+Array of bridge VLAN objects. In addition to the VLANs specified here, the port will also have the default-pvid VLAN configured on the bridge by the bridge.vlan-default-pvid property.
+In nmcli the VLAN list can be specified with the following syntax:
+$vid [pvid] [untagged] [, $vid [pvid] [untagged]]...
+where $vid is either a single id between 1 and 4094 or a range, represented as a couple of ids separated by a dash.
Format: array of vardict
cdma setting
-CDMA-based Mobile Broadband Settings.
+CDMA-based Mobile Broadband Settings.
Properties:
@@ -1246,7 +1255,7 @@- @@ -1254,7 +1263,7 @@If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
+If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
Format: uint32
- @@ -1264,7 +1273,7 @@The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.
+The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.
Format: string
@@ -1272,7 +1281,7 @@ Alias: password
-The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.
+The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.
Format: string
- @@ -1282,7 +1291,7 @@Flags indicating how to handle the "password" property.
+Flags indicating how to handle the "password" property.
Format: NMSettingSecretFlags (uint32)
@@ -1293,7 +1302,7 @@ Alias: user
-The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.
+The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.
Format: string
dcb setting
-Data Center Bridging Settings.
+Data Center Bridging Settings.
Properties:
@@ -1306,7 +1315,7 @@- @@ -1314,8 +1323,8 @@Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
+Specifies the NMSettingDcbFlags for the DCB FCoE application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
Format: NMSettingDcbFlags (uint32)
- @@ -1323,7 +1332,7 @@The FCoE controller mode; either "fabric" or "vn2vn".
-Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".
+The FCoE controller mode; either "fabric" or "vn2vn".
+Since 1.34, NULL is the default and means "fabric". Before 1.34, NULL was rejected as invalid and the default was "fabric".
Format: string
- @@ -1331,7 +1340,7 @@The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
+The highest User Priority (0 - 7) which FCoE frames should use, or -1 for default priority. Only used when the "app-fcoe-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
Format: int32
- @@ -1339,7 +1348,7 @@Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
+Specifies the NMSettingDcbFlags for the DCB FIP application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
Format: NMSettingDcbFlags (uint32)
- @@ -1347,7 +1356,7 @@The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
+The highest User Priority (0 - 7) which FIP frames should use, or -1 for default priority. Only used when the "app-fip-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
Format: int32
- @@ -1355,7 +1364,7 @@Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
+Specifies the NMSettingDcbFlags for the DCB iSCSI application. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
Format: NMSettingDcbFlags (uint32)
- @@ -1363,7 +1372,7 @@The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
+The highest User Priority (0 - 7) which iSCSI frames should use, or -1 for default priority. Only used when the "app-iscsi-flags" property includes the NM_SETTING_DCB_FLAG_ENABLE (0x1) flag.
Format: int32
- @@ -1371,7 +1380,7 @@An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.
+An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the percentage of bandwidth of the priority's assigned group that the priority may use. The sum of all percentages for priorities which belong to the same group must total 100 percents.
Format: array of uint32
- @@ -1379,7 +1388,7 @@An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.
+An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the corresponding priority should transmit priority pause.
Format: array of uint32
- @@ -1387,7 +1396,7 @@Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
+Specifies the NMSettingDcbFlags for DCB Priority Flow Control (PFC). Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
Format: NMSettingDcbFlags (uint32)
- @@ -1395,7 +1404,7 @@An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.
+An array of 8 uint values, where the array index corresponds to the Priority Group ID (0 - 7) and the value indicates the percentage of link bandwidth allocated to that group. Allowed values are 0 - 100, and the sum of all values must total 100 percents.
Format: array of uint32
- @@ -1403,7 +1412,7 @@Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
+Specifies the NMSettingDcbFlags for DCB Priority Groups. Flags may be any combination of NM_SETTING_DCB_FLAG_ENABLE (0x1), NM_SETTING_DCB_FLAG_ADVERTISE (0x2), and NM_SETTING_DCB_FLAG_WILLING (0x4).
Format: NMSettingDcbFlags (uint32)
- @@ -1411,7 +1420,7 @@An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.
+An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the Priority Group ID. Allowed Priority Group ID values are 0 - 7 or 15 for the unrestricted group.
Format: array of uint32
- @@ -1419,7 +1428,7 @@An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.
+An array of 8 boolean values, where the array index corresponds to the User Priority (0 - 7) and the value indicates whether or not the priority may use all of the bandwidth allocated to its assigned group.
Format: array of uint32
- @@ -1430,7 +1439,7 @@An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
+An array of 8 uint values, where the array index corresponds to the User Priority (0 - 7) and the value indicates the traffic class (0 - 7) to which the priority is mapped.
Format: array of uint32
ethtool setting
-Ethtool Ethernet Settings.
+Ethtool Ethernet Settings.
Properties:
@@ -1794,7 +1803,7 @@
gsm setting
-GSM-based Mobile Broadband Settings.
+GSM-based Mobile Broadband Settings.
Properties:
@@ -1809,7 +1818,7 @@@@ -1817,7 +1826,7 @@ Alias: apn
-The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.
+The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.
Format: string
- @@ -1825,7 +1834,7 @@When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.
+When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.
Format: boolean
- @@ -1833,7 +1842,7 @@The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.
+The device unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will only apply to the specified device.
Format: string
- @@ -1841,7 +1850,7 @@When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.
+When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.
Format: boolean
- @@ -1849,7 +1858,7 @@If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
+If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
Format: uint32
- @@ -1857,7 +1866,10 @@The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.
+The Network ID (GSM LAI format, ie MCC-MNC) to force specific network registration. If the Network ID is specified, NetworkManager will attempt to force the device to register only on the specified network. This can be used to ensure that the device does not roam when direct roaming control of the device is not otherwise possible.
Format: string
- @@ -1867,7 +1879,7 @@Legacy setting that used to help establishing PPP data sessions for GSM-based modems. Deprecated: 1
+Legacy setting that used to help establishing PPP data sessions for GSM-based modems.
++ This property is deprecated since version 1.16. + User-provided values for this setting are no longer used.
Format: string
@@ -1875,7 +1887,7 @@ Alias: password
-The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.
+The password used to authenticate with the network, if required. Many providers do not require a password, or accept any password. But if a password is required, it is specified here.
Format: string
- @@ -1883,7 +1895,7 @@Flags indicating how to handle the "password" property.
+Flags indicating how to handle the "password" property.
Format: NMSettingSecretFlags (uint32)
- @@ -1891,7 +1903,7 @@If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.
+If the SIM is locked with a PIN it must be unlocked before any other operations are requested. Specify the PIN here to allow operation of the device.
Format: string
- @@ -1899,7 +1911,7 @@Flags indicating how to handle the "pin" property.
+Flags indicating how to handle the "pin" property.
Format: NMSettingSecretFlags (uint32)
- @@ -1907,7 +1919,7 @@The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.
+The SIM card unique identifier (as given by the WWAN management service) which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" which contains a SIM card matching the given identifier.
Format: string
- @@ -1917,7 +1929,7 @@A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.
+A MCC/MNC string like "310260" or "21601" identifying the specific mobile network operator which this connection applies to. If given, the connection will apply to any device also allowed by "device-id" and "sim-id" which contains a SIM card provisioned by the given operator.
Format: string
@@ -1928,7 +1940,7 @@ Alias: user
-The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.
+The username used to authenticate with the network, if required. Many providers do not require a username, or accept any username. But if a username is required, it is specified here.
Format: string
infiniband setting
-Infiniband Settings.
+Infiniband Settings.
Properties:
@@ -1943,7 +1955,7 @@@@ -1953,7 +1965,7 @@ Alias: mac
-If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).
+If specified, this connection will only apply to the IPoIB device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).
Format: byte array
@@ -1963,7 +1975,7 @@ Alias: mtu
-If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
+If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.
Format: uint32
@@ -1973,7 +1985,7 @@ Alias: p-key
-The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.
+The InfiniBand P_Key to use for this device. A value of -1 means to use the default P_Key (aka "the P_Key at index 0"). Otherwise, it is a 16-bit unsigned integer, whose high bit is set if it is a "full membership" P_Key.
Format: int32
@@ -1983,7 +1995,7 @@ Alias: parent
-The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".
+The interface name of the parent device of this device. Normally NULL, but if the "p_key" property is set, then you must specify the base device by setting either this property or "mac-address".
Format: string
@@ -1994,7 +2006,7 @@ Alias: transport-mode
-The IP-over-InfiniBand transport mode. Either "datagram" or "connected".
+The IP-over-InfiniBand transport mode. Either "datagram" or "connected".
Format: string
+ ++ + +VPN connections will default to add the route automatically unless this setting is set to FALSE.
+For other connection types, adding such an automatic route is currently not supported and setting this to TRUE has no effect.
++ Format: NMTernary (int32)
+- @@ -2026,12 +2047,12 @@Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds.
-The property is currently implemented only for IPv4.
+Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds.
+The property is currently implemented only for IPv4.
Format: int32
- @@ -2039,7 +2060,7 @@A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.
-The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.
-The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset.
-The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id.
-The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
-If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.
+A string sent to the DHCP server to identify the local machine which the DHCP server may use to customize the DHCP lease and options. When the property is a hex string ('aa:bb:cc') it is interpreted as a binary client ID, in which case the first byte is assumed to be the 'type' field as per RFC 2132 section 9.14 and the remaining bytes may be an hardware address (e.g. '01:xx:xx:xx:xx:xx:xx' where 1 is the Ethernet ARP type and the rest is a MAC address). If the property is not a hex string it is considered as a non-hardware-address client ID and the 'type' field is set to 0.
+The special values "mac" and "perm-mac" are supported, which use the current or permanent MAC address of the device to generate a client identifier with type ethernet (01). Currently, these options only work for ethernet type of links.
+The special value "ipv6-duid" uses the DUID from "ipv6.dhcp-duid" property as an RFC4361-compliant client identifier. As IAID it uses "ipv4.dhcp-iaid" and falls back to "ipv6.dhcp-iaid" if unset.
+The special value "duid" generates a RFC4361-compliant client identifier based on "ipv4.dhcp-iaid" and uses a DUID generated by hashing /etc/machine-id.
+The special value "stable" is supported to generate a type 0 client identifier based on the stable-id (see connection.stable-id) and a per-host key. If you set the stable-id, you may want to include the "${DEVICE}" or "${MAC}" specifier to get a per-device key.
+If unset, a globally configured default is used. If still unset, the default depends on the DHCP plugin.
Format: string
- @@ -2047,7 +2068,7 @@If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.
+If the "dhcp-send-hostname" property is TRUE, then the specified FQDN will be sent to the DHCP server when acquiring a lease. This property and "dhcp-hostname" are mutually exclusive and cannot be set at the same time.
Format: string
- @@ -2055,9 +2076,9 @@If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.
+If the "dhcp-send-hostname" property is TRUE, then the specified name will be sent to the DHCP server when acquiring a lease. This property and "dhcp-fqdn" are mutually exclusive and cannot be set at the same time.
Format: string
- @@ -2065,7 +2086,7 @@Flags for the DHCP hostname and FQDN.
-Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
-When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
+Flags for the DHCP hostname and FQDN.
+Currently, this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4). When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6.
+When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.
Format: uint32
- @@ -2073,9 +2094,9 @@A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.
+A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.
Format: string
- @@ -2083,7 +2104,7 @@Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
-For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").
-This property is currently not implemented for DHCPv6.
+Array of servers from which DHCP offers must be rejected. This property is useful to avoid getting a lease from misconfigured or rogue servers.
+For DHCPv4, each element must be an IPv4 address, optionally followed by a slash and a prefix length (e.g. "192.168.122.0/24").
+This property is currently not implemented for DHCPv6.
Format: array of string
- @@ -2091,8 +2112,8 @@If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
+If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the "dhcp-hostname" property is NULL and this property is TRUE, the current persistent hostname of the computer is sent.
Format: boolean
- @@ -2100,7 +2121,7 @@A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).
-Set to 2147483647 (MAXINT32) for infinity.
+A timeout for a DHCP transaction in seconds. If zero (the default), a globally configured default is used. If still unspecified, a device specific timeout is used (usually 45 seconds).
+Set to 2147483647 (MAXINT32) for infinity.
Format: int32
- @@ -2108,7 +2129,8 @@The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.
+The Vendor Class Identifier DHCP option (60). Special characters in the data string may be escaped using C-style escapes, nevertheless this property cannot contain nul bytes. If the per-profile value is unspecified (the default), a global connection default gets consulted. If still unspecified, the DHCP option is not sent to the server.
Format: string
- @@ -2116,11 +2138,11 @@Array of IP addresses of DNS servers.
+Array of IP addresses of DNS servers.
+For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved.
Format: array of uint32
- @@ -2128,14 +2150,14 @@Array of DNS options as described in man 5 resolv.conf.
-NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
-The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
-The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
-When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.
+Array of DNS options as described in man 5 resolv.conf.
+NULL means that the options are unset and left at the default. In this case NetworkManager will use default options. This is distinct from an empty list of properties.
+The currently supported options are "attempts", "debug", "edns0", "inet6", "ip6-bytestring", "ip6-dotint", "ndots", "no-check-names", "no-ip6-dotint", "no-reload", "no-tld-query", "rotate", "single-request", "single-request-reopen", "timeout", "trust-ad", "use-vc".
+The "trust-ad" setting is only honored if the profile contributes name servers to resolv.conf, and if all contributing profiles have "trust-ad" enabled.
+When using a caching DNS plugin (dnsmasq or systemd-resolved in NetworkManager.conf) then "edns0" and "trust-ad" are automatically added.
Format: array of string
- @@ -2143,9 +2165,9 @@DNS servers priority.
-The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority).
-Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
-Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
-Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile.
-When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
-When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.
-When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.
+DNS servers priority.
+The relative priority for DNS servers specified by this setting. A lower numerical value is better (higher priority).
+Negative values have the special effect of excluding other configurations with a greater numerical priority value; so in presence of at least one negative priority, only DNS servers from connections with the lowest priority value will be used. To avoid all DNS leaks, set the priority of the profile that should be used to the most negative value of all active connections profiles.
+Zero selects a globally configured default value. If the latter is missing or zero too, it defaults to 50 for VPNs (including WireGuard) and 100 for other connections.
+Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile.
+When multiple devices have configurations with the same priority, VPNs will be considered first, then devices with the best (lowest metric) default route and then all other devices.
+When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. Note that commonly the resolver tries name servers in /etc/resolv.conf in the order listed, proceeding with the next server in the list on failure. See for example the "rotate" option of the dns-options setting. If there are any negative DNS priorities, then only name servers from the devices with that lowest priority will be considered.
+When using a DNS resolver that supports Conditional Forwarding or Split DNS (with dns=dnsmasq or dns=systemd-resolved settings), each connection is used to query domains in its search list. The search domains determine which name servers to ask, and the DNS priority is used to prioritize name servers based on the domain. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the best priority (lowest numerical value) wins. If a sub domain is configured on another interface it will be accepted regardless the priority, unless parent domain on the other interface has a negative priority, which causes the sub domain to be shadowed. With Split DNS one can avoid undesired DNS leaks by properly configuring DNS priorities and the search domains, so that only name servers of the desired interface are configured.
Format: int32
- @@ -2155,9 +2177,9 @@List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
-When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.
-When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).
+List of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.
+When using a DNS plugin that supports Conditional Forwarding or Split DNS, then the search domains specify which name servers to query. This makes the behavior different from running with plain /etc/resolv.conf. For more information see also the dns-priority setting.
+When set on a profile that also enabled DHCP, the DNS search list received automatically (option 119 for DHCPv4 and option 24 for DHCPv6) gets merged with the manual list. This can be prevented by setting "ignore-auto-dns". Note that if no DNS searches are configured, the fallback will be derived from the domain from DHCP (option 15).
Format: array of string
@@ -2165,7 +2187,7 @@ Alias: gw4
-The gateway associated with this configuration. This is only meaningful if "addresses" is also set.
-Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.
-Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".
+The gateway associated with this configuration. This is only meaningful if "addresses" is also set.
+Setting the gateway causes NetworkManager to configure a standard default route with the gateway as next hop. This is ignored if "never-default" is set. An alternative is to configure the default route explicitly with a manual route and /0 as prefix length.
+Note that the gateway usually conflicts with routing that NetworkManager configures for WireGuard interfaces, so usually it should not be set in that case. See "ip4-auto-default-route".
Format: string
- @@ -2173,7 +2195,7 @@When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.
+When "method" is set to "auto" and this property to TRUE, automatically configured name servers and search domains are ignored and only name servers and search domains specified in the "dns" and "dns-search" properties, if any, are used.
Format: boolean
- @@ -2181,8 +2203,8 @@When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.
+When "method" is set to "auto" and this property to TRUE, automatically configured routes are ignored and only routes specified in the "routes" property, if any, are used.
Format: boolean
- @@ -2190,7 +2212,7 @@Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server.
-When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".
+Enable and disable the IPv4 link-local configuration independently of the ipv4.method configuration. This allows a link-local address (169.254.x.y/16) to be obtained in addition to other addresses, such as those manually configured or obtained from a DHCP server.
+When set to "auto", the value is dependent on "ipv4.method". When set to "default", it honors the global connection default, before falling back to "auto". Note that if "ipv4.method" is "disabled", then link local addressing is always disabled too. The default is "default".
Format: int32
- @@ -2198,11 +2220,11 @@If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.
+If TRUE, allow overall network configuration to proceed even if the configuration specified by this property times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE on the NMSettingIP4Config allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.
Format: boolean
- @@ -2210,7 +2232,7 @@IP configuration method.
-NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
-In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
-For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
-For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.
+IP configuration method.
+NMSettingIP4Config and NMSettingIP6Config both support "disabled", "auto", "manual", and "link-local". See the subclass-specific documentation for other values.
+In general, for the "auto" method, properties such as "dns" and "routes" specify information that is added on to the information returned from automatic configuration. The "ignore-auto-routes" and "ignore-auto-dns" properties modify this behavior.
+For methods that imply no upstream network, such as "shared" or "link-local", these properties must be empty.
+For IPv4 method "shared", the IP subnet can be configured by adding one manual IPv4 address or otherwise 10.42.x.0/24 is chosen. Note that the shared method must be configured on the interface which shares the internet to a subnet, not on the uplink which is shared.
Format: string
- @@ -2218,10 +2240,10 @@If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.
+If TRUE, this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager.
Format: boolean
- @@ -2229,7 +2251,7 @@The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
-This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
-Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout.
-A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).
+The minimum time interval in milliseconds for which dynamic IP configuration should be tried before the connection succeeds.
+This property is useful for example if both IPv4 and IPv6 are enabled and are allowed to fail. Normally the connection succeeds as soon as one of the two address families completes; by setting a required timeout for e.g. IPv4, one can ensure that even if IP6 succeeds earlier than IPv4, NetworkManager waits some time for IPv4 before the connection becomes active.
+Note that if "may-fail" is FALSE for the same address family, this property has no effect as NetworkManager needs to wait for the full DHCP timeout.
+A zero value means that no required timeout is present, -1 means the default value (either configuration ipvx.required-timeout override or zero).
Format: int32
- @@ -2237,10 +2259,10 @@The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.
+The default metric for routes that don't explicitly specify a metric. The default value -1 means that the metric is chosen automatically based on the device type. The metric applies to dynamic routes, manual (static) routes that don't have an explicit metric setting, address prefix routes, and the default route. Note that for IPv6, the kernel accepts zero (0) but coerces it to 1024 (user default). Hence, setting this property to zero effectively mean setting it to 1024. For IPv4, zero is a regular value for the metric.
Format: int64
- @@ -2249,14 +2271,14 @@Enable policy routing (source routing) and set the routing table used when adding routes.
-This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
-If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.
-Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.
+Enable policy routing (source routing) and set the routing table used when adding routes.
+This affects all routes, including device-routes, IPv4LL, DHCP, SLAAC, default-routes and static routes. But note that static routes can individually overwrite the setting by explicitly specifying a non-zero routing table.
+If the table setting is left at zero, it is eligible to be overwritten via global configuration. If the property is zero even after applying the global configuration value, policy routing is disabled for the address family of this connection.
+Policy routing disabled means that NetworkManager will add all routes to the main table (except static routes that explicitly configure a different table). Additionally, NetworkManager will not delete any extraneous routes from tables except the main table. This is to preserve backward compatibility for users who manage routing tables outside of NetworkManager.
Format: uint32
-A list of IPv4 destination addresses, prefix length, optional IPv4 -next hop addresses, optional route metric, optional attribute. The valid syntax is: -"ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]". -For example "192.0.2.0/24 10.1.1.1 77, 198.51.100.0/24". + A list of IPv4 destination addresses, prefix length, optional IPv4 + next hop addresses, optional route metric, optional attribute. The valid syntax is: + "ip[/prefix] [next-hop] [metric] [attribute=val]...[,ip[/prefix]...]". + For example "192.0.2.0/24 10.1.1.1 77, 198.51.100.0/24".
-Various attributes are supported: -
+ Various attributes are supported: +
"advmss"- an unsigned 32 bit integer.- @@ -2269,17 +2291,33 @@ Various attributes are supported:
"cwnd"- an unsigned 32 bit integer.
"lock-mtu"- a boolean value.
"lock-window"- a boolean value.- -
"mtu"- an unsigned 32 bit integer.- +
"onlink"- a boolean value.
"onlink"- a boolean value. The onlink flag + is ignored for IPv4 routes without a gateway. That also means, + with a positive "weight" the route cannot merge with ECMP routes + which are onlink and have a gateway. +
"quickack"- a boolean value.- + The value is in milliseconds.
"rto_min"- an unsigned 32 bit integer. -The value is in milliseconds.
"scope"- an unsigned 8 bit integer. IPv4 only.
"src"- an IPv4 address.
"table"- an unsigned 32 bit integer. The default depends on ipv4.route-table.
"tos"- an unsigned 8 bit integer. IPv4 only.- +
"type"- one ofunicast,local,blackhole, -unavailable,prohibit,throw. -The default isunicast.unavailable,prohibit,throw. + The default isunicast. +- +
+
"weight"- an unsigned 32 bit integer + ranging from 0 to 256. A non-zero weight indicates that the IPv4 + route is an ECMP IPv4 route. NetworkManager will automatically + merge compatible ECMP routes into multi-hop routes. Setting to + zero or omitting the attribute configures single hop routes that + won't get merged. If the route finds no merge partner, it is + configured as single hop route.Note that in + NetworkManager, currently all nexthops of a ECMP route must share + the same "onlink" flag in order to be mergable.
+
"window"- an unsigned 32 bit integer.@@ -2313,7 +2351,7 @@ Example:
priority 5 from 192.167.4.0/24 table 45