summary refs log tree commit diff
path: root/introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml
diff options
context:
space:
mode:
Diffstat (limited to 'introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml')
-rw-r--r--introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml181
1 files changed, 143 insertions, 38 deletions
diff --git a/introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml b/introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml
index a5a0697b..883c5d75 100644
--- a/introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml
+++ b/introspection/nmdbus-device-org.freedesktop.NetworkManager.Device.xml
@@ -71,19 +71,39 @@ Reapply (IN  a{sa{sv}} connection,
          IN  t         version_id,
          IN  u         flags);
 </programlisting>
-<para>Attempts to update the configuration of a device without deactivating it. NetworkManager         has the concept of connections, which are profiles that contain the configuration for         a networking device. Those connections are exposed via D-Bus as individual objects         that can be created, modified and deleted. When activating such a settings-connection         on a device, the settings-connection is cloned to become an applied-connection and used to         configure the device (see GetAppliedConnection). Subsequent modification of the         settings-connection don't propagate automatically to the device's applied-connection         (with exception of the firewall-zone and the metered property). For the changes to take         effect, you can either re-activate the settings-connection, or call Reapply.         The Reapply call allows you to directly update the applied-connection and reconfigure         the device.         Reapply can also be useful if the currently applied-connection is equal to the connection         that is about to be reapplied. This allows to reconfigure the device and revert external         changes like removing or adding an IP address (which NetworkManager doesn't revert         automatically because it is assumed that the user made these changes intentionally outside         of NetworkManager).         Reapply can make the applied-connection different from the settings-connection,         just like updating the settings-connection can make them different.</para>
+<para>        Attempts to update the configuration of a device without deactivating it.
+        NetworkManager has the concept of connections, which are profiles that
+        contain the configuration for a networking device. Those connections are
+        exposed via D-Bus as individual objects that can be created, modified and
+        deleted. When activating such a settings-connection on a device, the
+        settings-connection is cloned to become an applied-connection and used to
+        configure the device (see GetAppliedConnection). Subsequent modification
+        of the settings-connection don't propagate automatically to the device's
+        applied-connection (with exception of the firewall-zone and the metered
+        property). For the changes to take effect, you can either re-activate the
+        settings-connection, or call Reapply. The Reapply call allows you to
+        directly update the applied-connection and reconfigure the device. Reapply
+        can also be useful if the currently applied-connection is equal to the
+        connection that is about to be reapplied. This allows to reconfigure the
+        device and revert external changes like removing or adding an IP address
+        (which NetworkManager doesn't revert automatically because it is assumed
+        that the user made these changes intentionally outside of NetworkManager).
+        Reapply can make the applied-connection different from the
+        settings-connection, just like updating the settings-connection can make
+        them different.
+</para>
 <variablelist role="params">
 <varlistentry>
   <term><literal>IN a{sa{sv}} <parameter>connection</parameter></literal>:</term>
-  <listitem><para>The optional connection settings that will be reapplied on the device. If empty, the           currently active settings-connection will be used. The connection cannot arbitrarly           differ from the current applied-connection otherwise the call will fail.           Only certain changes are supported, like adding or removing IP addresses.</para></listitem>
+  <listitem><para>The optional connection settings that will be reapplied on the device. If empty, the currently active settings-connection will be used. The connection cannot arbitrarly differ from the current applied-connection otherwise the call will fail. Only certain changes are supported, like adding or removing IP addresses.</para></listitem>
 </varlistentry>
 <varlistentry>
   <term><literal>IN t <parameter>version_id</parameter></literal>:</term>
-  <listitem><para>If non-zero, the current version id of the applied-connection must match.           The current version id can be retrieved via GetAppliedConnection.           This optional argument allows to catch concurrent modifications between           the GetAppliedConnection call and Reapply.</para></listitem>
+  <listitem><para>If non-zero, the current version id of the applied-connection must match. The current version id can be retrieved via GetAppliedConnection. This optional argument allows to catch concurrent modifications between the GetAppliedConnection call and Reapply.</para></listitem>
 </varlistentry>
 <varlistentry>
   <term><literal>IN u <parameter>flags</parameter></literal>:</term>
-  <listitem><para>Flags which would modify the behavior of the Reapply call.           There are no flags defined currently and the users should use the value of 0.</para></listitem>
+  <listitem><para>Flags which would modify the behavior of the Reapply call. There are no flags defined currently and the users should use the value of 0.</para></listitem>
 </varlistentry>
 </variablelist>
 </refsect2>
@@ -95,11 +115,18 @@ GetAppliedConnection (IN  u         flags,
                       OUT a{sa{sv}} connection,
                       OUT t         version_id);
 </programlisting>
-<para>Get the currently applied connection on the device. This is a snapshot of the last activated         connection on the device, that is the configuration that is currently applied on the device.         Usually this is the same as GetSettings of the referenced settings connection. However, it         can differ if the settings connection was subsequently modified or the applied connection was         modified by Reapply. The applied connection is set when activating a device or when calling         Reapply.</para>
+<para>        Get the currently applied connection on the device. This is a snapshot of
+        the last activated connection on the device, that is the configuration
+        that is currently applied on the device. Usually this is the same as
+        GetSettings of the referenced settings connection. However, it can differ
+        if the settings connection was subsequently modified or the applied
+        connection was modified by Reapply. The applied connection is set when
+        activating a device or when calling Reapply.
+</para>
 <variablelist role="params">
 <varlistentry>
   <term><literal>IN u <parameter>flags</parameter></literal>:</term>
-  <listitem><para>Flags which would modify the behavior of the GetAppliedConnection call.           There are no flags defined currently and the users should use the value of 0.</para></listitem>
+  <listitem><para>Flags which would modify the behavior of the GetAppliedConnection call. There are no flags defined currently and the users should use the value of 0.</para></listitem>
 </varlistentry>
 <varlistentry>
   <term><literal>OUT a{sa{sv}} <parameter>connection</parameter></literal>:</term>
@@ -107,7 +134,7 @@ GetAppliedConnection (IN  u         flags,
 </varlistentry>
 <varlistentry>
   <term><literal>OUT t <parameter>version_id</parameter></literal>:</term>
-  <listitem><para>The version-id of the currently applied connection. This can be specified during             Reapply to avoid races where you first fetch the applied connection, modify it             and try to reapply it. If the applied connection is modified in the meantime, the             version_id gets incremented and Reapply will fail.</para></listitem>
+  <listitem><para>The version-id of the currently applied connection. This can be specified during Reapply to avoid races where you first fetch the applied connection, modify it and try to reapply it. If the applied connection is modified in the meantime, the version_id gets incremented and Reapply will fail.</para></listitem>
 </varlistentry>
 </variablelist>
 </refsect2>
@@ -117,7 +144,9 @@ GetAppliedConnection (IN  u         flags,
 <programlisting>
 Disconnect ();
 </programlisting>
-<para>Disconnects a device and prevents the device from automatically activating further connections without user intervention.</para>
+<para>        Disconnects a device and prevents the device from automatically activating
+        further connections without user intervention.
+</para>
 </refsect2>
 <refsect2 role="method" id="gdbus-method-org-freedesktop-NetworkManager-Device.Delete">
   <title>The Delete() method</title>
@@ -125,7 +154,10 @@ Disconnect ();
 <programlisting>
 Delete ();
 </programlisting>
-<para>Deletes a software device from NetworkManager and removes the interface from the system.         The method returns an error when called for a hardware device.</para>
+<para>        Deletes a software device from NetworkManager and removes the interface
+        from the system. The method returns an error when called for a hardware
+        device.
+</para>
 </refsect2>
 </refsect1>
 <refsect1 role="details" id="gdbus-signals-org.freedesktop.NetworkManager.Device">
@@ -142,15 +174,15 @@ StateChanged (u new_state,
 <variablelist role="params">
 <varlistentry>
   <term><literal>u <parameter>new_state</parameter></literal>:</term>
-  <listitem><para>The new state of the device.</para></listitem>
+  <listitem><para>(<link linkend="NMDeviceState">NMDeviceState</link>) The new state of the device.</para></listitem>
 </varlistentry>
 <varlistentry>
   <term><literal>u <parameter>old_state</parameter></literal>:</term>
-  <listitem><para>The previous state of the device.</para></listitem>
+  <listitem><para>(<link linkend="NMDeviceState">NMDeviceState</link>) The previous state of the device.</para></listitem>
 </varlistentry>
 <varlistentry>
   <term><literal>u <parameter>reason</parameter></literal>:</term>
-  <listitem><para>A reason for the state transition.</para></listitem>
+  <listitem><para>(<link linkend="NMDeviceStateReason">NMDeviceStateReason</link>) A reason for the state transition.</para></listitem>
 </varlistentry>
 </variablelist>
 </refsect2>
@@ -163,7 +195,18 @@ StateChanged (u new_state,
 <programlisting>
 Udi  readable   s
 </programlisting>
-<para>Operating-system specific transient device hardware identifier.  This         is an opaque string representing the underlying hardware for the device,         and shouldn't be used to keep track of individual devices.  For some         device types (Bluetooth, Modems) it is an identifier used by the         hardware service (ie bluez or ModemManager) to refer to that device,         and client programs use it get additional information from those         services which NM does not provide.  The Udi is not guaranteed to be         consistent across reboots or hotplugs of the hardware. If you're looking         for a way to uniquely track each device in your application, use the         object path.  If you're looking for a way to track a specific piece of         hardware across reboot or hotplug, use a MAC address or USB serial         number.</para>
+<para>        Operating-system specific transient device hardware identifier. This is an
+        opaque string representing the underlying hardware for the device, and
+        shouldn't be used to keep track of individual devices. For some device
+        types (Bluetooth, Modems) it is an identifier used by the hardware service
+        (ie bluez or ModemManager) to refer to that device, and client programs
+        use it get additional information from those services which NM does not
+        provide. The Udi is not guaranteed to be consistent across reboots or
+        hotplugs of the hardware. If you're looking for a way to uniquely track
+        each device in your application, use the object path. If you're looking
+        for a way to track a specific piece of hardware across reboot or hotplug,
+        use a MAC address or USB serial number.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Interface">
   <title>The "Interface" property</title>
@@ -171,7 +214,8 @@ Udi  readable   s
 <programlisting>
 Interface  readable   s
 </programlisting>
-<para>The name of the device's control (and often data) interface.</para>
+<para>        The name of the device's control (and often data) interface.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.IpInterface">
   <title>The "IpInterface" property</title>
@@ -179,7 +223,11 @@ Interface  readable   s
 <programlisting>
 IpInterface  readable   s
 </programlisting>
-<para>The name of the device's data interface when available.  This property         may not refer to the actual data interface until the device has         successfully established a data connection, indicated by the device's         State becoming ACTIVATED.</para>
+<para>        The name of the device's data interface when available. This property may
+        not refer to the actual data interface until the device has successfully
+        established a data connection, indicated by the device's State becoming
+        ACTIVATED.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Driver">
   <title>The "Driver" property</title>
@@ -187,7 +235,8 @@ IpInterface  readable   s
 <programlisting>
 Driver  readable   s
 </programlisting>
-<para>The driver handling the device.</para>
+<para>        The driver handling the device.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.DriverVersion">
   <title>The "DriverVersion" property</title>
@@ -195,7 +244,8 @@ Driver  readable   s
 <programlisting>
 DriverVersion  readable   s
 </programlisting>
-<para>The version of the driver handling the device.</para>
+<para>        The version of the driver handling the device.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.FirmwareVersion">
   <title>The "FirmwareVersion" property</title>
@@ -203,7 +253,8 @@ DriverVersion  readable   s
 <programlisting>
 FirmwareVersion  readable   s
 </programlisting>
-<para>The firmware version for the device.</para>
+<para>        The firmware version for the device.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Capabilities">
   <title>The "Capabilities" property</title>
@@ -211,7 +262,9 @@ FirmwareVersion  readable   s
 <programlisting>
 Capabilities  readable   u
 </programlisting>
-<para>Flags describing the capabilities of the device.</para>
+<para>        Flags describing the capabilities of the device.
+</para><para>        Returns: <link linkend="NMDeviceCapabilities">NMDeviceCapabilities</link>
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Ip4Address">
   <title>The "Ip4Address" property</title>
@@ -219,7 +272,9 @@ Capabilities  readable   u
 <programlisting>
 Ip4Address  readable   u
 </programlisting>
-<para>DEPRECATED; use the 'Addresses' property of the 'Ip4Config' object instead.</para>
+<para>        DEPRECATED; use the 'Addresses' property of the 'Ip4Config' object
+        instead.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.State">
   <title>The "State" property</title>
@@ -227,7 +282,9 @@ Ip4Address  readable   u
 <programlisting>
 State  readable   u
 </programlisting>
-<para>The current state of the device.</para>
+<para>        The current state of the device.
+</para><para>        Returns: <link linkend="NMDeviceState">NMDeviceState</link>
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.StateReason">
   <title>The "StateReason" property</title>
@@ -235,7 +292,9 @@ State  readable   u
 <programlisting>
 StateReason  readable   (uu)
 </programlisting>
-<para>The current state and reason for changing to that state.</para>
+<para>        The current state and reason for changing to that state.
+</para><para>        Returns: A tuple of  <link linkend="NMDeviceState">NMDeviceState</link> and  <link linkend="NMDeviceStateReason">NMDeviceStateReason</link>.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.ActiveConnection">
   <title>The "ActiveConnection" property</title>
@@ -243,7 +302,11 @@ StateReason  readable   (uu)
 <programlisting>
 ActiveConnection  readable   o
 </programlisting>
-<para>Object path of an ActiveConnection object that "owns" this device during         activation.  The ActiveConnection object tracks the life-cycle of a         connection to a specific network and implements the         org.freedesktop.NetworkManager.Connection.Active D-Bus interface.</para>
+<para>        Object path of an ActiveConnection object that "owns" this device during
+        activation. The ActiveConnection object tracks the life-cycle of a
+        connection to a specific network and implements the
+        org.freedesktop.NetworkManager.Connection.Active D-Bus interface.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Ip4Config">
   <title>The "Ip4Config" property</title>
@@ -251,7 +314,10 @@ ActiveConnection  readable   o
 <programlisting>
 Ip4Config  readable   o
 </programlisting>
-<para>Object path of the Ip4Config object describing the configuration of the device.  Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state.</para>
+<para>        Object path of the Ip4Config object describing the configuration of the
+        device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED
+        state.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Dhcp4Config">
   <title>The "Dhcp4Config" property</title>
@@ -259,7 +325,10 @@ Ip4Config  readable   o
 <programlisting>
 Dhcp4Config  readable   o
 </programlisting>
-<para>Object path of the Dhcp4Config object describing the DHCP options returned by the DHCP server.  Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state.</para>
+<para>        Object path of the Dhcp4Config object describing the DHCP options returned
+        by the DHCP server. Only valid when the device is in the
+        NM_DEVICE_STATE_ACTIVATED state.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Ip6Config">
   <title>The "Ip6Config" property</title>
@@ -267,7 +336,10 @@ Dhcp4Config  readable   o
 <programlisting>
 Ip6Config  readable   o
 </programlisting>
-<para>Object path of the Ip6Config object describing the configuration of the device.  Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state.</para>
+<para>        Object path of the Ip6Config object describing the configuration of the
+        device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED
+        state.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Dhcp6Config">
   <title>The "Dhcp6Config" property</title>
@@ -275,7 +347,10 @@ Ip6Config  readable   o
 <programlisting>
 Dhcp6Config  readable   o
 </programlisting>
-<para>Object path of the Dhcp6Config object describing the DHCP options         returned by the DHCP server.  Only valid when the device is in the         NM_DEVICE_STATE_ACTIVATED state.</para>
+<para>        Object path of the Dhcp6Config object describing the DHCP options returned
+        by the DHCP server. Only valid when the device is in the
+        NM_DEVICE_STATE_ACTIVATED state.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Managed">
   <title>The "Managed" property</title>
@@ -283,7 +358,11 @@ Dhcp6Config  readable   o
 <programlisting>
 Managed  readwrite  b
 </programlisting>
-<para>Whether or not this device is managed by NetworkManager. Setting this         property has a similar effect to configuring the device as unmanaged         via the keyfile.unmanaged-devices setting in NetworkManager.conf.         Changes to this value are not persistent and lost after NetworkManager         restart.</para>
+<para>        Whether or not this device is managed by NetworkManager. Setting this
+        property has a similar effect to configuring the device as unmanaged via
+        the keyfile.unmanaged-devices setting in NetworkManager.conf. Changes to
+        this value are not persistent and lost after NetworkManager restart.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Autoconnect">
   <title>The "Autoconnect" property</title>
@@ -291,7 +370,12 @@ Managed  readwrite  b
 <programlisting>
 Autoconnect  readwrite  b
 </programlisting>
-<para>If TRUE, indicates the device is allowed to autoconnect.  If FALSE,         manual intervention is required before the device will automatically         connect to a known network, such as activating a connection using the         device, or setting this property to TRUE.  This property cannot be         set to TRUE for default-unmanaged devices, since they never autoconnect.</para>
+<para>        If TRUE, indicates the device is allowed to autoconnect. If FALSE, manual
+        intervention is required before the device will automatically connect to a
+        known network, such as activating a connection using the device, or
+        setting this property to TRUE. This property cannot be set to TRUE for
+        default-unmanaged devices, since they never autoconnect.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.FirmwareMissing">
   <title>The "FirmwareMissing" property</title>
@@ -299,7 +383,9 @@ Autoconnect  readwrite  b
 <programlisting>
 FirmwareMissing  readable   b
 </programlisting>
-<para>If TRUE, indicates the device is likely missing firmware necessary for         its operation.</para>
+<para>        If TRUE, indicates the device is likely missing firmware necessary for its
+        operation.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.NmPluginMissing">
   <title>The "NmPluginMissing" property</title>
@@ -307,7 +393,9 @@ FirmwareMissing  readable   b
 <programlisting>
 NmPluginMissing  readable   b
 </programlisting>
-<para>If TRUE, indicates the NetworkManager plugin for the device is likely         missing or misconfigured.</para>
+<para>        If TRUE, indicates the NetworkManager plugin for the device is likely
+        missing or misconfigured.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.DeviceType">
   <title>The "DeviceType" property</title>
@@ -315,7 +403,9 @@ NmPluginMissing  readable   b
 <programlisting>
 DeviceType  readable   u
 </programlisting>
-<para>The general type of the network device; ie Ethernet, WiFi, etc.</para>
+<para>        The general type of the network device; ie Ethernet, WiFi, etc.
+</para><para>        Returns: <link linkend="NMDeviceType">NMDeviceType</link>
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.AvailableConnections">
   <title>The "AvailableConnections" property</title>
@@ -323,7 +413,9 @@ DeviceType  readable   u
 <programlisting>
 AvailableConnections  readable   ao
 </programlisting>
-<para>An array of object paths of every configured connection that is currently 'available' through this device.</para>
+<para>        An array of object paths of every configured connection that is currently
+        'available' through this device.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.PhysicalPortId">
   <title>The "PhysicalPortId" property</title>
@@ -331,7 +423,11 @@ AvailableConnections  readable   ao
 <programlisting>
 PhysicalPortId  readable   s
 </programlisting>
-<para>If non-empty, an (opaque) indicator of the physical network         port associated with the device. This can be used to recognize  when two seemingly-separate hardware devices are actually just  different virtual interfaces to the same physical port.</para>
+<para>        If non-empty, an (opaque) indicator of the physical network port
+        associated with the device. This can be used to recognize when two
+        seemingly-separate hardware devices are actually just different virtual
+        interfaces to the same physical port.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Mtu">
   <title>The "Mtu" property</title>
@@ -339,7 +435,8 @@ PhysicalPortId  readable   s
 <programlisting>
 Mtu  readable   u
 </programlisting>
-<para>The device MTU (maximum transmission unit).</para>
+<para>        The device MTU (maximum transmission unit).
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Metered">
   <title>The "Metered" property</title>
@@ -347,7 +444,10 @@ Mtu  readable   u
 <programlisting>
 Metered  readable   u
 </programlisting>
-<para>Whether the amount of traffic flowing through the device is         subject to limitations, for example set by service providers.</para>
+<para>        Whether the amount of traffic flowing through the device is subject to
+        limitations, for example set by service providers.
+</para><para>        Returns: <link linkend="NMMetered">NMMetered</link>
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.LldpNeighbors">
   <title>The "LldpNeighbors" property</title>
@@ -355,7 +455,9 @@ Metered  readable   u
 <programlisting>
 LldpNeighbors  readable   aa{sv}
 </programlisting>
-<para>Array of LLDP neighbors; each element is a dictionary mapping         LLDP TLV names to variant boxed values.</para>
+<para>        Array of LLDP neighbors; each element is a dictionary mapping LLDP TLV
+        names to variant boxed values.
+</para>
 </refsect2>
 <refsect2 role="property" id="gdbus-property-org-freedesktop-NetworkManager-Device.Real">
   <title>The "Real" property</title>
@@ -363,7 +465,10 @@ LldpNeighbors  readable   aa{sv}
 <programlisting>
 Real  readable   b
 </programlisting>
-<para>True if the device exists, or False for placeholder devices that         do not yet exist but could be automatically created by NetworkManager         if one of their AvailableConnections was activated.</para>
+<para>        True if the device exists, or False for placeholder devices that do not
+        yet exist but could be automatically created by NetworkManager if one of
+        their AvailableConnections was activated.
+</para>
 </refsect2>
 </refsect1>
 </refentry>