NM_DBUS_INTERFACE_DEVICE_VXLAN

#define NM_DBUS_INTERFACE_DEVICE_VXLAN         NM_DBUS_INTERFACE_DEVICE ".Vxlan"

@@ -908,7 +928,7 @@ extensions.

NM_CAPABILITY_TEAM

Teams can be managed. This means the team device plugin - is loaded.

+is loaded.

@@ -916,7 +936,7 @@ extensions.

NM_CAPABILITY_OVS

OpenVSwitch can be managed. This means the OVS device plugin - is loaded. Since: 1.24, 1.22.2

+is loaded. Since: 1.24

@@ -941,11 +961,11 @@ extensions.

NM_STATE_UNKNOWN

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.

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

@@ -953,7 +973,7 @@ extensions.

NM_STATE_ASLEEP

Networking is not enabled, the system is being suspended or - resumed from suspend.

+resumed from suspend.

@@ -961,8 +981,8 @@ extensions.

NM_STATE_DISCONNECTED

There is no active network connection. - The graphical shell should indicate no network connectivity and the - applications should not attempt to access the network.

+The graphical shell should indicate no network connectivity and the +applications should not attempt to access the network.

@@ -970,7 +990,7 @@ extensions.

NM_STATE_DISCONNECTING

Network connections are being cleaned up. - The applications should tear down their network sessions.

+The applications should tear down their network sessions.

@@ -978,8 +998,8 @@ extensions.

NM_STATE_CONNECTING

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.

+The graphical shell should indicate the network is being connected while +the applications should still make no attempts to connect the network.

@@ -987,8 +1007,8 @@ extensions.

NM_STATE_CONNECTED_LOCAL

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.

+but no default route to access the Internet. The graphical shell should +indicate no network connectivity.

@@ -996,9 +1016,9 @@ extensions.

NM_STATE_CONNECTED_SITE

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.

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

@@ -1006,8 +1026,8 @@ extensions.

NM_STATE_CONNECTED_GLOBAL

There is global IPv4 and/or IPv6 Internet connectivity - This means the Internet connectivity check succeeded, the graphical shell should - indicate full network connectivity.

+This means the Internet connectivity check succeeded, the graphical shell should +indicate full network connectivity.

@@ -1031,9 +1051,9 @@ extensions.

NM_CONNECTIVITY_UNKNOWN

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.

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

@@ -1041,9 +1061,9 @@ extensions.

NM_CONNECTIVITY_NONE

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.

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

@@ -1051,11 +1071,11 @@ extensions.

NM_CONNECTIVITY_PORTAL

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 - against the https connections) for the purpose of authenticating to a gateway - and retrigger the connectivity check with CheckConnectivity() when the - browser window is dismissed.

+portal gateway. The graphical shell may open a sandboxed web browser window +(because the captive portals typically attempt a man-in-the-middle attacks +against the https connections) for the purpose of authenticating to a gateway +and retrigger the connectivity check with CheckConnectivity() when the +browser window is dismissed.

@@ -1063,8 +1083,8 @@ extensions.

NM_CONNECTIVITY_LIMITED

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.

+to be able to reach the full Internet, but a captive portal has not been +detected.

@@ -1072,7 +1092,7 @@ extensions.

NM_CONNECTIVITY_FULL

The host is connected to a network, and - appears to be able to reach the full Internet.

+appears to be able to reach the full Internet.

@@ -1312,6 +1332,13 @@ GSM/UMTS, or LTE network access protocols

+ +

NM_DEVICE_TYPE_VRF

+ +

A VRF (Virtual Routing and Forwarding) interface (Since: 1.24)

+ + +

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.

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.

the device is an access point/hotspot. Not valid for - access point objects; used only for hotspot mode on the local machine.

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.

the device can be activated, but is currently - idle and not connected to a network.

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.

the device is connecting to the requested network. - This may include operations like associating with the Wi-Fi AP, dialing - the modem, connecting to the remote Bluetooth device, etc.

the device requires more information to continue - connecting to the requested network. This includes secrets like WiFi - passphrases, login passwords, PIN codes, etc.

the device is requesting IPv4 and/or IPv6 - addresses and routing information from the network.

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.

the device is waiting for a secondary - connection (like a VPN) which must activated before the device can be - activated

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.

the device failed to connect to the requested - network and is cleaning up the connection request

indicates that the per-connection - setting is unspecified. In this case, it will fallback to the default - value, which is NM_CONNECTION_MULTI_CONNECT_SINGLE.

the connection profile can only - be active once at each moment. Activating a profile that is already active, - will first deactivate it.

the profile can - be manually activated multiple times on different devices. However, - regarding autoconnect, the profile will autoconnect only if it is - currently not connected otherwise.

the profile can autoactivate - and be manually activated multiple times together.

The active connection - changed state because the device it was using was disconnected.

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.

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.

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.

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.

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.

upon rollback, - delete any new connection added after the checkpoint (Since: 1.6)

upon rollback, - disconnect any new device appeared after the checkpoint (Since: 1.6)

by default, creating - a checkpoint fails if there are already existing checkoints that - reference the same devices. With this flag, creation of such - checkpoints is allowed, however, if an older checkpoint - that references overlapping devices gets rolled back, it will - automatically destroy this checkpoint during rollback. This - allows to create several overlapping checkpoints in parallel, - and rollback to them at will. With the special case that - rolling back to an older checkpoint will invalidate all - overlapping younger checkpoints. This opts-in that the - checkpoint can be automatically destroyed by the rollback - of an older checkpoint. (Since: 1.12)

the connection is not saved to disk. - That either means, that the connection is in-memory only and currently - is not backed by a file. Or, that the connection is backed by a file, - but has modifications in-memory that were not persisted to disk.

A connection is "nm-generated" if - it was generated by NetworkManger. If the connection gets modified or saved - by the user, the flag gets cleared. A nm-generated is also unsaved - and has no backing file as it is in-memory only.

The connection will be deleted - when it disconnects. That is for in-memory connections (unsaved), which are - currently active but deleted on disconnect. Volatile connections are - always unsaved, but they are also no backing file on disk and are entirely - in-memory only.

The master has any slave devices attached. - This only makes sense if the device is a master.

the lifetime - of the activation is bound to the visilibity of the connection profile, - which in turn depends on "connection.permissions" and whether a session - for the user exists. Since: 1.16

usually, when the connection - has autoconnect enabled and gets added, it becomes eligible to autoconnect - right away. Setting this flag, disables autoconnect until the connection - is manually activated.

makes the profile in-memory. - Note that such profiles are stored in keyfile format under /run. - If the file is already in-memory, the file in /run is updated in-place. - Otherwise, the previous storage for the profile is left unchanged - on disk, and the in-memory copy shadows it. - Note that the original filename of the previous persistent storage (if any) - is remembered. That means, when later persisting the profile again to disk, - the file on disk will be overwritten again. - Likewise, when finally deleting the profile, both the storage from /run - and persistent storage are deleted (or if the persistent storage does not - allow deletion, and nmmeta file is written to mark the UUID as deleted).

this is almost the same - as NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, with one difference: when later deleting - the profile, the original profile will not be deleted. Instead a nmmeta - file is written to /run to indicate that the profile is gone. - Note that if such a nmmeta tombstone file exists and hides a file in persistant - storage, then when re-adding the profile with the same UUID, then the original - storage is taken over again.

this is like NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, - but if the connection has a corresponding file on persistent storage, the file - will be deleted right away. If the profile is later again persisted to disk, - a new, unused filename will be chosen.

This can be specified with either - NM_SETTINGS_UPDATE2_FLAG_IN_MEMORY, 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.

usually, when the connection - has autoconnect enabled and is modified, it becomes eligible to autoconnect - right away. Setting this flag, disables autoconnect until the connection - is manually activated.

when a profile gets modified that is - currently active, then these changes don't take effect for the active - device unless the profile gets reactivated or the configuration reapplied. - There are two exceptions: by default "connection.zone" and "connection.metered" - properties take effect immediately. Specify this flag to prevent these - properties to take effect, so that the change is restricted to modify - the profile. Since: 1.20.

an alias for numeric zero, no flags set. This - reloads everything that is supported and is identical to a SIGHUP.

reload the NetworkManager.conf configuration - from disk. Note that this does not include connections, which can be - reloaded via Setting's ReloadConnections().

update DNS configuration, which usually - involves writing /etc/resolv.conf anew.

means to restart the DNS plugin. This - is for example useful when using dnsmasq plugin, which uses additional - configuration in /etc/NetworkManager/dnsmasq.d. If you edit those files, - you can restart the DNS plugin. This action shortly interrupts name - resolution.

the interface is enabled from the - administrative point of view. Corresponds to kernel IFF_UP.

the interface has carrier. In most - cases this is equal to the value of NM_DEVICE_INTERFACE_FLAG_LOWER_UP +cases this is equal to the value of NM_DEVICE_INTERFACE_FLAG_LOWER_UP . - However some devices have a non-standard carrier detection mechanism.

enum NMClientPermission

NMClientPermission values indicate various permissions that NetworkManager +clients can obtain to perform certain tasks on behalf of the current user.

Members

+++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

NM_CLIENT_PERMISSION_NONE	+ unknown or no permission +
NM_CLIENT_PERMISSION_ENABLE_DISABLE_NETWORK	+ controls whether networking +can be globally enabled or disabled +
NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIFI	+ controls whether Wi-Fi can be +globally enabled or disabled +
NM_CLIENT_PERMISSION_ENABLE_DISABLE_WWAN	+ controls whether WWAN (3G) can be +globally enabled or disabled +
NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIMAX	+ controls whether WiMAX can be +globally enabled or disabled +
NM_CLIENT_PERMISSION_SLEEP_WAKE	+ controls whether the client can ask +NetworkManager to sleep and wake +
NM_CLIENT_PERMISSION_NETWORK_CONTROL	+ controls whether networking connections +can be started, stopped, and changed +
NM_CLIENT_PERMISSION_WIFI_SHARE_PROTECTED	+ controls whether a password +protected Wi-Fi hotspot can be created +
NM_CLIENT_PERMISSION_WIFI_SHARE_OPEN	+ controls whether an open Wi-Fi hotspot +can be created +
NM_CLIENT_PERMISSION_SETTINGS_MODIFY_SYSTEM	+ controls whether connections +that are available to all users can be modified +
NM_CLIENT_PERMISSION_SETTINGS_MODIFY_OWN	+ controls whether connections +owned by the current user can be modified +
NM_CLIENT_PERMISSION_SETTINGS_MODIFY_HOSTNAME	+ controls whether the +persistent hostname can be changed +
NM_CLIENT_PERMISSION_SETTINGS_MODIFY_GLOBAL_DNS	+ modify persistent global +DNS configuration +
NM_CLIENT_PERMISSION_RELOAD	+ controls access to Reload. +
NM_CLIENT_PERMISSION_CHECKPOINT_ROLLBACK	+ permission to create checkpoints. +
NM_CLIENT_PERMISSION_ENABLE_DISABLE_STATISTICS	+ controls whether device +statistics can be globally enabled or disabled +
NM_CLIENT_PERMISSION_ENABLE_DISABLE_CONNECTIVITY_CHECK	+ controls whether +connectivity check can be enabled or disabled +
NM_CLIENT_PERMISSION_WIFI_SCAN	+ controls whether wifi scans can be performed +
NM_CLIENT_PERMISSION_LAST	+ a reserved boundary value +

NM_CLIENT_PERMISSION_RESULT_UNKNOWN	+ unknown or no authorization +
NM_CLIENT_PERMISSION_RESULT_YES	+ the permission is available +
NM_CLIENT_PERMISSION_RESULT_AUTH	+ authorization is necessary before the +permission is available +
NM_CLIENT_PERMISSION_RESULT_NO	+ permission to perform the operation is +denied by system policy +

Types and Values

NM_DBUS_INTERFACE_DEVICE_VRF

NM_DBUS_INTERFACE_DEVICE_VXLAN

enum NMClientPermission

Members

enum NMClientPermissionResult

Members

#define	NM_DBUS_INTERFACE_DEVICE_VRF
#define	NM_DBUS_INTERFACE_DEVICE_VXLAN
enum	NMDeviceInterfaceFlags
enum	NMClientPermission
enum	NMClientPermissionResult