Freeradius + WPA2 + Windows Client

[Fajar A. Nugraha]

On Fri, Aug 20, 2010 at 10:05 AM, rrperez <rrperez at apc.edu.ph> wrote:
>
> Thanks for this response Fajar,
>
> It definitely make sense, now I'm trying to install Open1x, but I can't find
> a manual on how to configure this. Do you know some references that can help
> me configuring Open1x?

No, sorry. You might have better luck asking on Open1x list, or just
explore the options that the GUI provides.

I've tested wpa_supllicant for windows (second link on my original
mail) some time ago. The file README-Windows.txt has some
documentation on using it (if you like using command line), but you'd
probably want to stick with the GUI (which is pretty much
self-explanatory).

FWIW, officially my company uses Odyssey Access Client (there's trial
version available:
http://www.juniper.net/support/products/oac/ent/#sw) for Windows to
connect to connect to wireless network, using PEAP-GTC, authenticating
to Lotus Domino LDAP. I don't use it though, and simply use Ubuntu
Lucid with its built-in network-manager (which can connect just fine).

Whatever supplicant you use, if you want to go through PEAP-GTC route
like I do, you basically need to configure the supplicant client to
choose:
- 802.1X (or WPA2 enterprise if it's not available) wireless security
- EAP or EAP-PEAP, or PEAP authentication protocol (different
supplicant may use different terms)
- GTC or EAP-GTC inner authentication
you may also need to disable server certificate verification (since
most likely you'll be using self-signed certificate, at least for
testing purposes)

-- 
Fajar