Menu
▾
▴
#243 Windows build fails to handle interface disable/re-enable
The Windows build of xsupplicant fails to handle situations where a wireless interface is disabled while connected and then subsequently re-enabled. After this sequence, the UI still shows the wireless interface as connected, even though the connection is not established and is lacking an IP. If you then click "Disconnect", two error dialogues appear:
1. Error: Failed to set the SSID for interface Intel(R) PRO/Wireless 2200BG Network Connection - Teefer2 Miniport.
2. Error: Failed to set the 802.11 infrastructure mode for interface Intel(R) PRO/Wireless 2200BG Network Connection - Teefer2 Miniport. Please be sure that your wireless card drivers are current.
All subsequent attempts to connect to the wireless network show additional copies of the error dialogues above. If you then quit out of xsupplicant, agreeing to terminate connections, and re-open the application, these error messages display again. The problem is resolved after rebooting Windows.
Additional information:
- Versions of xsupplicant tested: 2.0.1 / 2.1.9
- Windows version: XP SP3, all MS updates applied as of 2009/12/11
- Wireless adapter: Intel(R) PRO/Wireless 2200BG
- Wireless network configuration: WPA2-Enterprise, AES, PEAP/MSCHAPv2
- Reason for disabling/re-enabling wireless: We use the NicSwitch util (http://www.netswitcher.com/NicSwitch/nicswitch.htm) to ensure only one physical connection is active at any given time. This is needed to allow transparent switching between wired/wireless while maintaining a single IP address assigned by DHCP.
