any tutorial for implementing WPA-Personal (PSK) / CCMP (AES?) using wpa_supplicant on Windows 2000 Professional SP4+SRP1
j at w1.fi
Fri Dec 18 14:20:38 EST 2009
On Thu, Dec 17, 2009 at 09:49:28PM -0800, K_McIntosh wrote:
> I installed 'wpa_supplicant-0.6.9.exe', the latest stable release binary installer for Windows (as well as 'WinPcap_4_0_2.exe', during the latter's install) and am having a little trouble out of the gate ... (I have noted that the 'wpa_gui' program is unusually slow to react to user input - could there be an installation or environment issue?)
I have no tested 0.6.9 on Windows 2000 and don't know what to expect on
its functionality there. Your description seems to indicate that there
would indeed be problems that may end up with wpa_supplicant service
getting terminated unexpectedly.
> I have tried disabling the 'Wireless Configuration' service in Windows and have now made the 'wpa_supplicant service' Automatic (I also tried a change to the 'wpa_supplicant service' Log On - Log on as: Local System account by enabling sub-option 'Allow service to interact with desktop'), however, no change in results with 'wpa_gui' Add Interface or Network (I also tried executing 'wpasvc.exe' just to see what would happen ... it is one and the same as the 'wpa_supplicant service').
When running wpasvc manually, you will need to add "app" as a command
line argument to get it actually run in operational mode. If you enable
debugging (set debug_level variable to 2 in registry
HKLM\Software\wpa_supplicant key), "wpasvc app" should show debugging
> I have looked fairly carefully at the 'wpa_supplicant.conf' file and am wondering if I need to make changes there first in order to get the ball rolling, so to speak.
wpasvc will read the configuration from Windows registry. If you want to
try wpa_supplicant.exe, you can use the text file based configuration.
As a quick test, you could just create an empty configuration file and
run wpa_supplicant.exe with verbose debugging enabled (-dd on command
line). Check README-Windows.tx tfor other command line arguments needed
> Because my access point normally runs in "hidden SSID" mode, eventually I will need to edit 'wpa_supplicant.conf' to reflect ap_scan=2 mode, but first things first.
The default configuration in Windows registry (i.e., the configuration
used by wpasvc) uses ap_scan=2 by default, but yes, if you use
wpa_supplicant.exe, you will need to add ap_scan=2.
Jouni Malinen PGP id EFC895FA
More information about the HostAP