diff options
Diffstat (limited to 'docs/api/html/nm-settings.html')
| -rw-r--r-- | docs/api/html/nm-settings.html | 725 |
1 files changed, 467 insertions, 258 deletions
diff --git a/docs/api/html/nm-settings.html b/docs/api/html/nm-settings.html index 9501aa71..38c28d64 100644 --- a/docs/api/html/nm-settings.html +++ b/docs/api/html/nm-settings.html @@ -5,8 +5,8 @@ <title>nm-settings: NetworkManager Reference Manual</title> <meta name="generator" content="DocBook XSL Stylesheets V1.79.1"> <link rel="home" href="index.html" title="NetworkManager Reference Manual"> -<link rel="up" href="manpages.html" title="Manual Pages"> -<link rel="prev" href="NetworkManager.conf.html" title="NetworkManager.conf"> +<link rel="up" href="manpages.html" title="Part I. Manual Pages"> +<link rel="prev" href="nmtui.html" title="nmtui"> <link rel="next" href="nm-settings-keyfile.html" title="nm-settings-keyfile"> <meta name="generator" content="GTK-Doc V1.25 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> @@ -16,7 +16,7 @@ <td width="100%" align="left" class="shortcuts"></td> <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> <td><a accesskey="u" href="manpages.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> -<td><a accesskey="p" href="NetworkManager.conf.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> +<td><a accesskey="p" href="nmtui.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> <td><a accesskey="n" href="nm-settings-keyfile.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> </tr></table> <div class="refentry"> @@ -93,9 +93,171 @@ <tbody></tbody> </table> </div> -<div class="table"> -<a name="id-1.2.6.4.3"></a><p class="title"><b>Table 25. 802-1x setting</b></p> -<div class="table-contents"><table class="table" summary="802-1x setting" border="1"> +<div class="refsect2"> +<a name="id-1.2.7.4.3"></a><h3>connection setting</h3> +<p>General Connection Profile Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.autoconnect"></a>autoconnect</td> +<td align="left">boolean</td> +<td align="left">TRUE</td> +<td>Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.autoconnect-priority"></a>autoconnect-priority</td> +<td align="left">int32</td> +<td align="left">0</td> +<td>The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.autoconnect-retries"></a>autoconnect-retries</td> +<td align="left">int32</td> +<td align="left">-1</td> +<td>The number of times a connection should be tried when autoctivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden).</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.autoconnect-slaves"></a>autoconnect-slaves</td> +<td align="left">NMSettingConnectionAutoconnectSlaves (int32)</td> +<td align="left"> </td> +<td>Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.id"></a>id</td> +<td align="left">string</td> +<td align="left"> </td> +<td>A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.interface-name"></a>interface-name</td> +<td align="left">string</td> +<td align="left"> </td> +<td>The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.lldp"></a>lldp</td> +<td align="left">int32</td> +<td align="left">-1</td> +<td>Whether LLDP is enabled for the connection.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.master"></a>master</td> +<td align="left">string</td> +<td align="left"> </td> +<td>Interface name of the master device or UUID of the master connection.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.metered"></a>metered</td> +<td align="left">NMMetered (int32)</td> +<td align="left"> </td> +<td>Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.name"></a>name</td> +<td align="left">string</td> +<td align="left">connection</td> +<td>The setting's name, which uniquely identifies the setting within the connection. Each setting type has a name unique to that type, for example "ppp" or "wireless" or "wired".</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.permissions"></a>permissions</td> +<td align="left">array of string</td> +<td align="left">[]</td> +<td>An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection. Otherwise a user is allowed to access this connection if and only if they are in this list. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.read-only"></a>read-only</td> +<td align="left">boolean</td> +<td align="left">FALSE</td> +<td>FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.secondaries"></a>secondaries</td> +<td align="left">array of string</td> +<td align="left">[]</td> +<td>List of connection UUIDs that should be activated when the base connection itself is activated. Currently only VPN connections are supported.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.slave-type"></a>slave-type</td> +<td align="left">string</td> +<td align="left"> </td> +<td>Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.stable-id"></a>stable-id</td> +<td align="left">string</td> +<td align="left"> </td> +<td>Token to generate stable IDs for the connection. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. Note that also the interface name of the activating connection and a per-host secret key is included into the address generation so that the same stable-id on different hosts/devices yields different addresses. If the value is unset, an ID unique for the connection is used. Specifing a stable-id allows multiple connections to generate the same addresses. Another use is to generate IDs at runtime via dynamic substitutions. The '$' character is treated special to perform dynamic substitutions at runtime. Currently supported are "${CONNECTION}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-boot, or every time. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}/${BOOT}" to create a unique id for this connection that changes with every reboot. Note that two connections only use the same effective id if their stable-id is also identical before performing dynamic substitutions.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.timestamp"></a>timestamp</td> +<td align="left">uint64</td> +<td align="left">0</td> +<td>The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.type"></a>type</td> +<td align="left">string</td> +<td align="left"> </td> +<td>Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.uuid"></a>uuid</td> +<td align="left">string</td> +<td align="left"> </td> +<td>A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.connection.zone"></a>zone</td> +<td align="left">string</td> +<td align="left"> </td> +<td>The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.</td> +</tr> +</tbody> +</table></div> +</div> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.4"></a><h3>802-1x setting</h3> +<p>AIEEE 802.1x Authentication Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -125,6 +287,13 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.802-1x.auth-timeout"></a>auth-timeout</td> +<td align="left">int32</td> +<td align="left">0</td> +<td>A timeout for the authentication. Zero means the global default; if the global default is not set, the authentication timeout is 25 seconds.</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.802-1x.ca-cert"></a>ca-cert</td> <td align="left">byte array</td> <td align="left"> </td> @@ -132,6 +301,20 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.802-1x.ca-cert-password"></a>ca-cert-password</td> +<td align="left">string</td> +<td align="left"> </td> +<td>The password used to access the CA certificate stored in "ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.802-1x.ca-cert-password-flags"></a>ca-cert-password-flags</td> +<td align="left">NMSettingSecretFlags (uint32)</td> +<td align="left"> </td> +<td>Flags indicating how to handle the "ca-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.802-1x.ca-path"></a>ca-path</td> <td align="left">string</td> <td align="left"> </td> @@ -146,6 +329,20 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.802-1x.client-cert-password"></a>client-cert-password</td> +<td align="left">string</td> +<td align="left"> </td> +<td>The password used to access the client certificate stored in "client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.802-1x.client-cert-password-flags"></a>client-cert-password-flags</td> +<td align="left">NMSettingSecretFlags (uint32)</td> +<td align="left"> </td> +<td>Flags indicating how to handle the "client-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.802-1x.domain-suffix-match"></a>domain-suffix-match</td> <td align="left">string</td> <td align="left"> </td> @@ -209,6 +406,13 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.802-1x.phase1-auth-flags"></a>phase1-auth-flags</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>Specifies authentication flags to use in "phase 1" outer authentication using NMSetting8021xAuthFlags options. The invidual TLS versions can be explicitly disabled. If a certain TLS disable flag is not set, it is up to the supplicant to allow or forbid it. The TLS options map to tls_disable_tlsv1_x settings. See the wpa_supplicant documentation for more details.</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.802-1x.phase1-fast-provisioning"></a>phase1-fast-provisioning</td> <td align="left">string</td> <td align="left"> </td> @@ -258,6 +462,20 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.802-1x.phase2-ca-cert-password"></a>phase2-ca-cert-password</td> +<td align="left">string</td> +<td align="left"> </td> +<td>The password used to access the "phase2" CA certificate stored in "phase2-ca-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.802-1x.phase2-ca-cert-password-flags"></a>phase2-ca-cert-password-flags</td> +<td align="left">NMSettingSecretFlags (uint32)</td> +<td align="left"> </td> +<td>Flags indicating how to handle the "phase2-ca-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.802-1x.phase2-ca-path"></a>phase2-ca-path</td> <td align="left">string</td> <td align="left"> </td> @@ -272,6 +490,20 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.802-1x.phase2-client-cert-password"></a>phase2-client-cert-password</td> +<td align="left">string</td> +<td align="left"> </td> +<td>The password used to access the "phase2" client certificate stored in "phase2-client-cert" property. Only makes sense if the certificate is stored on a PKCS#11 token that requires a login.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.802-1x.phase2-client-cert-password-flags"></a>phase2-client-cert-password-flags</td> +<td align="left">NMSettingSecretFlags (uint32)</td> +<td align="left"> </td> +<td>Flags indicating how to handle the "phase2-client-cert-password" property. (see <a class="xref" href="nm-settings.html#secrets-flags" title="Secret flag types:">the section called “Secret flag types:”</a> for flag values)</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.802-1x.phase2-domain-suffix-match"></a>phase2-domain-suffix-match</td> <td align="left">string</td> <td align="left"> </td> @@ -282,7 +514,7 @@ <a name="nm-settings.property.802-1x.phase2-private-key"></a>phase2-private-key</td> <td align="left">byte array</td> <td align="left"> </td> -<td>Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</td> +<td>Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.</td> </tr> <tr> <td align="left"> @@ -324,7 +556,7 @@ <a name="nm-settings.property.802-1x.private-key"></a>private-key</td> <td align="left">byte array</td> <td align="left"> </td> -<td>Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</td> +<td>Contains the private key when the "eap" property is set to "tls". Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data and the "private-key-password" property must be set to password used to decrypt the PKCS#12 certificate and key. When using PKCS#12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate. WARNING: "private-key" is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.</td> </tr> <tr> <td align="left"> @@ -357,9 +589,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.4"></a><p class="title"><b>Table 26. adsl setting</b></p> -<div class="table-contents"><table class="table" summary="adsl setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.5"></a><h3>adsl setting</h3> +<p>ADSL Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -432,9 +666,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.5"></a><p class="title"><b>Table 27. bluetooth setting</b></p> -<div class="table-contents"><table class="table" summary="bluetooth setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.6"></a><h3>bluetooth setting</h3> +<p>Bluetooth Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -472,9 +708,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.6"></a><p class="title"><b>Table 28. bond setting</b></p> -<div class="table-contents"><table class="table" summary="bond setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.7"></a><h3>bond setting</h3> +<p>Bonding Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -512,9 +750,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.7"></a><p class="title"><b>Table 29. bridge setting</b></p> -<div class="table-contents"><table class="table" summary="bridge setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.8"></a><h3>bridge setting</h3> +<p>Bridging Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -601,9 +841,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.8"></a><p class="title"><b>Table 30. bridge-port setting</b></p> -<div class="table-contents"><table class="table" summary="bridge-port setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.9"></a><h3>bridge-port setting</h3> +<p>Bridge Port Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -648,9 +890,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.9"></a><p class="title"><b>Table 31. cdma setting</b></p> -<div class="table-contents"><table class="table" summary="cdma setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.10"></a><h3>cdma setting</h3> +<p>CDMA-based Mobile Broadband Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -666,6 +910,13 @@ <tbody> <tr> <td align="left"> +<a name="nm-settings.property.cdma.mtu"></a>mtu</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.cdma.name"></a>name</td> <td align="left">string</td> <td align="left">cdma</td> @@ -702,168 +953,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.10"></a><p class="title"><b>Table 32. connection setting</b></p> -<div class="table-contents"><table class="table" summary="connection setting" border="1"> -<colgroup> -<col> -<col> -<col> -<col> -</colgroup> -<thead><tr> -<th>Key Name</th> -<th>Value Type</th> -<th>Default Value</th> -<th>Value Description</th> -</tr></thead> -<tbody> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.autoconnect"></a>autoconnect</td> -<td align="left">boolean</td> -<td align="left">TRUE</td> -<td>Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.autoconnect-priority"></a>autoconnect-priority</td> -<td align="left">int32</td> -<td align="left">0</td> -<td>The autoconnect priority. If the connection is set to autoconnect, connections with higher priority will be preferred. Defaults to 0. The higher number means higher priority.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.autoconnect-retries"></a>autoconnect-retries</td> -<td align="left">int32</td> -<td align="left">-1</td> -<td>The number of times a connection should be tried when autoctivating before giving up. Zero means forever, -1 means the global default (4 times if not overridden).</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.autoconnect-slaves"></a>autoconnect-slaves</td> -<td align="left">NMSettingConnectionAutoconnectSlaves (int32)</td> -<td align="left"> </td> -<td>Whether or not slaves of this connection should be automatically brought up when NetworkManager activates this connection. This only has a real effect for master connections. The permitted values are: 0: leave slave connections untouched, 1: activate all the slave connections with this connection, -1: default. If -1 (default) is set, global connection.autoconnect-slaves is read to determine the real value. If it is default as well, this fallbacks to 0.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.gateway-ping-timeout"></a>gateway-ping-timeout</td> -<td align="left">uint32</td> -<td align="left">0</td> -<td>If greater than zero, delay success of IP addressing until either the timeout is reached, or an IP gateway replies to a ping.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.id"></a>id</td> -<td align="left">string</td> -<td align="left"> </td> -<td>A human readable unique identifier for the connection, like "Work Wi-Fi" or "T-Mobile 3G".</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.interface-name"></a>interface-name</td> -<td align="left">string</td> -<td align="left"> </td> -<td>The name of the network interface this connection is bound to. If not set, then the connection can be attached to any interface of the appropriate type (subject to restrictions imposed by other settings). For software devices this specifies the name of the created device. For connection types where interface names cannot easily be made persistent (e.g. mobile broadband or USB Ethernet), this property should not be used. Setting this property restricts the interfaces a connection can be used with, and if interface names change or are reordered the connection may be applied to the wrong interface.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.lldp"></a>lldp</td> -<td align="left">int32</td> -<td align="left">-1</td> -<td>Whether LLDP is enabled for the connection.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.master"></a>master</td> -<td align="left">string</td> -<td align="left"> </td> -<td>Interface name of the master device or UUID of the master connection.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.metered"></a>metered</td> -<td align="left">NMMetered (int32)</td> -<td align="left"> </td> -<td>Whether the connection is metered. When updating this property on a currently activated connection, the change takes effect immediately.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.name"></a>name</td> -<td align="left">string</td> -<td align="left">connection</td> -<td>The setting's name, which uniquely identifies the setting within the connection. Each setting type has a name unique to that type, for example "ppp" or "wireless" or "wired".</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.permissions"></a>permissions</td> -<td align="left">array of string</td> -<td align="left">[]</td> -<td>An array of strings defining what access a given user has to this connection. If this is NULL or empty, all users are allowed to access this connection. Otherwise a user is allowed to access this connection if and only if they are in this list. Each entry is of the form "[type]:[id]:[reserved]"; for example, "user:dcbw:blah". At this time only the "user" [type] is allowed. Any other values are ignored and reserved for future use. [id] is the username that this permission refers to, which may not contain the ":" character. Any [reserved] information present must be ignored and is reserved for future use. All of [type], [id], and [reserved] must be valid UTF-8.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.read-only"></a>read-only</td> -<td align="left">boolean</td> -<td align="left">FALSE</td> -<td>FALSE if the connection can be modified using the provided settings service's D-Bus interface with the right privileges, or TRUE if the connection is read-only and cannot be modified.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.secondaries"></a>secondaries</td> -<td align="left">array of string</td> -<td align="left">[]</td> -<td>List of connection UUIDs that should be activated when the base connection itself is activated. Currently only VPN connections are supported.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.slave-type"></a>slave-type</td> -<td align="left">string</td> -<td align="left"> </td> -<td>Setting name of the device type of this slave's master connection (eg, "bond"), or NULL if this connection is not a slave.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.stable-id"></a>stable-id</td> -<td align="left">string</td> -<td align="left"> </td> -<td>Token to generate stable IDs for the connection. The stable-id is used for generating IPv6 stable private addresses with ipv6.addr-gen-mode=stable-privacy. It is also used to seed the generated cloned MAC address for ethernet.cloned-mac-address=stable and wifi.cloned-mac-address=stable. Note that also the interface name of the activating connection and a per-host secret key is included into the address generation so that the same stable-id on different hosts/devices yields different addresses. If the value is unset, an ID unique for the connection is used. Specifing a stable-id allows multiple connections to generate the same addresses. Another use is to generate IDs at runtime via dynamic substitutions. The '$' character is treated special to perform dynamic substitutions at runtime. Currently supported are "${CONNECTION}", "${BOOT}", "${RANDOM}". These effectively create unique IDs per-connection, per-boot, or every time. Any unrecognized patterns following '$' are treated verbatim, however are reserved for future use. You are thus advised to avoid '$' or escape it as "$$". For example, set it to "${CONNECTION}/${BOOT}" to create a unique id for this connection that changes with every reboot. Note that two connections only use the same effective id if their stable-id is also identical before performing dynamic substitutions.</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.timestamp"></a>timestamp</td> -<td align="left">uint64</td> -<td align="left">0</td> -<td>The time, in seconds since the Unix Epoch, that the connection was last _successfully_ fully activated. NetworkManager updates the connection timestamp periodically when the connection is active to ensure that an active connection has the latest timestamp. The property is only meant for reading (changes to this property will not be preserved).</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.type"></a>type</td> -<td align="left">string</td> -<td align="left"> </td> -<td>Base type of the connection. For hardware-dependent connections, should contain the setting name of the hardware-type specific setting (ie, "802-3-ethernet" or "802-11-wireless" or "bluetooth", etc), and for non-hardware dependent connections like VPN or otherwise, should contain the setting name of that setting type (ie, "vpn" or "bridge", etc).</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.uuid"></a>uuid</td> -<td align="left">string</td> -<td align="left"> </td> -<td>A universally unique identifier for the connection, for example generated with libuuid. It should be assigned when the connection is created, and never changed as long as the connection still applies to the same network. For example, it should not be changed when the "id" property or NMSettingIP4Config changes, but might need to be re-created when the Wi-Fi SSID, mobile broadband network provider, or "type" property changes. The UUID must be in the format "2815492f-7e56-435e-b2e9-246bd7cdc664" (ie, contains only hexadecimal characters and "-").</td> -</tr> -<tr> -<td align="left"> -<a name="nm-settings.property.connection.zone"></a>zone</td> -<td align="left">string</td> -<td align="left"> </td> -<td>The trust level of a the connection. Free form case-insensitive string (for example "Home", "Work", "Public"). NULL or unspecified zone means the connection will be placed in the default zone as defined by the firewall. When updating this property on a currently activated connection, the change takes effect immediately.</td> -</tr> -</tbody> -</table></div> -</div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.11"></a><p class="title"><b>Table 33. dcb setting</b></p> -<div class="table-contents"><table class="table" summary="dcb setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.11"></a><h3>dcb setting</h3> +<p>Data Center Bridging Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -992,9 +1086,37 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.12"></a><p class="title"><b>Table 34. generic setting</b></p> -<div class="table-contents"><table class="table" summary="generic setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.12"></a><h3>dummy setting</h3> +<p>Dummy Link Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody><tr> +<td align="left"> +<a name="nm-settings.property.dummy.name"></a>name</td> +<td align="left">string</td> +<td align="left">dummy</td> +<td>The setting's name, which uniquely identifies the setting within the connection. Each setting type has a name unique to that type, for example "ppp" or "wireless" or "wired".</td> +</tr></tbody> +</table></div> +</div> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.13"></a><h3>generic setting</h3> +<p>Generic Link Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1016,9 +1138,11 @@ </tr></tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.13"></a><p class="title"><b>Table 35. gsm setting</b></p> -<div class="table-contents"><table class="table" summary="gsm setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.14"></a><h3>gsm setting</h3> +<p>GSM-based Mobile Broadband Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1055,6 +1179,13 @@ </tr> <tr> <td align="left"> +<a name="nm-settings.property.gsm.mtu"></a>mtu</td> +<td align="left">uint32</td> +<td align="left">0</td> +<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple frames.</td> +</tr> +<tr> +<td align="left"> <a name="nm-settings.property.gsm.name"></a>name</td> <td align="left">string</td> <td align="left">gsm</td> @@ -1126,9 +1257,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.14"></a><p class="title"><b>Table 36. infiniband setting</b></p> -<div class="table-contents"><table class="table" summary="infiniband setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.15"></a><h3>infiniband setting</h3> +<p>Infiniband Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1187,9 +1320,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.15"></a><p class="title"><b>Table 37. ipv4 setting</b></p> -<div class="table-contents"><table class="table" summary="ipv4 setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.16"></a><h3>ipv4 setting</h3> +<p>IPv4 Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1360,9 +1495,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.16"></a><p class="title"><b>Table 38. ipv6 setting</b></p> -<div class="table-contents"><table class="table" summary="ipv6 setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.17"></a><h3>ipv6 setting</h3> +<p>IPv6 Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1540,9 +1677,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.17"></a><p class="title"><b>Table 39. ip-tunnel setting</b></p> -<div class="table-contents"><table class="table" summary="ip-tunnel setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.18"></a><h3>ip-tunnel setting</h3> +<p>IP Tunneling Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1650,9 +1789,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.18"></a><p class="title"><b>Table 40. macsec setting</b></p> -<div class="table-contents"><table class="table" summary="macsec setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.19"></a><h3>macsec setting</h3> +<p>MACSec Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1732,9 +1873,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.19"></a><p class="title"><b>Table 41. macvlan setting</b></p> -<div class="table-contents"><table class="table" summary="macvlan setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.20"></a><h3>macvlan setting</h3> +<p>MAC VLAN Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1786,9 +1929,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.20"></a><p class="title"><b>Table 42. 802-11-olpc-mesh setting</b></p> -<div class="table-contents"><table class="table" summary="802-11-olpc-mesh setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.21"></a><h3>802-11-olpc-mesh setting</h3> +<p>OLPC Wireless Mesh Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1833,9 +1978,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.21"></a><p class="title"><b>Table 43. ppp setting</b></p> -<div class="table-contents"><table class="table" summary="ppp setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.22"></a><h3>ppp setting</h3> +<p>Point-to-Point Protocol Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -1985,9 +2132,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.22"></a><p class="title"><b>Table 44. pppoe setting</b></p> -<div class="table-contents"><table class="table" summary="pppoe setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.23"></a><h3>pppoe setting</h3> +<p>PPP-over-Ethernet Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2039,9 +2188,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.23"></a><p class="title"><b>Table 45. proxy setting</b></p> -<div class="table-contents"><table class="table" summary="proxy setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.24"></a><h3>proxy setting</h3> +<p>WWW Proxy Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2093,9 +2244,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.24"></a><p class="title"><b>Table 46. serial setting</b></p> -<div class="table-contents"><table class="table" summary="serial setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.25"></a><h3>serial setting</h3> +<p>Serial Link Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2154,9 +2307,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.25"></a><p class="title"><b>Table 47. team setting</b></p> -<div class="table-contents"><table class="table" summary="team setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.26"></a><h3>team setting</h3> +<p>Teaming Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2194,9 +2349,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.26"></a><p class="title"><b>Table 48. team-port setting</b></p> -<div class="table-contents"><table class="table" summary="team-port setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.27"></a><h3>team-port setting</h3> +<p>Team Port Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2227,9 +2384,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.27"></a><p class="title"><b>Table 49. tun setting</b></p> -<div class="table-contents"><table class="table" summary="tun setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.28"></a><h3>tun setting</h3> +<p>Tunnel Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2295,9 +2454,46 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.28"></a><p class="title"><b>Table 50. vlan setting</b></p> -<div class="table-contents"><table class="table" summary="vlan setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.29"></a><h3>user setting</h3> +<p>General User Profile Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> +<colgroup> +<col> +<col> +<col> +<col> +</colgroup> +<thead><tr> +<th>Key Name</th> +<th>Value Type</th> +<th>Default Value</th> +<th>Value Description</th> +</tr></thead> +<tbody> +<tr> +<td align="left"> +<a name="nm-settings.property.user.data"></a>data</td> +<td align="left">dict of string to string</td> +<td align="left">{}</td> +<td>A dictionary of key/value pairs with user data. This data is ignored by NetworkManager and can be used at the users discretion. The keys only support a strict ascii format, but the values can be arbitrary UTF8 strings up to a certain length.</td> +</tr> +<tr> +<td align="left"> +<a name="nm-settings.property.user.name"></a>name</td> +<td align="left">string</td> +<td align="left">user</td> +<td>The setting's name, which uniquely identifies the setting within the connection. Each setting type has a name unique to that type, for example "ppp" or "wireless" or "wired".</td> +</tr> +</tbody> +</table></div> +</div> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.30"></a><h3>vlan setting</h3> +<p>VLAN Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2363,9 +2559,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.29"></a><p class="title"><b>Table 51. vpn setting</b></p> -<div class="table-contents"><table class="table" summary="vpn setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.31"></a><h3>vpn setting</h3> +<p>VPN Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2431,9 +2629,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.30"></a><p class="title"><b>Table 52. vxlan setting</b></p> -<div class="table-contents"><table class="table" summary="vxlan setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.32"></a><h3>vxlan setting</h3> +<p>VXLAN Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2569,9 +2769,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.31"></a><p class="title"><b>Table 53. wimax setting</b></p> -<div class="table-contents"><table class="table" summary="wimax setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.33"></a><h3>wimax setting</h3> +<p>WiMax Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2609,9 +2811,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.32"></a><p class="title"><b>Table 54. 802-3-ethernet setting</b></p> -<div class="table-contents"><table class="table" summary="802-3-ethernet setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.34"></a><h3>802-3-ethernet setting</h3> +<p>Wired Ethernet Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2740,9 +2944,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.33"></a><p class="title"><b>Table 55. 802-11-wireless setting</b></p> -<div class="table-contents"><table class="table" summary="802-11-wireless setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.35"></a><h3>802-11-wireless setting</h3> +<p>Wi-Fi Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -2892,9 +3098,11 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="table"> -<a name="id-1.2.6.4.34"></a><p class="title"><b>Table 56. 802-11-wireless-security setting</b></p> -<div class="table-contents"><table class="table" summary="802-11-wireless-security setting" border="1"> +<hr> +<div class="refsect2"> +<a name="id-1.2.7.4.36"></a><h3>802-11-wireless-security setting</h3> +<p>Wi-Fi Security Settings.</p> +<div class="informaltable"><table class="informaltable" border="1"> <colgroup> <col> <col> @@ -3037,7 +3245,8 @@ </tbody> </table></div> </div> -<br class="table-break"><div class="refsect2"> +<hr> +<div class="refsect2"> <a name="secrets-flags"></a><h3>Secret flag types:</h3> <p> Each secret property in a setting has an associated <span class="emphasis"><em>flags</em></span> property |