AutoIP service error
AutoIP service failed
AutoIP service failed to start
Problem with the RFC 2684 Ethernet over ADSL bridge
The Bluetooth connection failed or timed out
Carrier/link changed
The device could not be readied for configuration
The device's existing connection was assumed
The device's active connection disappeared
DCB or FCoE setup failed
A dependency of the connection failed
The device handler dispatcher returned an error. Since: 1.46
DHCP client error
DHCP client failed
DHCP client failed to start
Necessary firmware for the device may be missing
Failed to select the specified APN
PIN check failed
Network registration denied
Failed to register with the requested network
Not searching for networks
Network registration timed out
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 duplicate IP address was detected
The IP config is no longer valid
IP configuration could not be reserved (no available address, timeout, etc)
The selected IP method is not supported
Modem now ready and available
The line is busy
The dialing attempt failed
The dialing request timed out
Modem failed or no longer available
Modem initialization failed
ModemManager not running
No carrier could be established
No dial tone
The modem's operator code wasn't available, and auto-configuration was requested. Since: 1.56
The modem could not be found
NetworkManager was disabled (networking off). Since: 1.56
New connection activation was enqueued
Secrets were required, but not provided
No reason given
Device is now managed
Device is now unmanaged
problem communicating with Open vSwitch database
the device's parent changed
the device parent's management changed
The Wi-Fi P2P peer could not be found
PPP service disconnected
PPP failed
PPP service failed to start
The device was removed
A secondary connection of the base connection failed
Shared connection service failed
Shared connection service failed to start
SIM PIN was incorrect
NetworkManager went to sleep
configuration of SR-IOV parameters failed
The Wi-Fi network could not be found
The supplicant is now available
802.1x supplicant configuration failed
802.1x supplicant disconnected
802.1x supplicant failed
802.1x supplicant took too long to authenticate
teamd control failed
Unknown error
The device is unmanaged because the device type is unmanaged by default. Since: 1.48
The device is unmanaged because it is an external device and is unconfigured (down or without addresses). Since: 1.48
The device is unmanaged because the link is not initialized by udev. Since: 1.48
The device is unmanaged because networking is disabled or the system is suspended. Since: 1.56
The device is unmanaged because NetworkManager is quitting. Since: 1.48
Since: 1.48. Deprecated: 1.56: Use NM.DeviceStateReason.UNMANAGED_MANAGER_DISABLED instead.
The device is unmanaged by user decision in NetworkManager.conf ('unmanaged' in a [device*] section). Since: 1.48
The device is unmanaged by explicit user decision (e.g. 'nmcli device set $DEV managed no'). Since: 1.48
The device is unmanaged by user decision via settings plugin ('unmanaged-devices' for keyfile or 'NM_CONTROLLED=no' for ifcfg-rh). Since: 1.48
The device is unmanaged via udev rule. Since: 1.48
Device disconnected by user or client
Device state change reason codes