OS/2, eCS & ArcaOS - Technical > Networking

Test build wpa_supplicant v2.7 - v2.10-devel

<< < (5/7) > >>

Andi B.:
Once again I updated to the latest sources from the official git repository. It's still a development version.

--- Code: ---wpa_supplicant v2.10-devel (OS/2, Dec 20 2020 18:50:55, AB)
--- End code ---
No clue when Jouni wants to make the official 2.10 version.

Be aware these build needs latest openssl and libc libraries from bww/netlabs rpm. Some workarounds in older version could be cleaned up this way.

It works on one of my machines. But as I don't use wireless very much these days it has only limited testing here.

If you like to test it get it from the usual place - https://bitbucket.org/Andi_B/os-2-wpa_supplicant/downloads/. Again, don't post direct links to files inside this directory.

There were a lot of changes made in a lot of files. Honestly I've no clue if we can use all these new features or if they are only available with more advanced driver interfaces than ours. The genmac interface and the l2_packet handling may limit some functionality on our platform. But I tried to compile with standard .config as much as possible.

As usual you can replace the supplicant coming with xwlan with this version. Or you can play with wpa_gui.exe and wpa_supplicant.conf.

Andi B.:
Updated again to current development sources (July 2021). https://bitbucket.org/Andi_B/os-2-wpa_supplicant/downloads/.

Unfortunately bitbucket has changed and no more can be used with our Seamonkey :-(. Had to install simplebrowser for uploading.

Andi B.:
Official v2.10 for other platforms is out for a while now. I started to port it to OS/2 immediately after it was released. There are a lot of changes but I think no really important things for us compared to my latest release. Anyway I wanted to make this official release available for us too. But there is a problem which I stuck currently so I can't say if or when I can finish 2.10 release. Problem is the current code needs a lot of time to establish a wpa2 secured connection here. Definitely longer then with my previous release. Sometimes it seems it takes forever. I'm currently stuck with this problem.

I've done a lot of ifdefs for IPv6 code. Although there is a compiler switch for IPv6 these were missing. It seems on other platforms they can't imagine that there are still platforms out there without IPv6 support. Although my current code compiles fine this 'long time to connect' problem drives me crazy. No clue if it's a problem with our genmac driver or some porting issue. Anyway if anyone wants to play with the code and help to debug (reading and interpreting wpa_supplicant debug messages) drop me a mail. I'll update the source code at my bitbucket git repository. But there are some test code which needs to cleaned up once the connection problem is solved before making a release. This is just to keep you informed.

Edit - can't upload to bitbucket anymore -

--- Code: ---remote: Bitbucket Cloud recently stopped supporting account passwords for Git authentication.
remote: See our community post for more details: https://atlassian.community/t5/x/x/ba-p/1948231
remote: App passwords are recommended for most use cases and can be created in your Personal settings:
remote: https://bitbucket.org/account/settings/app-passwords/
fatal: Authentication failed for 'https://xxxxxx@bitbucket.org/Andi_B/os-2-wpa_supplicant/'
--- End code ---

Tried to setup a ssh key. But it's not possible to add the public key at bitbucket.org with our browsers :-(

Edit2 - uploaded current code to https://sourceforge.net/projects/wpa-supplicant/

Dave Yeo:
Yea, Bitbucket has really gone down hill since Atlassian bought them out. I was trying to upload binaries of the Mozilla apps, uploaded Firefox and then trying to upload SM, I started getting permission denied errors.
Might move to Sourceforge, as it seems the only site that works with our old browsers. Even Bitbucket I have to use the SimpleBrowser to use.

Andi B.:
Yes did the same in the meantime - https://sourceforge.net/projects/wpa-supplicant/

Seems bitbucket locked us out since March 1. I've problems with ssh to sourceforge too. But https still works there. At least from command line. SmartGit doesn't work :-(

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version