###############################################################################BetaTester installation intructions- replace installed wpa_supplicant.exe with the included oneWhen using xwlan widget wpa_supplicant is usually found in\util\xworkplace\plugins\xcenter\xwlan\.When using the standalone wlanstat then in .\xwlan\.- check if the new version is used by xwlan/wlanstatright-click - properties - tab 'WPA supplicant' check version and path- connect to wpa protected networks and post your findings at correspondendingthread at os2world.com- you can also test wpa_supplicant with a .conf file. F.i. set up a profilewith no security, switch on wireless and start wpa_supplicant manually(f.i. wpa_supplicant.exe -i lan1 -cwpa_supplicant.conf)###############################################################################If someone want to test feel free to post your findings here. If you're using the xcenter widget (in contrary to the standalone wlanstat.exe), be sure your ALT-F1 boot works or you've a working maintenance partition. I once saw a hang on my T60 at bootup of the xwlan widget with teh new wpa_supplicant.

Hi Andi, thanks for the update.The readme.os2 needs updating to refer to where ArcaOS stores its wpa_supplicant.exe, namely x:\sys\apps\xwps\plugins\xcenter\xwlanAfter rebooting (is this needed? Perhaps add to readme.os2) right clicking shows I'm now using wpa_supplicant v2.2 (eCS-v1) which I have to assume is correct.Double clicking the widget connected to my internet hub fine, seemed to connect quicker. Firefox loaded pages fine.This on a T42

I must of mis-clicked when copying the exe. Now it says "wpa-supplicant v2.7-devel (OS2-v2beta)-hostap_2_6-1746-gba5 and perhaps 4, it is clipped at this point as itis wider then the settings window.Seems to work fine.

Hi Andi,I start wpa_supplicant by using a .conf file. and do not use xwlan. For some reason this only worked (until know) with a very old version of wpa_supplicant dated from 2008.I tried the one you uploaded (thank you for all the work!). At first it did not work, this was the message shown:Successfully initialized wpa_supplicantlan0: No network configuration found for the current API amended my .conf with ap_scan=2, this helped, works now

Good to hear. The .conf file is full of documentation. Honestly I've to say I do not understand what all the options are good for. I only enabled the build to allow .conf file cause someone asked it long ago in a ticket IIRC. I never used it by myself and so can do only very limited testing. This is one reason why I asked here for testers.

I did a little more testing with your new build compared to the old one I use.

For the records: The old wpa_supplicant is shown as version 0.5.7.This one works well when using a .conf file and works well with xwlan too. The connection to my wlan is established extremely fast.Message :Trying to associate with SSID 'WLAN-KHH8TK'Associated with 08:7a:4c:01:98:2eWPA: Key negotiation completed with 08:7a:4c:01:98:2e [PTK=CCMP GTK=CCMP]CTRL-EVENT-CONNECTED - Connection to 08:7a:4c:01:98:2e completed (auth) [id=0 id_str=]

The new build works well too in xwlan and using a .conf file but connection is sometimes established slower.Message:lan0: No network configuration found for the current APlan0: CTRL-EVENT-DISCONNECTED bssid=18:00:71:08:31:1e reason=3 locally_generated=1 ndis_get_oid res=36lan0: No network configuration found for the current APlan0: CTRL-EVENT-DISCONNECTED bssid=18:00:71:08:31:1e reason=3 locally_generated=1lan0: Trying to associate with SSID 'WLAN-KHH8TK' ndis_get_oid res=36lan0: Associated with 08:7a:4c:01:98:2e ndis_get_oid res=36lan0: WPA: Key negotiation completed with 08:7a:4c:01:98:2e [PTK=CCMP GTK=CCMP]lan0: CTRL-EVENT-CONNECTED - Connection to 08:7a:4c:01:98:2e completed [id=0 id_str=]

Both messages are what I see when using xwlan and choosing wpa_supplicant visible.And sometimes when using the new build connection is interrupted and it may take several tries to reestablish the connection.

Using the .conf file the messages are the same as above, depending on which wpa_supplicant I use.Using your new build with a .conf file I played around with the ap_scan= line documented in the wpa_supplicant.conf included in the new build.The best seems to be to set ap_scan=2, but I admit, I have no idea why?

Using with XWLAN/WLANSTAT-------------------------- Replace installed wpa_supplicant.exe with the included one. When using xwlan widget wpa_supplicant is usually found in \util\xworkplace\plugins\xcenter\xwlan\. When using the standalone wlanstat then it is in .\xwlan\.- Check if the new version is used by xwlan/wlanstat (right-click - properties - tab 'WPA supplicant' check version and path)- Connect to wpa protected networks and post your findings at correspondending thread at os2world.com

- You can also test wpa_supplicant with a .conf file. F.i. set up a profile with no security, switch on wireless and start wpa_supplicant manually (f.i. wpa_supplicant.exe -i lan1 -cwpa_supplicant.conf - see wp.cmd)

Using with wpa_gui.exe----------------------wpa_gui is a QT frontend for wpa_supplicant. You can use it instead ofxwlan/wlanstat for managing your wireless networks. It works for me and I canconnect to my local wireless networks here.- Start wpa_supplicant with a .conf file f.i. wp.cmd- Use wpa_gui for scanning and configuration

As usual your wireless card has to be supported by genmac to use wirelessnetworks with OS/2.

There is also included wpa_cli.exe. But this is not tested very well.###############################################################################

@Holger - I've seen these delays in establishing the connection since ages. I guess this is the way it works since a long time on OS/2. But I do not have any *nix system to test against. Though it may be a timing problem together with genmac too. I don't think it does make much sense to test against v0.5.7 as I don't even know if we have the sources for the OS/2 version somewhere.

I've uploaded a new testbuild. It includes latest changes from official development tree. I've updated some old OS/2 source files to current level where possible too. Some new options in wpa_supplicant.conf are enabled (the ones which does not stop compiling).

If you have pmprintf.dll on your system then the debug messages are routed there too. The output maybe better readable in the PM window than in the VIO.

Unfortunately I had to delete the old versions cause some sites directly linked to an old version. The drawback is I don't see the download counter for them. I didn't find a way to simply rename the binary on bitbucket.