wpa_supplicant as library...

Stjepan Gros sgros
Tue Oct 3 06:14:06 PDT 2006


I'm continuing the story with ikev2 and wpa_supplicant based on your
advice to include only EAP machines into IKEv2 daemon.

We also figured out that on responder side, we only need to use radius
client module (RADIUS server will implement state machines).

Anyway, I made Makefiles that should be placed into the follwing

Makefile.lib.hostapd into wpa_supplicant/hostapd
Makefile.lib.utils into wpa_supplicant/utils
Makefile.lib.wpa_supplicant into wpa_supplicant/wpa_supplicant

Note that in each Makefile there are some variables at the top that
define where libraries and header files will be installed.

Now, it's possible to make dynamic libraries and install them with
simple make/make install steps.

Also, attached is examples archive that contains few simple examples
that can be compiled using those libraries and header files (adjusting
of library directory is probably necessary).

It's not complete, and certainly it's not perfect. But, before
continuing, there are some questions. Is this right step? Do you agree
that things should be done this way? Do you have any comments and/or


P.S. I can make patches to wpa_supplicant if it's easier for someone to
tries these changes.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_lib_v00.tar.gz
Type: application/x-compressed-tar
Size: 3902 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061003/5f2d7f9d/attachment.bin 

More information about the Hostap mailing list