NetworkManager D-Bus API Types: NetworkManager Reference Manual

## NetworkManager D-Bus API Types NetworkManager D-Bus API Types |

### 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.

#### Values

NM_CAPABILITY_TEAM | = `1` | Teams can be managed |

### enum NMState

NMState values indicate the current overall networking state.

#### Values

NM_STATE_UNKNOWN | = `0` | Networking state is unknown. This indicates a daemon error that makes it unable to reasonably assess the state. In such event the applications are expected to assume Internet connectivity might be present and not disable controls that require network access. The graphical shells may hide the network accessibility indicator altogether since no meaningful status indication can be provided. |
NM_STATE_ASLEEP | = `10` | Networking is not enabled, the system is being suspended or resumed from suspend. |
NM_STATE_DISCONNECTED | = `20` | There is no active network connection. The graphical shell should indicate no network connectivity and the applications should not attempt to access the network. |
NM_STATE_DISCONNECTING | = `30` | Network connections are being cleaned up. The applications should tear down their network sessions. |
NM_STATE_CONNECTING | = `40` | A network connection is being started The graphical shell should indicate the network is being connected while the applications should still make no attempts to connect the network. |
NM_STATE_CONNECTED_LOCAL | = `50` | There is only local IPv4 and/or IPv6 connectivity, but no default route to access the Internet. The graphical shell should indicate no network connectivity. |
NM_STATE_CONNECTED_SITE | = `60` | There is only site-wide IPv4 and/or IPv6 connectivity. This means a default route is available, but the Internet connectivity check (see "Connectivity" property) did not succeed. The graphical shell should indicate limited network connectivity. |
NM_STATE_CONNECTED_GLOBAL | = `70` | There is global IPv4 and/or IPv6 Internet connectivity This means the Internet connectivity check succeeded, the graphical shell should indicate full network connectivity. |

### enum NMConnectivityState

#### Values

NM_CONNECTIVITY_UNKNOWN | = `0` | Network connectivity is unknown. This means the connectivity checks are disabled (e.g. on server installations) or has not run yet. The graphical shell should assume the Internet connection might be available and not present a captive portal window. |
NM_CONNECTIVITY_NONE | = `1` | The host is not connected to any network. There's no active connection that contains a default route to the internet and thus it makes no sense to even attempt a connectivity check. The graphical shell should use this state to indicate the network connection is unavailable. |
NM_CONNECTIVITY_PORTAL | = `2` | The Internet connection is hijacked by a captive portal gateway. The graphical shell may open a sandboxed web browser window (because the captive portals typically attempt a man-in-the-middle attacks agains the https connections) for the purpose of authenticating to a gateway and retrigger the connectivity check with CheckConnectivity() when the browser window is dismissed. |
NM_CONNECTIVITY_LIMITED | = `3` | The host is connected to a network, does not appear to be able to reach the full Internet, but a captive portal has not been detected. |
NM_CONNECTIVITY_FULL | = `4` | The host is connected to a network, and appears to be able to reach the full Internet. |

### enum NMDeviceType

NMDeviceType values indicate the type of hardware represented by a device object.

#### Values

NM_DEVICE_TYPE_UNKNOWN | = `0` | unknown device |
NM_DEVICE_TYPE_GENERIC | = `14` | generic support for unrecognized device types |
NM_DEVICE_TYPE_ETHERNET | = `1` | a wired ethernet device |
NM_DEVICE_TYPE_WIFI | = `2` | an 802.11 WiFi device |
NM_DEVICE_TYPE_UNUSED1 | = `3` | not used |
NM_DEVICE_TYPE_UNUSED2 | = `4` | not used |
NM_DEVICE_TYPE_BT | = `5` | a Bluetooth device supporting PAN or DUN access protocols |
NM_DEVICE_TYPE_OLPC_MESH | = `6` | an OLPC XO mesh networking device |
NM_DEVICE_TYPE_WIMAX | = `7` | an 802.16e Mobile WiMAX broadband device |
NM_DEVICE_TYPE_MODEM | = `8` | a modem supporting analog telephone, CDMA/EVDO, GSM/UMTS, or LTE network access protocols |
NM_DEVICE_TYPE_INFINIBAND | = `9` | an IP-over-InfiniBand device |
NM_DEVICE_TYPE_BOND | = `10` | a bond master interface |
NM_DEVICE_TYPE_VLAN | = `11` | an 802.1Q VLAN interface |
NM_DEVICE_TYPE_ADSL | = `12` | ADSL modem |
NM_DEVICE_TYPE_BRIDGE | = `13` | a bridge master interface |
NM_DEVICE_TYPE_TEAM | = `15` | a team master interface |
NM_DEVICE_TYPE_TUN | = `16` | a TUN or TAP interface |
NM_DEVICE_TYPE_IP_TUNNEL | = `17` | a IP tunnel interface |
NM_DEVICE_TYPE_MACVLAN | = `18` | a MACVLAN interface |
NM_DEVICE_TYPE_VXLAN | = `19` | a VXLAN interface |
NM_DEVICE_TYPE_VETH | = `20` | a VETH interface |
NM_DEVICE_TYPE_MACSEC | = `21` | a MACsec interface |
NM_DEVICE_TYPE_DUMMY | = `22` | a dummy interface |
NM_DEVICE_TYPE_PPP | = `23` | a PPP interface |
NM_DEVICE_TYPE_OVS_INTERFACE | = `24` | a OpenVSwitch interface |
NM_DEVICE_TYPE_OVS_PORT | = `25` | a OpenVSwitch port |
NM_DEVICE_TYPE_OVS_BRIDGE | = `26` | a OpenVSwitch bridge |

### enum NMDeviceCapabilities

General device capability flags.

#### Values

NM_DEVICE_CAP_NONE | = `0x00000000` | device has no special capabilities |
NM_DEVICE_CAP_NM_SUPPORTED | = `0x00000001` | NetworkManager supports this device |
NM_DEVICE_CAP_CARRIER_DETECT | = `0x00000002` | this device can indicate carrier status |
NM_DEVICE_CAP_IS_SOFTWARE | = `0x00000004` | this device is a software device |
NM_DEVICE_CAP_SRIOV | = `0x00000008` | this device supports single-root I/O virtualization |

### enum NMDeviceWifiCapabilities

802.11 specific device encryption and authentication capabilities.

#### Values

NM_WIFI_DEVICE_CAP_NONE | = `0x00000000` | device has no encryption/authentication capabilities |
NM_WIFI_DEVICE_CAP_CIPHER_WEP40 | = `0x00000001` | device supports 40/64-bit WEP encryption |
NM_WIFI_DEVICE_CAP_CIPHER_WEP104 | = `0x00000002` | device supports 104/128-bit WEP encryption |
NM_WIFI_DEVICE_CAP_CIPHER_TKIP | = `0x00000004` | device supports TKIP encryption |
NM_WIFI_DEVICE_CAP_CIPHER_CCMP | = `0x00000008` | device supports AES/CCMP encryption |
NM_WIFI_DEVICE_CAP_WPA | = `0x00000010` | device supports WPA1 authentication |
NM_WIFI_DEVICE_CAP_RSN | = `0x00000020` | device supports WPA2/RSN authentication |
NM_WIFI_DEVICE_CAP_AP | = `0x00000040` | device supports Access Point mode |
NM_WIFI_DEVICE_CAP_ADHOC | = `0x00000080` | device supports Ad-Hoc mode |
NM_WIFI_DEVICE_CAP_FREQ_VALID | = `0x00000100` | device reports frequency capabilities |
NM_WIFI_DEVICE_CAP_FREQ_2GHZ | = `0x00000200` | device supports 2.4GHz frequencies |
NM_WIFI_DEVICE_CAP_FREQ_5GHZ | = `0x00000400` | device supports 5GHz frequencies |

### enum NM80211ApFlags

802.11 access point flags.

#### Values

NM_802_11_AP_FLAGS_NONE | = `0x00000000` | access point has no special capabilities |
NM_802_11_AP_FLAGS_PRIVACY | = `0x00000001` | access point requires authentication and encryption (usually means WEP) |
NM_802_11_AP_FLAGS_WPS | = `0x00000002` | access point supports some WPS method |
NM_802_11_AP_FLAGS_WPS_PBC | = `0x00000004` | access point supports push-button WPS |
NM_802_11_AP_FLAGS_WPS_PIN | = `0x00000008` | access point supports PIN-based WPS |

### enum NM80211ApSecurityFlags

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

NM_802_11_AP_SEC_NONE | = `0x00000000` | the access point has no special security requirements |
NM_802_11_AP_SEC_PAIR_WEP40 | = `0x00000001` | 40/64-bit WEP is supported for pairwise/unicast encryption |
NM_802_11_AP_SEC_PAIR_WEP104 | = `0x00000002` | 104/128-bit WEP is supported for pairwise/unicast encryption |
NM_802_11_AP_SEC_PAIR_TKIP | = `0x00000004` | TKIP is supported for pairwise/unicast encryption |
NM_802_11_AP_SEC_PAIR_CCMP | = `0x00000008` | AES/CCMP is supported for pairwise/unicast encryption |
NM_802_11_AP_SEC_GROUP_WEP40 | = `0x00000010` | 40/64-bit WEP is supported for group/broadcast encryption |
NM_802_11_AP_SEC_GROUP_WEP104 | = `0x00000020` | 104/128-bit WEP is supported for group/broadcast encryption |
NM_802_11_AP_SEC_GROUP_TKIP | = `0x00000040` | TKIP is supported for group/broadcast encryption |
NM_802_11_AP_SEC_GROUP_CCMP | = `0x00000080` | AES/CCMP is supported for group/broadcast encryption |
NM_802_11_AP_SEC_KEY_MGMT_PSK | = `0x00000100` | WPA/RSN Pre-Shared Key encryption is supported |
NM_802_11_AP_SEC_KEY_MGMT_802_1X | = `0x00000200` | 802.1x authentication and key management is supported |

### enum NM80211Mode

Indicates the 802.11 mode an access point or device is currently in.

#### Values

NM_802_11_MODE_UNKNOWN | = `0` | the device or access point mode is unknown |
NM_802_11_MODE_ADHOC | = `1` | for both devices and access point objects, indicates the object is part of an Ad-Hoc 802.11 network without a central coordinating access point. |
NM_802_11_MODE_INFRA | = `2` | the device or access point is in infrastructure mode. For devices, this indicates the device is an 802.11 client/station. For access point objects, this indicates the object is an access point that provides connectivity to clients. |
NM_802_11_MODE_AP | = `3` | the device is an access point/hotspot. Not valid for access point objects; used only for hotspot mode on the local machine. |

### enum NMBluetoothCapabilities

NMBluetoothCapabilities values indicate the usable capabilities of a Bluetooth device.

#### Values

NM_BT_CAPABILITY_NONE | = `0x00000000` | device has no usable capabilities |
NM_BT_CAPABILITY_DUN | = `0x00000001` | device provides Dial-Up Networking capability |
NM_BT_CAPABILITY_NAP | = `0x00000002` | device provides Network Access Point capability |

### enum NMDeviceModemCapabilities

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

NM_DEVICE_MODEM_CAPABILITY_NONE | = `0x00000000` | modem has no usable capabilities |
NM_DEVICE_MODEM_CAPABILITY_POTS | = `0x00000001` | modem uses the analog wired telephone network and is not a wireless/cellular device |
NM_DEVICE_MODEM_CAPABILITY_CDMA_EVDO | = `0x00000002` | modem supports at least one of CDMA 1xRTT, EVDO revision 0, EVDO revision A, or EVDO revision B |
NM_DEVICE_MODEM_CAPABILITY_GSM_UMTS | = `0x00000004` | modem supports at least one of GSM, GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability |
NM_DEVICE_MODEM_CAPABILITY_LTE | = `0x00000008` | modem has LTE data capability |

### enum NMWimaxNspNetworkType

WiMAX network type.

#### Values

NM_WIMAX_NSP_NETWORK_TYPE_UNKNOWN | = `0` | unknown network type |
NM_WIMAX_NSP_NETWORK_TYPE_HOME | = `1` | home network |
NM_WIMAX_NSP_NETWORK_TYPE_PARTNER | = `2` | partner network |
NM_WIMAX_NSP_NETWORK_TYPE_ROAMING_PARTNER | = `3` | roaming partner network |

### enum NMDeviceState

#### Values

NM_DEVICE_STATE_UNKNOWN | = `0` | the device's state is unknown |
NM_DEVICE_STATE_UNMANAGED | = `10` | the device is recognized, but not managed by NetworkManager |
NM_DEVICE_STATE_UNAVAILABLE | = `20` | the device is managed by NetworkManager, but is not available for use. Reasons may include the wireless switched off, missing firmware, no ethernet carrier, missing supplicant or modem manager, etc. |
NM_DEVICE_STATE_DISCONNECTED | = `30` | the device can be activated, but is currently idle and not connected to a network. |
NM_DEVICE_STATE_PREPARE | = `40` | the device is preparing the connection to the network. This may include operations like changing the MAC address, setting physical link properties, and anything else required to connect to the requested network. |
NM_DEVICE_STATE_CONFIG | = `50` | the device is connecting to the requested network. This may include operations like associating with the WiFi AP, dialing the modem, connecting to the remote Bluetooth device, etc. |
NM_DEVICE_STATE_NEED_AUTH | = `60` | the device requires more information to continue connecting to the requested network. This includes secrets like WiFi passphrases, login passwords, PIN codes, etc. |
NM_DEVICE_STATE_IP_CONFIG | = `70` | the device is requesting IPv4 and/or IPv6 addresses and routing information from the network. |
NM_DEVICE_STATE_IP_CHECK | = `80` | the device is checking whether further action is required for the requested network connection. This may include checking whether only local network access is available, whether a captive portal is blocking access to the Internet, etc. |
NM_DEVICE_STATE_SECONDARIES | = `90` | the device is waiting for a secondary connection (like a VPN) which must activated before the device can be activated |
NM_DEVICE_STATE_ACTIVATED | = `100` | the device has a network connection, either local or global. |
NM_DEVICE_STATE_DEACTIVATING | = `110` | a disconnection from the current network connection was requested, and the device is cleaning up resources used for that connection. The network connection may still be valid. |
NM_DEVICE_STATE_FAILED | = `120` | the device failed to connect to the requested network and is cleaning up the connection request |

### enum NMDeviceStateReason

Device state change reason codes

#### Values

NM_DEVICE_STATE_REASON_NONE | = `0` | No reason given |
NM_DEVICE_STATE_REASON_UNKNOWN | = `1` | Unknown error |
NM_DEVICE_STATE_REASON_NOW_MANAGED | = `2` | Device is now managed |
NM_DEVICE_STATE_REASON_NOW_UNMANAGED | = `3` | Device is now unmanaged |
NM_DEVICE_STATE_REASON_CONFIG_FAILED | = `4` | The device could not be readied for configuration |
NM_DEVICE_STATE_REASON_IP_CONFIG_UNAVAILABLE | = `5` | IP configuration could not be reserved (no available address, timeout, etc) |
NM_DEVICE_STATE_REASON_IP_CONFIG_EXPIRED | = `6` | The IP config is no longer valid |
NM_DEVICE_STATE_REASON_NO_SECRETS | = `7` | Secrets were required, but not provided |
NM_DEVICE_STATE_REASON_SUPPLICANT_DISCONNECT | = `8` | 802.1x supplicant disconnected |
NM_DEVICE_STATE_REASON_SUPPLICANT_CONFIG_FAILED | = `9` | 802.1x supplicant configuration failed |
NM_DEVICE_STATE_REASON_SUPPLICANT_FAILED | = `10` | 802.1x supplicant failed |
NM_DEVICE_STATE_REASON_SUPPLICANT_TIMEOUT | = `11` | 802.1x supplicant took too long to authenticate |
NM_DEVICE_STATE_REASON_PPP_START_FAILED | = `12` | PPP service failed to start |
NM_DEVICE_STATE_REASON_PPP_DISCONNECT | = `13` | PPP service disconnected |
NM_DEVICE_STATE_REASON_PPP_FAILED | = `14` | PPP failed |
NM_DEVICE_STATE_REASON_DHCP_START_FAILED | = `15` | DHCP client failed to start |
NM_DEVICE_STATE_REASON_DHCP_ERROR | = `16` | DHCP client error |
NM_DEVICE_STATE_REASON_DHCP_FAILED | = `17` | DHCP client failed |
NM_DEVICE_STATE_REASON_SHARED_START_FAILED | = `18` | Shared connection service failed to start |
NM_DEVICE_STATE_REASON_SHARED_FAILED | = `19` | Shared connection service failed |
NM_DEVICE_STATE_REASON_AUTOIP_START_FAILED | = `20` | AutoIP service failed to start |
NM_DEVICE_STATE_REASON_AUTOIP_ERROR | = `21` | AutoIP service error |
NM_DEVICE_STATE_REASON_AUTOIP_FAILED | = `22` | AutoIP service failed |
NM_DEVICE_STATE_REASON_MODEM_BUSY | = `23` | The line is busy |
NM_DEVICE_STATE_REASON_MODEM_NO_DIAL_TONE | = `24` | No dial tone |
NM_DEVICE_STATE_REASON_MODEM_NO_CARRIER | = `25` | No carrier could be established |
NM_DEVICE_STATE_REASON_MODEM_DIAL_TIMEOUT | = `26` | The dialing request timed out |
NM_DEVICE_STATE_REASON_MODEM_DIAL_FAILED | = `27` | The dialing attempt failed |
NM_DEVICE_STATE_REASON_MODEM_INIT_FAILED | = `28` | Modem initialization failed |
NM_DEVICE_STATE_REASON_GSM_APN_FAILED | = `29` | Failed to select the specified APN |
NM_DEVICE_STATE_REASON_GSM_REGISTRATION_NOT_SEARCHING | = `30` | Not searching for networks |
NM_DEVICE_STATE_REASON_GSM_REGISTRATION_DENIED | = `31` | Network registration denied |
NM_DEVICE_STATE_REASON_GSM_REGISTRATION_TIMEOUT | = `32` | Network registration timed out |
NM_DEVICE_STATE_REASON_GSM_REGISTRATION_FAILED | = `33` | Failed to register with the requested network |
NM_DEVICE_STATE_REASON_GSM_PIN_CHECK_FAILED | = `34` | PIN check failed |
NM_DEVICE_STATE_REASON_FIRMWARE_MISSING | = `35` | Necessary firmware for the device may be missing |
NM_DEVICE_STATE_REASON_REMOVED | = `36` | The device was removed |
NM_DEVICE_STATE_REASON_SLEEPING | = `37` | NetworkManager went to sleep |
NM_DEVICE_STATE_REASON_CONNECTION_REMOVED | = `38` | The device's active connection disappeared |
NM_DEVICE_STATE_REASON_USER_REQUESTED | = `39` | Device disconnected by user or client |
NM_DEVICE_STATE_REASON_CARRIER | = `40` | Carrier/link changed |
NM_DEVICE_STATE_REASON_CONNECTION_ASSUMED | = `41` | The device's existing connection was assumed |
NM_DEVICE_STATE_REASON_SUPPLICANT_AVAILABLE | = `42` | The supplicant is now available |
NM_DEVICE_STATE_REASON_MODEM_NOT_FOUND | = `43` | The modem could not be found |
NM_DEVICE_STATE_REASON_BT_FAILED | = `44` | The Bluetooth connection failed or timed out |
NM_DEVICE_STATE_REASON_GSM_SIM_NOT_INSERTED | = `45` | GSM Modem's SIM Card not inserted |
NM_DEVICE_STATE_REASON_GSM_SIM_PIN_REQUIRED | = `46` | GSM Modem's SIM Pin required |
NM_DEVICE_STATE_REASON_GSM_SIM_PUK_REQUIRED | = `47` | GSM Modem's SIM Puk required |
NM_DEVICE_STATE_REASON_GSM_SIM_WRONG | = `48` | GSM Modem's SIM wrong |
NM_DEVICE_STATE_REASON_INFINIBAND_MODE | = `49` | InfiniBand device does not support connected mode |
NM_DEVICE_STATE_REASON_DEPENDENCY_FAILED | = `50` | A dependency of the connection failed |
NM_DEVICE_STATE_REASON_BR2684_FAILED | = `51` | Problem with the RFC 2684 Ethernet over ADSL bridge |
NM_DEVICE_STATE_REASON_MODEM_MANAGER_UNAVAILABLE | = `52` | ModemManager not running |
NM_DEVICE_STATE_REASON_SSID_NOT_FOUND | = `53` | The WiFi network could not be found |
NM_DEVICE_STATE_REASON_SECONDARY_CONNECTION_FAILED | = `54` | A secondary connection of the base connection failed |
NM_DEVICE_STATE_REASON_DCB_FCOE_FAILED | = `55` | DCB or FCoE setup failed |
NM_DEVICE_STATE_REASON_TEAMD_CONTROL_FAILED | = `56` | teamd control failed |
NM_DEVICE_STATE_REASON_MODEM_FAILED | = `57` | Modem failed or no longer available |
NM_DEVICE_STATE_REASON_MODEM_AVAILABLE | = `58` | Modem now ready and available |
NM_DEVICE_STATE_REASON_SIM_PIN_INCORRECT | = `59` | SIM PIN was incorrect |
NM_DEVICE_STATE_REASON_NEW_ACTIVATION | = `60` | New connection activation was enqueued |
NM_DEVICE_STATE_REASON_PARENT_CHANGED | = `61` | the device's parent changed |
NM_DEVICE_STATE_REASON_PARENT_MANAGED_CHANGED | = `62` | the device parent's management changed |
NM_DEVICE_STATE_REASON_OVSDB_FAILED | = `63` | problem communicating with OpenVSwitch database |
NM_DEVICE_STATE_REASON_IP_ADDRESS_DUPLICATE | = `64` | a duplicate IP address was detected |
NM_DEVICE_STATE_REASON_IP_METHOD_UNSUPPORTED | = `65` | The selected IP method is not supported |

### enum NMMetered

Since: 1.2

#### Values

NM_METERED_UNKNOWN | = `0` | The metered status is unknown |
NM_METERED_YES | = `1` | Metered, the value was statically set |
NM_METERED_NO | = `2` | Not metered, the value was statically set |
NM_METERED_GUESS_YES | = `3` | Metered, the value was guessed |
NM_METERED_GUESS_NO | = `4` | Not metered, the value was guessed |

### enum NMActiveConnectionState

NMActiveConnectionState values indicate the state of a connection to a specific network while it is starting, connected, or disconnecting from that network.

#### Values

NM_ACTIVE_CONNECTION_STATE_UNKNOWN | = `0` | the state of the connection is unknown |
NM_ACTIVE_CONNECTION_STATE_ACTIVATING | = `1` | a network connection is being prepared |
NM_ACTIVE_CONNECTION_STATE_ACTIVATED | = `2` | there is a connection to the network |
NM_ACTIVE_CONNECTION_STATE_DEACTIVATING | = `3` | the network connection is being torn down and cleaned up |
NM_ACTIVE_CONNECTION_STATE_DEACTIVATED | = `4` | the network connection is disconnected and will be removed |

### enum NMActiveConnectionStateReason

Active connection state reasons.

Since: 1.8

#### Values

NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN | = `0` | The reason for the active connection state change is unknown. |
NM_ACTIVE_CONNECTION_STATE_REASON_NONE | = `1` | No reason was given for the active connection state change. |
NM_ACTIVE_CONNECTION_STATE_REASON_USER_DISCONNECTED | = `2` | The active connection changed state because the user disconnected it. |
NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED | = `3` | The active connection changed state because the device it was using was disconnected. |
NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_STOPPED | = `4` | The service providing the VPN connection was stopped. |
NM_ACTIVE_CONNECTION_STATE_REASON_IP_CONFIG_INVALID | = `5` | The IP config of the active connection was invalid. |
NM_ACTIVE_CONNECTION_STATE_REASON_CONNECT_TIMEOUT | = `6` | The connection attempt to the VPN service timed out. |
NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT | = `7` | A timeout occurred while starting the service providing the VPN connection. |
NM_ACTIVE_CONNECTION_STATE_REASON_SERVICE_START_FAILED | = `8` | Starting the service providing the VPN connection failed. |
NM_ACTIVE_CONNECTION_STATE_REASON_NO_SECRETS | = `9` | Necessary secrets for the connection were not provided. |
NM_ACTIVE_CONNECTION_STATE_REASON_LOGIN_FAILED | = `10` | Authentication to the server failed. |
NM_ACTIVE_CONNECTION_STATE_REASON_CONNECTION_REMOVED | = `11` | The connection was deleted from settings. |
NM_ACTIVE_CONNECTION_STATE_REASON_DEPENDENCY_FAILED | = `12` | Master connection of this connection failed to activate. |
NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REALIZE_FAILED | = `13` | Could not create the software device link. |
NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_REMOVED | = `14` | The device this connection depended on disappeared. |

### enum NMSecretAgentGetSecretsFlags

NMSecretAgentGetSecretsFlags values modify the behavior of a GetSecrets request.

#### Values

NM_SECRET_AGENT_GET_SECRETS_FLAG_NONE | = `0x0` | no special behavior; by default no user interaction is allowed and requests for secrets are fulfilled from persistent storage, or if no secrets are available an error is returned. |
NM_SECRET_AGENT_GET_SECRETS_FLAG_ALLOW_INTERACTION | = `0x1` | allows the request to interact with the user, possibly prompting via UI for secrets if any are required, or if none are found in persistent storage. |
NM_SECRET_AGENT_GET_SECRETS_FLAG_REQUEST_NEW | = `0x2` | explicitly prompt for new secrets from the user. This flag signals that NetworkManager thinks any existing secrets are invalid or wrong. This flag implies that interaction is allowed. |
NM_SECRET_AGENT_GET_SECRETS_FLAG_USER_REQUESTED | = `0x4` | set if the request was initiated by user-requested action via the D-Bus interface, as opposed to automatically initiated by NetworkManager in response to (for example) scan results or carrier changes. |
NM_SECRET_AGENT_GET_SECRETS_FLAG_WPS_PBC_ACTIVE | = `0x8` | indicates that WPS enrollment is active with PBC method. The agent may suggest that the user pushes a button on the router instead of supplying a PSK. |
NM_SECRET_AGENT_GET_SECRETS_FLAG_ONLY_SYSTEM | = `0x80000000` | Internal flag, not part of the D-Bus API. |
NM_SECRET_AGENT_GET_SECRETS_FLAG_NO_ERRORS | = `0x40000000` | Internal flag, not part of the D-Bus API. |

### enum NMSecretAgentCapabilities

NMSecretAgentCapabilities indicate various capabilities of the agent.

#### Values

NM_SECRET_AGENT_CAPABILITY_NONE | = `0x0` | the agent supports no special capabilities |
NM_SECRET_AGENT_CAPABILITY_VPN_HINTS | = `0x1` | the agent supports passing hints to VPN plugin authentication dialogs. |

### enum NMIPTunnelMode

The tunneling mode.

Since: 1.2

#### Values

NM_IP_TUNNEL_MODE_UNKNOWN | = `0` | Unknown/unset tunnel mode |
NM_IP_TUNNEL_MODE_IPIP | = `1` | IP in IP tunnel |
NM_IP_TUNNEL_MODE_GRE | = `2` | GRE tunnel |
NM_IP_TUNNEL_MODE_SIT | = `3` | SIT tunnel |
NM_IP_TUNNEL_MODE_ISATAP | = `4` | ISATAP tunnel |
NM_IP_TUNNEL_MODE_VTI | = `5` | VTI tunnel |
NM_IP_TUNNEL_MODE_IP6IP6 | = `6` | IPv6 in IPv6 tunnel |
NM_IP_TUNNEL_MODE_IPIP6 | = `7` | IPv4 in IPv6 tunnel |
NM_IP_TUNNEL_MODE_IP6GRE | = `8` | IPv6 GRE tunnel |
NM_IP_TUNNEL_MODE_VTI6 | = `9` | IPv6 VTI tunnel |

### enum NMCheckpointCreateFlags

The flags for CheckpointCreate call

Since: 1.4

#### Values

NM_CHECKPOINT_CREATE_FLAG_NONE | = `0` | no flags |
NM_CHECKPOINT_CREATE_FLAG_DESTROY_ALL | = `0x01` | when creating a new checkpoint, destroy all existing ones. |
NM_CHECKPOINT_CREATE_FLAG_DELETE_NEW_CONNECTIONS | = `0x02` | upon rollback, delete any new connection added after the checkpoint (Since: 1.6) |
NM_CHECKPOINT_CREATE_FLAG_DISCONNECT_NEW_DEVICES | = `0x04` | upon rollback, disconnect any new device appeared after the checkpoint (Since: 1.6) |

### enum NMRollbackResult

The result of a checkpoint Rollback() operation for a specific device.

Since: 1.4

#### Values

NM_ROLLBACK_RESULT_OK | = `0` | the rollback succeeded. |
NM_ROLLBACK_RESULT_ERR_NO_DEVICE | = `1` | the device no longer exists. |
NM_ROLLBACK_RESULT_ERR_DEVICE_UNMANAGED | = `2` | the device is now unmanaged. |
NM_ROLLBACK_RESULT_ERR_FAILED | = `3` | other errors during rollback. |

### enum NMActivationStateFlags

Flags describing the current activation state.

Since: 1.10

#### Values

NM_ACTIVATION_STATE_FLAG_NONE | = `0` | an alias for numeric zero, no flags set. |
NM_ACTIVATION_STATE_FLAG_IS_MASTER | = `(1LL` | the device is a master. |
NM_ACTIVATION_STATE_FLAG_IS_SLAVE | = `(1LL` | the device is a slave. |
NM_ACTIVATION_STATE_FLAG_LAYER2_READY | = `(1LL` | layer2 is activated and ready. |
NM_ACTIVATION_STATE_FLAG_IP4_READY | = `(1LL` | IPv4 setting is completed. |
NM_ACTIVATION_STATE_FLAG_IP6_READY | = `(1LL` | IPv6 setting is completed. |
NM_ACTIVATION_STATE_FLAG_MASTER_HAS_SLAVES | = `(1LL` | The master has any slave devices attached. This only makes sense if the device is a master. |

### enum NMSettingsUpdate2Flags

Since: 1.10.2

#### Values

NM_SETTINGS_UPDATE2_FLAG_NONE | = `0` | an alias for numeric zero, no flags set. |
NM_SETTINGS_UPDATE2_FLAG_TO_DISK | = `(1LL` | to persist the connection to disk. |
NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY | = `(1LL` | to make the connection in-memory only. If the connection was previously persistent, the corresponding file on disk is not deleted but merely the connection is decoupled from the file on disk. If you later delete an in-memory connection, the connection on disk will be deleted as well. |
NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED | = `(1LL` | this is like @NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, but if the connection has a corresponding file on disk, the association between the connection and the file is forgotten but the file is not modified. The difference to %NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY is if you later save the connection again to disk, a new file name will be chosen without overwriting the remaining file on disk. Also, if you delete the connection later, the file on disk will not be deleted. |
NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY | = `(1LL` | this is like @NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, but if the connection has a corresponding file on disk, the file on disk will be deleted. |
NM_SETTINGS_UPDATE2_FLAG_VOLATILE | = `(1LL` | This can be specified with either %NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_DETACHED or %NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY_ONLY. After making the connection in-memory only, the connection is marked as volatile. That means, if the connection is currently not active it will be deleted right away. Otherwise, it is marked to for deletion once the connection deactivates. A volatile connection cannot autoactivate again (because it's about to be deleted), but a manual activation will clear the volatile flag. |
NM_SETTINGS_UPDATE2_FLAG_BLOCK_AUTOCONNECT | = `(1LL` | usually, when the connection has autoconnect enabled and is modified, it becomes elegible to autoconnect right away. Setting this flag, disables autoconnect until the connection is manually activated. |