Release Notes for
Intel(R) PROSet/Wireless Software
Version 11.5.0.0 for Windows Vista*

Supported Adapters
Operating Systems
Viewing User Documentation
Upgrading Drivers and Utilities from Previous Versions
Recommended Power Save Settings
Recommended Power Configuration
Known Issues
Customer Support
Third Party Software Notices

Supported Adapters

Intel(R) PROSet/Wireless software is compatible with the following adapters:

Intel(R) Wireless WiFi Link 4965AGN
Intel(R) Wireless WiFi Link 4965AG_
Intel(R) PRO/Wireless 3945ABG Network Connection
Intel(R) PRO/Wireless 3945BG Network Connection
Intel(R) PRO/Wireless 2915ABG Network Connection
Intel(R) PRO/Wireless 2200BG Network Connection

Operating Systems

This release of Intel(R) PROSet/Wireless software runs on Microsoft* Windows Vista*.

NOTE: To function correctly, this application requires the installation of Windows Vista Hotfix KB932063. See http://support.microsoft.com/default.aspx/kb/932063

Viewing User Documentation

To access user documentation, load the Intel(R) PROSet/Wireless CD. Click View User Guide on the Intel PROSet/Wireless Installer screen.

Upgrading Drivers and Utilities from Previous Versions

When you run the Intel(R) PROSet/Wireless Installer program, it automatically replaces all previous versions of Intel(R) PROSet/Wireless software and any installed utilities, with version 11.5.0.0

Recommended Power Save Settings

To optimize power settings, follow the instructions provided at the following support site:

http://www.intel.com/support/wireless/wlan/sb/CS-024509.htm

Recommended Power Configuration

A client disassociates upon moving from hibernation mode when the following conditions are met:

A client is connected to an 802.1X profile.
The Power Management setting in the Adapter Settings is configured to "Allow the device to bring the computer out of standby".
In Windows, the system is configured to move automatically from standby to hibernation in the Power Option Properties.

The recommendation is to set the system hibernate power option to “Never” when the computer is on AC power.

Known Issues

Operating in 802.11n Mode

Intel recommends using security with your wireless network. The Intel(R) Wireless WiFi Link 4965AGN adapter can only achieve transfer rates greater than 54 Mbps on 802.11n connections when using AES security, or no security. You should only use no security when setting up or troubleshooting the network.

To enable AES for Personal Security, select WPA-Personal (AES-CCMP) or WPA2-Personal (AES-CCMP) in the Security Settings pulldown menu. To enable AES for Enterprise Security, select AES-CCMP in the Data Encryption pulldown menu.

Wi-Fi* Protected Setup*

Wi-Fi* Protected Setup* is supported only on the 3945ABG Network Connection, the Wireless WiFi Link 4965AGN, and Wireless WiFi Link 4965AG_.

Engineering Release Notes

WoWLAN is not supported with NETBIOS packets on Microsoft Windows Vista. This is expected to be fixed by Microsoft at SP1.
When the driver is uninstalled, the default setting loads the Microsoft Windows Vista inbox driver.

Cisco EAP-FAST Vista Plug-In

EAP-FAST requires Cisco ACS server version 4.0 or later for full functionality support. EAP-FAST Does Not Update Profile With User's Choice to Use Matching PAC Authority. The user keeps getting prompted that the PAC authority he is trying to connect to is different from what he has configured in his profile.
Workaround: Manually edit profile to select correct PAC authority.
Profile GUIs for LEAP, PEAP, and FAST Show Actual Length of Saved Password. EAP-FAST Does Not Correctly Handle Scenario of User Saving Invalid Credentials in Profile. In the case that only unauthenticated provisioning is enabled on the ACS server, users who save incorrect credentials in FAST profiles will not be connected reliably even if they enter correct credentials at the prompt. Furthermore, the profile is not updated with correct credentials. (This behavior is a result of limitations in both Vista and ACS.)
Can't authenticate using windows credentials using default inner method settings with ACS 3.2.3. EAP-FAST is by default configured to use EAP-MSCHAPv2 with Windows user credentials, but ACS Version 3.2.3 only supports EAP-GTC inner method during authentication phase. So, authentication will fail with default configuration. Workaround: Upgrade to ACS Version 3.3 or above or set the profile to use EAP-GTC inner method.
EAP-FAST profile does not use newly provisioned PAC. On a device with no PAC, anonymous tunnel PAC provisioning is successful. However, on subsequent authentication attempts, you are prompted to use the new PAC instead of the PAC that the profile should use automatically. If you accept the new PAC, the prompt does not appear for subsequent authentications.
Workaround: Select the PAC that should be used from the Select a PAC Authority to use menu in the EAP-FAST settings, or accept the prompt to use the new PAC.

Cisco PEAP-GTC Vista Plug-In

PEAP-GTC requires Cisco ACS server version 3.2.3 or later.
PEAP-GTC machine authentication fails with all currently-released versions of ACS. Default configuration of the profile for SSO will likely result in a failed pre-logon connection attempt. In order to successfully make SSO (pre-logon) connections, it is necessary to configure the profile to authenticate for users only (“user”, not “machineOrUser”).
Workaround: This requires modification of the <authMode> in the XML file corresponding to the profile.
Next authentication after SSO password change fails. After the SSO password is successfully changed, the next authentication fails. This condition occurs during Fast User Switch (when you switch users and log on as the same user again). This condition will be resolved in Vista Service Pack 1.
Next authentication after SSO OTP fails. This condition occurs during Fast User Switch (when you switch users and log on as the same user again). This condition will be resolved in Vista Service Pack 1.
ntdll.dll crashes during PEAP-GTC authentication. The module is configured to prompt for credentials and to ask the user to verify server certificate (none are selected as trusted). The EAPHost chooses to process the second identity request from two that have been received. After getting credentials from the user, sometimes the EAPHost immediately prompts for credentials again. While the user is entering credentials, the authentication proceeds with credentials from the first prompt until the module asks the user to verify the server certificate. The authentication then stops, but the corresponding dialog does not appear. After the credentials dialog is closed ntdll.dll crashes.

Cisco LEAP Vista Plug-In

LEAP requires Cisco ACS server version 3.3 or later.
LEAP authentication does not succeed against Cisco ACS 3.2.3
The ACS server sends incorrect packets during authentication. These packets are ignored by the EAPHost. This condition is fixed in ACS release 3.3.
The module does not prevent invalid saved credentials from being reused.
When the network is configured with automatic connection, the LEAP module does not prevent invalid saved credentials from being reused repeatedly. This behavior could lead to account locking, especially in the case of pre-logon authentication. The supplicant can only attempt approximately 15 authentications.

Known Microsoft Vista Issues Pertaining to EAP Authentication

Client Machine Does Not Associate Automatically to AP2 After Unsuccessful Association Attempt to AP1. When the same SSID is configured on AP1 and AP2, the Vista client does not automatically associate to AP2 if its authentication attempt to AP1 failed. (Microsoft’s Native WiFi stack disables the profile for 20 minutes due to the previous EAP failure.)
No connections possible with Windows credentials using PEAP-MSCHAPv2 unless Client Machine is joined to domain. Connections using PEAP-MSCHAPv2 profiles configured to use Windows logon credentials (default configuration) will fail unless the client is already joined to the Windows computer domain.
When Using Remote Desktop, Client Machine Fails 802.1X Authentication When AP's Radio is Disabled/Enabled. While using Remote Desktop, when the AP to which a client is connected has its radio disabled and re-enabled after 30 seconds, the EAP process will fail. (If not using Remote Desktop, EAP will succeed.)

The following known issues are fixed in Vista by the Hotfix KB932063

EAPHost shows Cisco PEAP-GTC after MS PEAP has been configured. After an MS PEAP profile has been configured and the Wireless Network profile dialog has been opened again, the Cisco PEAP-GTC method is selected in the authentication method list, even though authentication correctly performs MS PEAP. Also, when a new profile is created, the default selected method is Cisco PEAP-GTC.
EAPHost crashes when server rejects outer identity. When the server fails authentication immediately after receiving outer identity (IAS-specific behavior), the EAPHost/supplicant crashes in onex.dll:OneXShowUI. The crash stack does not include the PEAP module.
Unable to do pre-logon user authentication. There is no authentication at all, and sometimes the EAPHost crashes.
UI not selecting the correct method when displaying saved profile on next raising of the UI.
Wireless IHV profiles get corrupted on editing them.
IHV Profiles prompt the user for credentials for every roam.
Supplicant not renewing IP address after switching VLAN.
1x module is not checking against the authorId/vendorId before parsing PEAP data.

Customer Support

Main Intel web support site: http://support.intel.com

Network products information: http://www.intel.com/network

Worldwide access: Intel has technical support centers worldwide. Many of the centers are staffed by technicians who speak the local languages. For a list of all Intel support centers, the telephone numbers, and the times they are open, visit http://www.intel.com/support/9089.htm.

Third Party Software Notices

Intel® PROSet/Wireless Software

Portions of Intel(R) PROSet/Wireless Software include software under the following terms:

OpenSSL License

Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License

Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related.
If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS:' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

zlib.h -- interface of the 'zlib' general purpose compression library, version 1.2.3, July 18th, 2005

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
This notice may not be removed or altered from any source distribution.

Jean-loup Gailly jloup@gzip.org
Mark Adler madler@alumni.caltech.edu

Intel(R) Wireless WiFi Link 4965AGN Driver

Portions of the driver include software under the following terms:

wpa_supplicant

Copyright (c) 2003-2007, Jouni Malinen <jkmaline@cc.hut.fi> and contributors. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Jouni Malinen nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

__________

LICENSE TERMS

The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that:

Distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer;
distributions in binary form include the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other associated materials;
the copyright holder's name is not used to endorse products built using this software without specific written permission.

DISCLAIMER

This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not limited to, correctness and fitness for purpose.

Issue Date: 29/07/2002

This file contains the definitions required to use AES (Rijndael) in C.

Trademark and Disclaimers information: Intel(R) is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. * Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Intel disclaims any proprietary interest in trademarks and trade names other than its own.

* Microsoft, Windows, and Vista are registered trademarks of Microsoft Corporation. Other names and brands may be claimed as the property of others. Intel Corporation assumes no responsibility for errors or omissions in this document, nor does Intel make any commitment to update the information contained herein.

September 2007

Release Notes for Intel(R) PROSet/Wireless Software Version 11.5.0.0 for Windows Vista*