Flags

Details

class NM.ActivationStateFlags(value)

Bases: GObject.GFlags

Flags describing the current activation state.

New in version 1.10.

NONE = 0

an alias for numeric zero, no flags set.

IS_MASTER = 1

the device is a master.

EXTERNAL = 128

the active connection was generated to represent an external configuration of a networking device.

New in version 1.26.

IP6_READY = 16

IPv6 setting is completed.

IS_SLAVE = 2

the device is a slave.

MASTER_HAS_SLAVES = 32

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

LAYER2_READY = 4

layer2 is activated and ready.

LIFETIME_BOUND_TO_PROFILE_VISIBILITY = 64

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.

New in version 1.16.

IP4_READY = 8

IPv4 setting is completed.

class NM.BluetoothCapabilities(value)

Bases: GObject.GFlags

NM.BluetoothCapabilities values indicate the usable capabilities of a Bluetooth device.

NONE = 0

device has no usable capabilities

DUN = 1

device provides Dial-Up Networking capability

NAP = 2

device provides Network Access Point capability

class NM.CheckpointCreateFlags(value)

Bases: GObject.GFlags

The flags for CheckpointCreate call

New in version 1.4.

NONE = 0

no flags

DESTROY_ALL = 1

when creating a new checkpoint, destroy all existing ones.

DELETE_NEW_CONNECTIONS = 2

upon rollback, delete any new connection added after the checkpoint

New in version 1.6.

DISCONNECT_NEW_DEVICES = 4

upon rollback, disconnect any new device appeared after the checkpoint

New in version 1.6.

ALLOW_OVERLAPPING = 8

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.

New in version 1.12.

class NM.ClientInstanceFlags(value)

Bases: GObject.GFlags

New in version 1.24.

NONE = 0

special value to indicate no flags.

NO_AUTO_FETCH_PERMISSIONS = 1

by default, NM.Client will fetch the permissions via “GetPermissions” and refetch them when “CheckPermissions” signal gets received. By setting this flag, this behavior can be disabled. You can toggle this flag to enable and disable automatic fetching of the permissions. Watch also NM.Client.get_permissions_state() to know whether the permissions are up to date.

class NM.ConnectionSerializationFlags(value)

Bases: GObject.GFlags

These flags determine which properties are serialized when calling when calling NM.Connection.to_dbus().

ALL = 0

serialize all properties (including secrets)

NO_SECRETS = 1

do not include secrets

ONLY_SECRETS = 2

only serialize secrets

WITH_SECRETS_AGENT_OWNED = 4

if set, only secrets that are agent owned will be serialized.

New in version 1.20.

class NM.DeviceCapabilities(value)

Bases: GObject.GFlags

General device capability flags.

NONE = 0

device has no special capabilities

NM_SUPPORTED = 1

NetworkManager supports this device

CARRIER_DETECT = 2

this device can indicate carrier status

IS_SOFTWARE = 4

this device is a software device

SRIOV = 8

this device supports single-root I/O virtualization

class NM.DeviceInterfaceFlags(value)

Bases: GObject.GFlags

Flags for a network interface.

New in version 1.22.

UP = 1

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

LOWER_UP = 2

the physical link is up. Corresponds to kernel IFF_LOWER_UP.

CARRIER = 65536

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

class NM.DeviceModemCapabilities(value)

Bases: GObject.GFlags

NM.DeviceModemCapabilities 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.

NONE = 0

modem has no usable capabilities

POTS = 1

modem uses the analog wired telephone network and is not a wireless/cellular device

CDMA_EVDO = 2

modem supports at least one of CDMA 1xRTT, EVDO revision 0, EVDO revision A, or EVDO revision B

GSM_UMTS = 4

modem supports at least one of GSM, GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability

LTE = 8

modem has LTE data capability

class NM.DeviceWifiCapabilities(value)

Bases: GObject.GFlags

802.11 specific device encryption and authentication capabilities.

NONE = 0

device has no encryption/authentication capabilities

CIPHER_WEP40 = 1

device supports 40/64-bit WEP encryption

FREQ_5GHZ = 1024

device supports 5GHz frequencies

ADHOC = 128

device supports Ad-Hoc mode

WPA = 16

device supports WPA1 authentication

CIPHER_WEP104 = 2

device supports 104/128-bit WEP encryption

FREQ_VALID = 256

device reports frequency capabilities

RSN = 32

device supports WPA2/RSN authentication

CIPHER_TKIP = 4

device supports TKIP encryption

MESH = 4096

device supports acting as a mesh point.

New in version 1.20.

FREQ_2GHZ = 512

device supports 2.4GHz frequencies

AP = 64

device supports Access Point mode

CIPHER_CCMP = 8

device supports AES/CCMP encryption

IBSS_RSN = 8192

device supports WPA2/RSN in an IBSS network.

New in version 1.22.

class NM.DhcpHostnameFlags(value)

Bases: GObject.GFlags

NM.DhcpHostnameFlags describe flags related to the DHCP hostname and FQDN.

New in version 1.22.

NONE = 0

no flag set. The default value from Networkmanager global configuration is used. If such value is unset or still zero, the DHCP request will use standard FQDN flags, i.e. NM.DhcpHostnameFlags.FQDN_SERV_UPDATE and NM.DhcpHostnameFlags.FQDN_ENCODED for IPv4 and NM.DhcpHostnameFlags.FQDN_SERV_UPDATE for IPv6.

FQDN_SERV_UPDATE = 1

whether the server should do the A RR (FQDN-to-address) DNS updates.

FQDN_ENCODED = 2

if set, the FQDN is encoded using canonical wire format. Otherwise it uses the deprecated ASCII encoding. This flag is allowed only for DHCPv4.

FQDN_NO_UPDATE = 4

when not set, request the server to perform updates (the PTR RR and possibly the A RR based on the NM.DhcpHostnameFlags.FQDN_SERV_UPDATE flag). If this is set, the NM.DhcpHostnameFlags.FQDN_SERV_UPDATE flag should be cleared.

FQDN_CLEAR_FLAGS = 8

when set, no FQDN flags are sent in the DHCP FQDN option. When cleared and all other FQDN flags are zero, standard FQDN flags are sent. This flag is incompatible with any other FQDN flag.

class NM.IPAddressCmpFlags(value)

Bases: GObject.GFlags

Compare flags for NM.IPAddress.cmp_full().

New in version 1.22.

NONE = 0

no flags.

WITH_ATTRS = 1

when comparing two addresses, also consider their attributes. Warning: note that attributes are GVariants and they don’t have a total order. In other words, if the address differs only by their attributes, the returned compare order is not total. In that case, the return value merely indicates equality (zero) or inequality.

class NM.IPRoutingRuleAsStringFlags(value)

Bases: GObject.GFlags

New in version 1.18.

NONE = 0

no flags selected.

AF_INET = 1

whether to allow parsing IPv4 addresses.

AF_INET6 = 2

whether to allow parsing IPv6 addresses. If both NM.IPRoutingRuleAsStringFlags.AF_INET and NM.IPRoutingRuleAsStringFlags.AF_INET6 are unset, it’s the same as setting them both.

VALIDATE = 4

if set, ensure that the rule verfies or fail.

class NM.IPTunnelFlags(value)

Bases: GObject.GFlags

NONE = 0
IP6_IGN_ENCAP_LIMIT = 1
IP6_RCV_DSCP_COPY = 16
IP6_USE_ORIG_TCLASS = 2
IP6_USE_ORIG_FWMARK = 32
IP6_USE_ORIG_FLOWLABEL = 4
IP6_MIP6_DEV = 8
class NM.ManagerReloadFlags(value)

Bases: GObject.GFlags

Flags for the manager Reload() call.

New in version 1.22.

CONF = 1

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

DNS_RC = 2

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

DNS_FULL = 4

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.

class NM.SecretAgentCapabilities(value)

Bases: GObject.GFlags

NM.SecretAgentCapabilities indicate various capabilities of the agent.

NONE = 0

the agent supports no special capabilities

LAST = 1

bounds checking value; should not be used.

VPN_HINTS = 1

the agent supports passing hints to VPN plugin authentication dialogs.

class NM.SecretAgentGetSecretsFlags(value)

Bases: GObject.GFlags

NM.SecretAgentGetSecretsFlags values modify the behavior of a GetSecrets request.

ONLY_SYSTEM = -2147483648

Internal flag, not part of the D-Bus API.

NONE = 0

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.

ALLOW_INTERACTION = 1

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.

NO_ERRORS = 1073741824

Internal flag, not part of the D-Bus API.

REQUEST_NEW = 2

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.

USER_REQUESTED = 4

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.

WPS_PBC_ACTIVE = 8

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.

class NM.Setting8021xAuthFlags(value)

Bases: GObject.GFlags

NM.Setting8021xAuthFlags values indicate which authentication settings should be used.

Before 1.22, this was wrongly marked as a enum and not as a flags type.

New in version 1.8.

NONE = 0

No flags

TLS_1_0_DISABLE = 1

Disable TLSv1.0

TLS_1_1_DISABLE = 2

Disable TLSv1.1

TLS_1_2_DISABLE = 4

Disable TLSv1.2

ALL = 7

All supported flags

class NM.SettingDcbFlags(value)

Bases: GObject.GFlags

DCB feature flags.

NONE = 0

no flag

ENABLE = 1

the feature is enabled

ADVERTISE = 2

the feature is advertised

WILLING = 4

the feature is willing to change based on peer configuration advertisements

class NM.SettingSecretFlags(value)

Bases: GObject.GFlags

These flags indicate specific behavior related to handling of a secret. Each secret has a corresponding set of these flags which indicate how the secret is to be stored and/or requested when it is needed.

NONE = 0

the system is responsible for providing and storing this secret (default)

AGENT_OWNED = 1

a user secret agent is responsible for providing and storing this secret; when it is required agents will be asked to retrieve it

NOT_SAVED = 2

this secret should not be saved, but should be requested from the user each time it is needed

NOT_REQUIRED = 4

in situations where it cannot be automatically determined that the secret is required (some VPNs and PPP providers don’t require all secrets) this flag indicates that the specific secret is not required

class NM.SettingWiredWakeOnLan(value)

Bases: GObject.GFlags

Options for NM.SettingWired :wake-on-lan. Note that not all options are supported by all devices.

New in version 1.2.

DEFAULT = 1

Use the default value

BROADCAST = 16

Wake on broadcast messages

PHY = 2

Wake on PHY activity

ARP = 32

Wake on ARP

IGNORE = 32768

Don’t change configured settings

UNICAST = 4

Wake on unicast messages

MAGIC = 64

Wake on magic packet

MULTICAST = 8

Wake on multicast messages

class NM.SettingWirelessSecurityWpsMethod(value)

Bases: GObject.GFlags

Configure the use of WPS by a connection while it activates.

Note: prior to 1.16, this was a GEnum type instead of a GFlags type although, with the same numeric values.

New in version 1.10.

DEFAULT = 0

Attempt whichever method AP supports

DISABLED = 1

WPS can not be used.

AUTO = 2

Use WPS, any method

PBC = 4

use WPS push-buthon method

PIN = 8

use PIN method

class NM.SettingWirelessWakeOnWLan(value)

Bases: GObject.GFlags

Options for NM.SettingWireless :wake-on-wlan. Note that not all options are supported by all devices.

New in version 1.12.

DEFAULT = 1

Use the default value

RFKILL_RELEASE = 128

Wake on rfkill release

GTK_REKEY_FAILURE = 16

Wake on GTK rekey failure

ANY = 2

Wake on any activity

TCP = 256
EAP_IDENTITY_REQUEST = 32

Wake on EAP identity request

IGNORE = 32768

Don’t change configured settings

DISCONNECT = 4

Wake on disconnect

ALL = 510

Wake on all events. This does not include the exclusive flags NM.SettingWirelessWakeOnWLan.DEFAULT or NM.SettingWirelessWakeOnWLan.IGNORE.

4WAY_HANDSHAKE = 64
_4WAY_HANDSHAKE = 64

Wake on 4way handshake

MAGIC = 8

Wake on magic packet

class NM.SettingsAddConnection2Flags(value)

Bases: GObject.GFlags

Numeric flags for the “flags” argument of AddConnection2() D-Bus API.

New in version 1.20.

NONE = 0

an alias for numeric zero, no flags set.

TO_DISK = 1

to persist the connection to disk.

IN_MEMORY = 2

to make the connection in-memory only.

BLOCK_AUTOCONNECT = 32

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.

class NM.SettingsConnectionFlags(value)

Bases: GObject.GFlags

Flags describing the current activation state.

New in version 1.12.

NONE = 0

an alias for numeric zero, no flags set.

UNSAVED = 1

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.

NM_GENERATED = 2

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.

VOLATILE = 4

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.

EXTERNAL = 8

the profile was generated to represent an external configuration of a networking device.

New in version 1.26.

class NM.SettingsUpdate2Flags(value)

Bases: GObject.GFlags

New in version 1.12.

NONE = 0

an alias for numeric zero, no flags set.

TO_DISK = 1

to persist the connection to disk.

VOLATILE = 16

This can be specified with either NM.SettingsUpdate2Flags.IN_MEMORY, NM.SettingsUpdate2Flags.IN_MEMORY_DETACHED or NM.SettingsUpdate2Flags.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.

IN_MEMORY = 2

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

BLOCK_AUTOCONNECT = 32

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.

IN_MEMORY_DETACHED = 4

this is almost the same as NM.SettingsUpdate2Flags.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.

NO_REAPPLY = 64

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.

New in version 1.20.

IN_MEMORY_ONLY = 8

this is like NM.SettingsUpdate2Flags.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.

class NM.TeamLinkWatcherArpPingFlags(value)

Bases: GObject.GFlags

VALIDATE_ACTIVE = 2

the arp_ping link watcher option ‘validate_active’ is enabled (set to true).

VALIDATE_INACTIVE = 4

the arp_ping link watcher option ‘validate_inactive’ is enabled (set to true).

SEND_ALWAYS = 8

the arp_ping link watcher option ‘send_always’ is enabled (set to true).

class NM.VlanFlags(value)

Bases: GObject.GFlags

NM.VlanFlags values control the behavior of the VLAN interface.

REORDER_HEADERS = 1

indicates that this interface should reorder outgoing packet headers to look more like a non-VLAN Ethernet interface

GVRP = 2

indicates that this interface should use GVRP to register itself with its switch

LOOSE_BINDING = 4

indicates that this interface’s operating state is tied to the underlying network interface but other details (like routing) are not.

MVRP = 8

indicates that this interface should use MVRP to register itself with its switch

class NM.VpnEditorPluginCapability(value)

Bases: GObject.GFlags

Flags that indicate certain capabilities of the plugin to editor programs.

NONE = 0

unknown or no capability

IMPORT = 1

the plugin can import new connections

EXPORT = 2

the plugin can export connections

IPV6 = 4

the plugin supports IPv6 addressing