Re: WPA+Prism54(association request)

--===============1989464036==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="I7gN1YuHeqxrxkIZ"
Content-Disposition: inline


--I7gN1YuHeqxrxkIZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 30, 2005 at 07:24:28PM +0800, cathylilu wrote:
> Dear All,
>=20
>         Now I am working on wpa_supplicantv0.2.5+prism54. My problem is t=
hat
> wpa_supplicant can not send "ASSOCReq" to the WPA-AP.
>=20
> It seems that Prism54 driver can not be triggered to send "ASSOCReq" fram=
e.
> I know that the Prism54 did not support WPA. So I modify the prism54 based
> on initial path from Jouni Malinen  <mailto:[email protected]>
> [email protected].
>=20
>     Did anybody encounter the same problem or any comment for me? I will
> very appreciate.=20
>=20
> Thanks in advance=20
>=20
> Cathy Liu

Cathy,=20

prism54 does have WPA client code and it's probably 95% complete. I just
can't figure out what's wrong. You should look into our latest svn
release and work off of that.

	Luis

--=20
GnuPG Key fingerprint =3D 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

--I7gN1YuHeqxrxkIZ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCU2iYat1JN+IKUl4RAglrAJ4my3K9k+12MTVzCiyrEJInhpAIBACdFXaA
RMqYL8Fh4Nd6CjMSHIwyrtA=
=HOgn
-----END PGP SIGNATURE-----

--I7gN1YuHeqxrxkIZ--

--===============1989464036==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Prism54-users mailing list
[email protected]
http://prism54.org/mailman/listinfo/prism54-users

--===============1989464036==--