[gnomeweb-wml] nm: update settings spec to 0.8.4
- From: Dan Williams <dcbw src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnomeweb-wml] nm: update settings spec to 0.8.4
- Date: Thu, 21 Apr 2011 19:38:53 +0000 (UTC)
commit 328bbc63fb867c793aedc91f5d7a837cee2191be
Author: Dan Williams <dcbw redhat com>
Date: Thu Apr 21 12:24:13 2011 -0500
nm: update settings spec to 0.8.4
.../developers/settings-spec-08.html | 130 +++++++++++++------
1 files changed, 89 insertions(+), 41 deletions(-)
---
diff --git a/projects.gnome.org/NetworkManager/developers/settings-spec-08.html b/projects.gnome.org/NetworkManager/developers/settings-spec-08.html
index 4cdd100..eba3b1e 100644
--- a/projects.gnome.org/NetworkManager/developers/settings-spec-08.html
+++ b/projects.gnome.org/NetworkManager/developers/settings-spec-08.html
@@ -1,6 +1,6 @@
<html>
<head>
-<title>NetworkManager 0.8 Settings Specification</title></head>
+<title>NetworkManager 0.8.4.0 Settings Specification</title></head>
<body>
<p><h2>Setting name: '802-1x'</h2></p>
<table cellspacing=10 border=0 cellpadding=2>
@@ -17,7 +17,7 @@
<tr align=left valign=top>
<td><strong>eap</strong></td>
<td>array of string</td>
-<td></td>
+<td>[]</td>
<td>The allowed EAP method to be used when authenticating to the network with 802.1x. Valid methods are: 'leap', 'md5', 'tls', 'peap', 'ttls', and 'fast'. Each method requires different configuration using the properties of this setting; refer to wpa_supplicant documentation for the allowed combinations.</td>
</tr>
<tr align=left valign=top>
@@ -35,7 +35,7 @@
<tr align=left valign=top>
<td><strong>ca-cert</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>Contains the CA certificate if used by the EAP method specified in the 'eap' property. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td>
</tr>
<tr align=left valign=top>
@@ -47,7 +47,7 @@
<tr align=left valign=top>
<td><strong>client-cert</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>Contains the client certificate if used by the EAP method specified in the 'eap' property. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte.</td>
</tr>
<tr align=left valign=top>
@@ -83,7 +83,7 @@
<tr align=left valign=top>
<td><strong>phase2-ca-cert</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>Contains the 'phase 2' CA certificate if used by the EAP method specified in the 'phase2-auth' or 'phase2-autheap' properties. Certificate data is specified using a 'scheme'; two are currentlysupported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td>
</tr>
<tr align=left valign=top>
@@ -95,7 +95,7 @@
<tr align=left valign=top>
<td><strong>phase2-client-cert</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>Contains the 'phase 2' client certificate if used by the EAP method specified in the 'phase2-eap' or 'phase2-autheap' properties. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte.</td>
</tr>
<tr align=left valign=top>
@@ -107,7 +107,7 @@
<tr align=left valign=top>
<td><strong>private-key</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</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 X.509 private keys, this property should be set to the keys's decrypted DER encoded data. When using X.509 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 and ending with a terminating NULL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data (which is encrypted) 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 NULL 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.</td>
</tr>
<tr align=left valign=top>
@@ -119,7 +119,7 @@
<tr align=left valign=top>
<td><strong>phase2-private-key</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>Contains the 'phase 2' inner private key when the 'phase2-eap' 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 X.509 private keys, this property should be set to the keys's decrypted DER encoded data. When using X.509 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 and ending with a terminating NULL byte. When using PKCS#12 format private keys and the blob scheme, this property should be set to the PKCS#12 data (which is encrypted) 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 NULL byte, and as with the blob sche
me the 'private-key-password' property must be set to the password used to decode the PKCS#12 private key and certificate.</td>
</tr>
<tr align=left valign=top>
@@ -150,14 +150,14 @@
<tr align=left valign=top>
<td><strong>bdaddr</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>The Bluetooth address of the device</td>
</tr>
<tr align=left valign=top>
<td><strong>type</strong></td>
<td>string</td>
<td></td>
-<td>Either 'dun' for Dial-Up Networking connections (not yet supported) or 'panu' for Personal Area Networking connections.</td>
+<td>Either 'dun' for Dial-Up Networking connections or 'panu' for Personal Area Networking connections.</td>
</tr>
</table><br/>
<p><h2>Setting name: 'cdma'</h2></p>
@@ -274,7 +274,7 @@
<td><strong>apn</strong></td>
<td>string</td>
<td></td>
-<td>The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan.</td>
+<td>The GPRS Access Point Name specifying the APN used when establishing a data session with the GSM-based network. The APN often determines how the user will be billed for their network usage and whether the user has access to the Internet or just a provider-specific walled-garden, so it is important to use the correct APN for the user's mobile broadband plan. The APN may only be composed of the characters a-z, 0-9, ., and - per GSM 03.60 Section 14.9.</td>
</tr>
<tr align=left valign=top>
<td><strong>network-id</strong></td>
@@ -312,6 +312,12 @@
<td>1</td>
<td>Bitfield of allowed frequency bands. Note that not all devices allow frequency band control.</td>
</tr>
+<tr align=left valign=top>
+<td><strong>home-only</strong></td>
+<td>boolean</td>
+<td>FALSE</td>
+<td>When TRUE, only connections to the home network will be allowed. Connections to roaming networks will not be made.</td>
+</tr>
</table><br/>
<p><h2>Setting name: 'ipv4'</h2></p>
<table cellspacing=10 border=0 cellpadding=2>
@@ -329,31 +335,31 @@
<td><strong>method</strong></td>
<td>string</td>
<td></td>
-<td>IPv4 configuration method. If 'auto' is specified then the appropriate automatic method (DHCP, PPP, etc) is used for the interface and most other properties can be left unset. If 'link-local' is specified, then a link-local address in the 169.254/16 range will be assigned to the interface. If 'manual' is specified, static IP addressing is used and at least one IP address must be given in the 'addresses' property. If 'shared' is specified (indicating that this connection will provide network access to other computers) then the interface is assigned an address in the 10.42.x.1/24 range and a DHCP and forwarding DNS server are started, and the interface is NAT-ed to the current default network connection. This property must be set.</td>
+<td>IPv4 configuration method. If 'auto' is specified then the appropriate automatic method (DHCP, PPP, etc) is used for the interface and most other properties can be left unset. If 'link-local' is specified, then a link-local address in the 169.254/16 range will be assigned to the interface. If 'manual' is specified, static IP addressing is used and at least one IP address must be given in the 'addresses' property. If 'shared' is specified (indicating that this connection will provide network access to other computers) then the interface is assigned an address in the 10.42.x.1/24 range and a DHCP and forwarding DNS server are started, and the interface is NAT-ed to the current default network connection. 'disabled' means IPv4 will not be used on this connection. This property must be set.</td>
</tr>
<tr align=left valign=top>
<td><strong>dns</strong></td>
<td>array of uint32</td>
-<td></td>
-<td>List of DNS servers (network byte order). For the 'auto' method, these DNS servers are appended to those (if any) returned by automatic configuration. DNS servers cannot be used with the 'shared' or 'link-local' methods as there is no usptream network. In all other methods, these DNS servers are used as the only DNS servers for this connection.</td>
+<td>[]</td>
+<td>List of DNS servers (network byte order). For the 'auto' method, these DNS servers are appended to those (if any) returned by automatic configuration. DNS servers cannot be used with the 'shared', 'link-local', or 'disabled' methods as there is no usptream network. In all other methods, these DNS servers are used as the only DNS servers for this connection.</td>
</tr>
<tr align=left valign=top>
<td><strong>dns-search</strong></td>
<td>array of string</td>
-<td></td>
-<td>List of DNS search domains. For the 'auto' method, these search domains are appended to those returned by automatic configuration. Search domains cannot be used with the 'shared' or 'link-local' methods as there is no upstream network. In all other methods, these search domains are used as the only search domains for this connection.</td>
+<td>[]</td>
+<td>List of DNS search domains. For the 'auto' method, these search domains are appended to those returned by automatic configuration. Search domains cannot be used with the 'shared', 'link-local', or 'disabled' methods as there is no upstream network. In all other methods, these search domains are used as the only search domains for this connection.</td>
</tr>
<tr align=left valign=top>
<td><strong>addresses</strong></td>
<td>array of array of uint32</td>
-<td></td>
-<td>Array of IPv4 address structures. Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet. For the 'auto' method, given IP addresses are appended to those returned by automatic configuration. Addresses cannot be used with the 'shared' or 'link-local' methods as the interface is automatically assigned an address with these methods.</td>
+<td>[]</td>
+<td>Array of IPv4 address structures. Each IPv4 address structure is composed of 3 32-bit values; the first being the IPv4 address (network byte order), the second the prefix (1 - 32), and last the IPv4 gateway (network byte order). The gateway may be left as 0 if no gateway exists for that subnet. For the 'auto' method, given IP addresses are appended to those returned by automatic configuration. Addresses cannot be used with the 'shared', 'link-local', or 'disabled' methods as addressing is either automatic or disabled with these methods.</td>
</tr>
<tr align=left valign=top>
<td><strong>routes</strong></td>
<td>array of array of uint32</td>
-<td></td>
-<td>Array of IPv4 route structures. Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. For the 'auto' method, given IP routes are appended to those returned by automatic configuration. Routes cannot be used with the 'shared' or 'link-local' methods as there is no upstream network.</td>
+<td>[]</td>
+<td>Array of IPv4 route structures. Each IPv4 route structure is composed of 4 32-bit values; the first being the destination IPv4 network or address (network byte order), the second the destination network or address prefix (1 - 32), the third being the next-hop (network byte order) if any, and the fourth being the route metric. For the 'auto' method, given IP routes are appended to those returned by automatic configuration. Routes cannot be used with the 'shared', 'link-local', or 'disabled', methods as there is no upstream network.</td>
</tr>
<tr align=left valign=top>
<td><strong>ignore-auto-routes</strong></td>
@@ -376,7 +382,7 @@
<tr align=left valign=top>
<td><strong>dhcp-send-hostname</strong></td>
<td>boolean</td>
-<td>FALSE</td>
+<td>TRUE</td>
<td>If TRUE, a hostname is sent to the DHCP server when acquiring a lease. Some DHCP servers use this hostname to update DNS databases, essentially providing a static hostname for the computer. If the 'dhcp-hostname' property is empty and this property is TRUE, the current persistent hostname of the computer is sent.</td>
</tr>
<tr align=left valign=top>
@@ -391,6 +397,12 @@
<td>FALSE</td>
<td>If TRUE, this connection will never be the default IPv4 connection, meaning it will never be assigned the default route by NetworkManager.</td>
</tr>
+<tr align=left valign=top>
+<td><strong>may-fail</strong></td>
+<td>boolean</td>
+<td>FALSE</td>
+<td>If TRUE, allow overall network configuration to proceed even if IPv4 configuration times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv6-only networks, setting this property to TRUE allows the overall network configuration to succeed if IPv4 configuration fails but IPv6 configuration completes successfully.</td>
+</tr>
</table><br/>
<p><h2>Setting name: 'ipv6'</h2></p>
<table cellspacing=10 border=0 cellpadding=2>
@@ -413,25 +425,25 @@
<tr align=left valign=top>
<td><strong>dns</strong></td>
<td>array of byte array</td>
-<td></td>
+<td>[]</td>
<td>Array of DNS servers, where each member of the array is a byte array containing the IPv6 address of the DNS server (in network byte order). For the 'auto' method, these DNS servers are appended to those (if any) returned by automatic configuration. DNS servers cannot be used with the 'shared' or 'link-local' methods as there is no usptream network. In all other methods, these DNS servers are used as the only DNS servers for this connection.</td>
</tr>
<tr align=left valign=top>
<td><strong>dns-search</strong></td>
<td>array of string</td>
-<td></td>
+<td>[]</td>
<td>List of DNS search domains. For the 'auto' method, these search domains are appended to those returned by automatic configuration. Search domains cannot be used with the 'shared' or 'link-local' methods as there is no upstream network. In all other methods, these search domains are used as the only search domains for this connection.</td>
</tr>
<tr align=left valign=top>
<td><strong>addresses</strong></td>
-<td>array of (byte array, uint32)</td>
-<td></td>
-<td>Array of IPv6 address structures. Each IPv6 address structure is composed of 2 members, the first being a byte array containing the IPv6 address (network byte order) and the second a 32-bit integer containing the IPv6 address prefix. For the 'auto' method, given IP addresses are appended to those returned by automatic configuration. Addresses cannot be used with the 'shared' or 'link-local' methods as the interface is automatically assigned an address with these methods.</td>
+<td>array of (byte array, uint32, byte array)</td>
+<td>[]</td>
+<td>Array of IPv6 address structures. Each IPv6 address structure is composed of 3 members, the first being a byte array containing the IPv6 address (network byte order), the second a 32-bit integer containing the IPv6 address prefix, and the third a byte array containing the IPv6 address (network byte order) of the gateway associated with this address, if any. If no gateway is given, the third element should be given as all zeros. For the 'auto' method, given IP addresses are appended to those returned by automatic configuration. Addresses cannot be used with the 'shared' or 'link-local' methods as the interface is automatically assigned an address with these methods.</td>
</tr>
<tr align=left valign=top>
<td><strong>routes</strong></td>
<td>array of (byte array, uint32, byte array, uint32)</td>
-<td></td>
+<td>[]</td>
<td>Array of IPv6 route structures. Each IPv6 route structure is composed of 4 members; the first being the destination IPv6 network or address (network byte order) as a byte array, the second the destination network or address IPv6 prefix, the third being the next-hop IPv6 address (network byte order) if any, and the fourth being the route metric. For the 'auto' method, given IP routes are appended to those returned by automatic configuration. Routes cannot be used with the 'shared' or 'link-local' methods because there is no upstream network.</td>
</tr>
<tr align=left valign=top>
@@ -452,6 +464,12 @@
<td>FALSE</td>
<td>If TRUE, this connection will never be the default IPv6 connection, meaning it will never be assigned the default IPv6 route by NetworkManager.</td>
</tr>
+<tr align=left valign=top>
+<td><strong>may-fail</strong></td>
+<td>boolean</td>
+<td>FALSE</td>
+<td>If TRUE, allow overall network configuration to proceed even if IPv6 configuration times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv4-only networks, setting this property to TRUE allows the overall network configuration to succeed if IPv6 configuration fails but IPv4 configuration completes successfully.</td>
+</tr>
</table><br/>
<p><h2>Setting name: '802-11-olpc-mesh'</h2></p>
<table cellspacing=10 border=0 cellpadding=2>
@@ -468,7 +486,7 @@
<tr align=left valign=top>
<td><strong>ssid</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>SSID of the mesh network to join.</td>
</tr>
<tr align=left valign=top>
@@ -480,7 +498,7 @@
<tr align=left valign=top>
<td><strong>dhcp-anycast-address</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>Anycast DHCP MAC address used when requesting an IP address via DHCP. The specific anycast address used determines which DHCP server class answers the the request.</td>
</tr>
</table><br/>
@@ -706,13 +724,13 @@
<tr align=left valign=top>
<td><strong>data</strong></td>
<td>dict of (string::string)</td>
-<td></td>
+<td>[ ]</td>
<td>Dictionary of key/value pairs of VPN plugin specific data. Both keys and values must be strings.</td>
</tr>
<tr align=left valign=top>
<td><strong>secrets</strong></td>
<td>dict of (string::string)</td>
-<td></td>
+<td>[ ]</td>
<td>Dictionary of key/value pairs of VPN plugin specific secrets like passwords or private keys. Both keys and values must be strings.</td>
</tr>
</table><br/>
@@ -755,8 +773,14 @@
<tr align=left valign=top>
<td><strong>mac-address</strong></td>
<td>byte array</td>
-<td></td>
-<td>If specified, this connection will only apply to the ethernet device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing).</td>
+<td>[]</td>
+<td>If specified, this connection will only apply to the ethernet device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
+</tr>
+<tr align=left valign=top>
+<td><strong>cloned-mac-address</strong></td>
+<td>byte array</td>
+<td>[]</td>
+<td>If specified, request that the device use this MAC address instead of its permanent MAC address. This is known as MAC cloning or spoofing.</td>
</tr>
<tr align=left valign=top>
<td><strong>mtu</strong></td>
@@ -764,6 +788,24 @@
<td>0</td>
<td>If non-zero, only transmit packets of the specified size or smaller, breaking larger packets up into multiple Ethernet frames.</td>
</tr>
+<tr align=left valign=top>
+<td><strong>s390-subchannels</strong></td>
+<td>GPtrArray_gchararray_</td>
+<td>[]</td>
+<td>Identifies specific subchannels that this network device uses for communcation with z/VM or s390 host. Like the 'mac-address' property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.</td>
+</tr>
+<tr align=left valign=top>
+<td><strong>s390-nettype</strong></td>
+<td>string</td>
+<td></td>
+<td>s390 network device type; one of 'qeth', 'lcs', or 'ctc', representing the different types of virtual network devices available on s390 systems.</td>
+</tr>
+<tr align=left valign=top>
+<td><strong>s390-options</strong></td>
+<td>dict of (string::string)</td>
+<td>[ ]</td>
+<td>Dictionary of key/value pairs of s390-specific device options. Both keys and values must be strings. Allowed keys include 'portno', 'layer2', 'portname', 'protocol', among others.</td>
+</tr>
</table><br/>
<p><h2>Setting name: '802-11-wireless'</h2></p>
<table cellspacing=10 border=0 cellpadding=2>
@@ -780,7 +822,7 @@
<tr align=left valign=top>
<td><strong>ssid</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>SSID of the WiFi network. Must be specified.</td>
</tr>
<tr align=left valign=top>
@@ -804,7 +846,7 @@
<tr align=left valign=top>
<td><strong>bssid</strong></td>
<td>byte array</td>
-<td></td>
+<td>[]</td>
<td>If specified, directs the device to only associate with the given access point. This capability is highly driver dependent and not supported by all devices. Note: this property does not control the BSSID used when creating an Ad-Hoc network and is unlikely to in the future.</td>
</tr>
<tr align=left valign=top>
@@ -822,8 +864,14 @@
<tr align=left valign=top>
<td><strong>mac-address</strong></td>
<td>byte array</td>
-<td></td>
-<td>If specified, this connection will only apply to the WiFi device whose MAC address matches. This property does not change the MAC address of the device (known as MAC spoofing).</td>
+<td>[]</td>
+<td>If specified, this connection will only apply to the WiFi device whose permanent MAC address matches. This property does not change the MAC address of the device (i.e. MAC spoofing).</td>
+</tr>
+<tr align=left valign=top>
+<td><strong>cloned-mac-address</strong></td>
+<td>byte array</td>
+<td>[]</td>
+<td>If specified, request that the WiFi device use this MAC address instead of its permanent MAC address. This is known as MAC cloning or spoofing.</td>
</tr>
<tr align=left valign=top>
<td><strong>mtu</strong></td>
@@ -834,7 +882,7 @@
<tr align=left valign=top>
<td><strong>seen-bssids</strong></td>
<td>array of string</td>
-<td></td>
+<td>[]</td>
<td>A list of BSSIDs (each BSSID formatted as a MAC address like '00:11:22:33:44:55') that have been detected as part of the WiFI network. The settings service will usually populate this property by periodically asking NetworkManager what the device's current AP is while connected to the network (or monitoring the device's 'active-ap' property) and adding the current AP's BSSID to this list. This list helps NetworkManager find hidden APs by matching up scan results with the BSSIDs in this list.</td>
</tr>
<tr align=left valign=top>
@@ -877,19 +925,19 @@
<tr align=left valign=top>
<td><strong>proto</strong></td>
<td>array of string</td>
-<td></td>
+<td>[]</td>
<td>List of strings specifying the allowed WPA protocol versions to use. Each element may be one 'wpa' (allow WPA) or 'rsn' (allow WPA2/RSN). If not specified, both WPA and RSN connections are allowed.</td>
</tr>
<tr align=left valign=top>
<td><strong>pairwise</strong></td>
<td>array of string</td>
-<td></td>
+<td>[]</td>
<td>If specified, will only connect to WPA networks that provide the specified pairwise encryption capabilities. Each element may be one of 'wep40', 'wep104', 'tkip', or 'ccmp'.</td>
</tr>
<tr align=left valign=top>
<td><strong>group</strong></td>
<td>array of string</td>
-<td></td>
+<td>[]</td>
<td>If specified, will only connect to WPA networks that provide the specified group/multicast encryption capabilities. Each element may be one of 'wep40', 'wep104', 'tkip', or 'ccmp'.</td>
</tr>
<tr align=left valign=top>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
