No subject

[bogus at does.not.exist.com]

you need an open or OSEN ap for the initial OSU traffic.

a) So, for a simplistic setup, perhaps you use one virtual AP interface
as the OSEN, and then have a second that is running 802.1x.

Or, is there some way to make one hostapd instance able to do both?

(I tried just adding osen=1, but now the thing shows up as WEP encrypted,
 in the scan results of wpa_cli, which I am not sure is right...)

Assuming a) is right, then maybe the connection logic is to look for any
Open or OSEN APs advertising HS20, connect to them if we can find them, fetch list of icons
using 'wpa_cli ... fetch_osu', present these to the user, and let them make the selection.

After that, this is where the OSU client is used to somehow get credentials,
and then we connect to the .1x ap and are finally fully connected to the network?

Thanks,
Ben


On 03/16/2015 04:04 PM, Ben Greear wrote:
> On 03/13/2015 11:10 AM, Jouni Malinen wrote:
>> On Fri, Mar 13, 2015 at 10:22:42AM -0700, Ben Greear wrote:
>>> I just found the hs20/server/hs20-osu-server.txt file..that looks like a good place
>>> to start at first glance.
>>>
>>> And the hs20 test file seems to use it as well in some of the test cases?
>>>
>>> Looks like just source code in the hs20/client directory, but that
>>> can be read as well :)
>>
>> It needs to be understand that neither the OSU server nor the client
>> code is really ready for production use (i.e., useful for developer
>> testing, but that's about it without significant additional effort) and
>> that's also behind there being not much documentation available for them
>> or high priority in addressing that. The server setup used to be pretty
>> complex, but it is at least somewhat easier now with newer Apache
>> version being included in distros.
>>
>> For client, the command line usage documentation should give a pretty
>> clear idea on how it can be used as long as you are familiar with the
>> Hotspot 2.0 Rel 2 specification and how the OSU protocol works. And if
>> you are not, you'll have hard time getting this doing anything useful..
>> :)
> 
> So, I'm digging into all of this.
> 
> First, I noticed that you need 'osu_dir' in the supplicant config file,
> but it is not documented yet.  I'll send a patch when I understand this
> better if no one beats me to it.
> 
> And if someone could indulge me, I have what is probably a basic
> question:
> 
> I notice that I can use the 'wpa_cli -i sta0 fetch_osu'
> command, and it will get some information and icons using ANQP/GAS and place them in
> the configured directory.
> 
> But, nothing calls this automatically as far as I can tell.
> 
> So, what is the expected behaviour and/or interaction with wpa_supplicant
> to get the OSU icons and information.  Is that something the osu client
> is supposed to initiate?
> 
> I assume after I have icons and info, I can then start doing more of the
> clever stuff to actually authenticate with one of the 'icons'.
> 
> Thanks,
> Ben
> 
> 
>>
>> I'm not completely sure what you are referring to with the "hs20 test
>> file". If that is referring to the hwsim tests, then no, those test
>> cases do not yet exercise any of the hs20/{client,server} functionality.
>>  
>>
> 
> 


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