<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>[0.5.10 PATCH] Add WiFi Protected Setup (WPS) support</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>This is an alpha quality patch adding both PIN and Push Button Configuration (PBC) for an enrollee. Alpha means:<BR>
- it is not feature complete<BR>
- it has had limited testing<BR>
- it has bugs and may accidentally erase your harddrive :)<BR>
<BR>
That said, I wanted to send this out to get some early feedback on a number of areas including the control interface additions, supplicant and device driver requirements, and the over all integration with the supplicant.<BR>
<BR>
The testing to date has been against a DLink DGL-4500 on an embedded system. The patch includes modifications to driver_wext.c but not the others (ie madwifi, prism, etc) drivers. Additionally, kernel device drivers need to pass up the WPS IE as part of the scan results. To build, add<BR>
CONFIG_EAP_WPS=y<BR>
CONFIG_IEEE8021X_EAPOL=y<BR>
to the .config file. Unfortunately, this first release requires OpenSSL, but I hope to remove this requirement in the near future. To run, create a wpa_supplicant.conf file that has<BR>
<BR>
network={<BR>
proto=WPS<BR>
eap=WPS<BR>
}<BR>
<BR>
To connect using PBC, use the wpa_cli 'pbc' command. To connect using a PIN, first get the PIN via the wpa_cli 'pin_get' command. Once you have entered this into the registrar, use the wpa_cli 'pin_entered' command to start the connection process.<BR>
<BR>
The patch is hosted on SourceForge (<A HREF="https://sourceforge.net/projects/wpsetup/">https://sourceforge.net/projects/wpsetup/</A>).<BR>
<BR>
---chuck</FONT>
</P>
</BODY>
</HTML>