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. The name of the device's control (and often data) interface. 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. The driver handling the device. The version of the driver handling the device. The firmware version for the device. Flags describing the capabilities of the device. The IPv4 address bound to the device. FIXME: what about devices with >1 IP address? The current state of the device. The current state and reason for changing to that state. 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. 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. 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. 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. 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. Whether or not this device is managed by NetworkManager. 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. If TRUE, indicates the device is likely missing firmware necessary for its operation. The general type of the network device; ie Ethernet, WiFi, etc. An array of object paths of every configured connection that is currently 'available' through this device. Disconnects a device and prevents the device from automatically activating further connections without user intervention. The new state of the device. The previous state of the device. A reason for the state transition. The device is in an unknown state. The device is recognized but not managed by NetworkManager. The device cannot be used (carrier off, rfkill, etc). The device is not connected. The device is preparing to connect. The device is being configured. The device is awaiting secrets necessary to continue connection. The IP settings of the device are being requested and configured. The device's IP connectivity ability is being determined. The device is waiting for secondary connections to be activated. The device is active. The device's network connection is being torn down. The device is in a failure state following an attempt to activate it. The device type is unknown. The device is wired Ethernet device. The device is an 802.11 WiFi device. Unused Unused The device is Bluetooth device that provides PAN or DUN capabilities. The device is an OLPC mesh networking device. The device is an 802.16e Mobile WiMAX device. The device is a modem supporting one or more of analog telephone, CDMA/EVDO, GSM/UMTS/HSPA, or LTE standards to access a cellular or wireline data network. The device is an IP-capable InfiniBand interface. The device is a bond master interface. The device is a VLAN interface. The device is an ADSL device supporting PPPoE and PPPoATM protocols. Null capability. The device is supported by NetworkManager. The device supports carrier detection. The reason for the device state change is unknown. The state change is normal. The device is now managed. The device is no longer managed. The device could not be readied for configuration. IP configuration could not be reserved (no available address, timeout, etc). The IP configuration is no longer valid. Secrets were required, but not provided. The 802.1X supplicant disconnected from the access point or authentication server. Configuration of the 802.1X supplicant failed. The 802.1X supplicant quit or failed unexpectedly. The 802.1X supplicant took too long to authenticate. The PPP service failed to start within the allowed time. The PPP service disconnected unexpectedly. The PPP service quit or failed unexpectedly. The DHCP service failed to start within the allowed time. The DHCP service reported an unexpected error. The DHCP service quit or failed unexpectedly. The shared connection service failed to start. The shared connection service quit or failed unexpectedly. The AutoIP service failed to start. The AutoIP service reported an unexpected error. The AutoIP service quit or failed unexpectedly. Dialing failed because the line was busy. Dialing failed because there was no dial tone. Dialing failed because there was carrier. Dialing timed out. Dialing failed. Modem initialization failed. Failed to select the specified GSM APN. Not searching for networks. Network registration was denied. Network registration timed out. Failed to register with the requested GSM network. PIN check failed. Necessary firmware for the device may be missing. The device was removed. NetworkManager went to sleep. The device's active connection was removed or disappeared. A user or client requested the disconnection. The device's carrier/link changed. The device's existing connection was assumed. The 802.1x supplicant is now available. The modem could not be found. The Bluetooth connection timed out or failed. GSM Modem's SIM Card not inserted. GSM Modem's SIM Pin required. GSM Modem's SIM Puk required. GSM Modem's SIM wrong InfiniBand device does not support connected mode. A dependency of the connection failed. Problem with the RFC 2684 Ethernet over ADSL bridge. The device state. The reason for originally changing to the device state.