Getting started with HS20 r2 (OSU client/server and such?)

[Ben Greear]

On 03/17/2015 08:22 AM, Jouni Malinen wrote:
> On Tue, Mar 17, 2015 at 08:06:54AM -0700, Ben Greear wrote:
>>> Number of clients may recognize OSEN configuration as WEP.
>>
>> Should this be fixed in the wpa-cli scan output to show OSEN instead
>> of WEP?
> 
> Probably, or well, in wpa_supplicant scan result processing. It looks
> like it does not currently have any special case for OSEN, so the [WEP]
> default gets used if privacy is set.

I can work on that...

>> Ok.  What should happen before the cmd_signup() is called, or maybe a better
>> question, how should a station determine that it should do cmd_signup?
> 
> That's pretty much the first operation.. The exact trigger depends on
> what kind of user experience is desired for the specific device, but
> that could be, e.g., scan showing no matching networks.

Do you happen to have an example OSEN hostapd config file, and even
better, a pair with one OSEN and one .1x config file meant to work
together in conjunction with the hs20 client/servers?

If not, would it be correct to assume that the OPEN/OSEN hostapd config
file has all of the HS20 configurables, and the .1x is mostly just normal
with .1x radius config info (ie, no HS20 attributes)?

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com