New upstream version 1.22.0 upstream/1.22.0

author: Michael Biebl <biebl@debian.org> 2019-12-18 18:29:24 +0100
committer: Michael Biebl <biebl@debian.org> 2019-12-18 18:29:24 +0100
commit: 28028b26b3371756811e95d894f709f4b1207c00 (patch)
tree: 6fe7316fd743b51042db47601a8ef8814b3134ac /docs/api/html/nm-settings.html
parent: e22609983008e1a669196ad64ba3a59ae8c76e0d (diff)
1 files changed, 40 insertions, 5 deletions
diff --git a/docs/api/html/nm-settings.html b/docs/api/html/nm-settings.html
index d07169a4..0dfdd5dc 100644
--- a/docs/api/html/nm-settings.html
+++ b/docs/api/html/nm-settings.html
@@ -8,7 +8,7 @@
 <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.29.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.29 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -498,14 +498,14 @@
 <a name="nm-settings.property.802-1x.phase2-auth"></a>phase2-auth</td>
 <td align="left">string</td>
 <td align="left"> </td>
-<td>Specifies the allowed "phase 2" inner non-EAP authentication methods when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  Recognized non-EAP "phase 2" methods are "pap", "chap", "mschap", "mschapv2", "gtc", "otp", "md5", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
+<td>Specifies the allowed "phase 2" inner non-EAP authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  Recognized non-EAP "phase 2" methods are "pap", "chap", "mschap", "mschapv2", "gtc", "otp", "md5", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
 </tr>
 <tr>
 <td align="left">
 <a name="nm-settings.property.802-1x.phase2-autheap"></a>phase2-autheap</td>
 <td align="left">string</td>
 <td align="left"> </td>
-<td>Specifies the allowed "phase 2" inner EAP-based authentication methods when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
+<td>Specifies the allowed "phase 2" inner EAP-based authentication method when an EAP method that uses an inner TLS tunnel is specified in the "eap" property.  Recognized EAP-based "phase 2" methods are "md5", "mschapv2", "otp", "gtc", and "tls". Each "phase 2" inner method requires specific parameters for successful authentication; see the wpa_supplicant documentation for more details.</td>
 </tr>
 <tr>
 <td align="left">
@@ -1213,6 +1213,13 @@
 </tr>
 <tr>
 <td align="left">
+<a name="nm-settings.property.gsm.auto-config"></a>auto-config</td>
+<td align="left">boolean</td>
+<td align="left">FALSE</td>
+<td>When TRUE, the settings such as APN, username, or password will default to values that match the network the modem will register to in the Mobile Broadband Provider database.</td>
+</tr>
+<tr>
+<td align="left">
 <a name="nm-settings.property.gsm.device-id"></a>device-id</td>
 <td align="left">string</td>
 <td align="left"> </td>
@@ -1416,6 +1423,20 @@
 </tr>
 <tr>
 <td align="left">
+<a name="nm-settings.property.ipv4.dhcp-hostname-flags"></a>dhcp-hostname-flags</td>
+<td align="left">uint32</td>
+<td align="left">0</td>
+<td>Flags for the DHCP hostname and FQDN. Currently this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td>
+</tr>
+<tr>
+<td align="left">
+<a name="nm-settings.property.ipv4.dhcp-iaid"></a>dhcp-iaid</td>
+<td align="left">string</td>
+<td align="left"> </td>
+<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td>
+</tr>
+<tr>
+<td align="left">
 <a name="nm-settings.property.ipv4.dhcp-send-hostname"></a>dhcp-send-hostname</td>
 <td align="left">boolean</td>
 <td align="left">TRUE</td>
@@ -1591,6 +1612,20 @@
 </tr>
 <tr>
 <td align="left">
+<a name="nm-settings.property.ipv6.dhcp-hostname-flags"></a>dhcp-hostname-flags</td>
+<td align="left">uint32</td>
+<td align="left">0</td>
+<td>Flags for the DHCP hostname and FQDN. Currently this property only includes flags to control the FQDN flags set in the DHCP FQDN option. Supported FQDN flags are NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) and NM_DHCP_HOSTNAME_FLAG_FQDN_NO_UPDATE (0x4).  When no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is set, the DHCP FQDN option will contain no flag. Otherwise, if no FQDN flag is set and NM_DHCP_HOSTNAME_FLAG_FQDN_CLEAR_FLAGS (0x8) is not set, the standard FQDN flags are set in the request: NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1), NM_DHCP_HOSTNAME_FLAG_FQDN_ENCODED (0x2) for IPv4 and NM_DHCP_HOSTNAME_FLAG_FQDN_SERV_UPDATE (0x1) for IPv6. When this property is set to the default value NM_DHCP_HOSTNAME_FLAG_NONE (0x0), a global default is looked up in NetworkManager configuration. If that value is unset or also NM_DHCP_HOSTNAME_FLAG_NONE (0x0), then the standard FQDN flags described above are sent in the DHCP requests.</td>
+</tr>
+<tr>
+<td align="left">
+<a name="nm-settings.property.ipv6.dhcp-iaid"></a>dhcp-iaid</td>
+<td align="left">string</td>
+<td align="left"> </td>
+<td>A string containing the "Identity Association Identifier" (IAID) used by the DHCP client. The property is a 32-bit decimal value or a special value among "mac", "perm-mac", "ifname" and "stable". When set to "mac" (or "perm-mac"), the last 4 bytes of the current (or permanent) MAC address are used as IAID. When set to "ifname", the IAID is computed by hashing the interface name. The special value "stable" can be used to generate an IAID based on the stable-id (see connection.stable-id), a per-host key and the interface name. When the property is unset, the value from global configuration is used; if no global default is set then the IAID is assumed to be "ifname". Note that at the moment this property is ignored for IPv6 by dhclient, which always derives the IAID from the MAC address.</td>
+</tr>
+<tr>
+<td align="left">
 <a name="nm-settings.property.ipv6.dhcp-send-hostname"></a>dhcp-send-hostname</td>
 <td align="left">boolean</td>
 <td align="left">TRUE</td>
@@ -3656,7 +3691,7 @@
 <a name="nm-settings.property.802-11-wireless-security.key-mgmt"></a>key-mgmt</td>
 <td align="left">string</td>
 <td align="left"> </td>
-<td>Key management used for the connection.  One of "none" (WEP), "ieee8021x" (Dynamic WEP), "wpa-none" (Ad-Hoc WPA-PSK), "wpa-psk" (infrastructure WPA-PSK), "sae" (SAE) or "wpa-eap" (WPA-Enterprise). This property must be set for any Wi-Fi connection that uses security.</td>
+<td>Key management used for the connection.  One of "none" (WEP), "ieee8021x" (Dynamic WEP), "wpa-psk" (infrastructure WPA-PSK), "sae" (SAE) or "wpa-eap" (WPA-Enterprise).  This property must be set for any Wi-Fi connection that uses security.</td>
 </tr>
 <tr>
 <td align="left">
@@ -3867,6 +3902,6 @@
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.29.1</div>
+<hr>Generated by GTK-Doc V1.29</div>
 </body>
 </html>
\ No newline at end of file
author	Michael Biebl <biebl@debian.org>	2019-12-18 18:29:24 +0100
committer	Michael Biebl <biebl@debian.org>	2019-12-18 18:29:24 +0100
commit	28028b26b3371756811e95d894f709f4b1207c00 (patch)
tree	6fe7316fd743b51042db47601a8ef8814b3134ac /docs/api/html/nm-settings.html
parent	e22609983008e1a669196ad64ba3a59ae8c76e0d (diff)