wpa_supplicant ad-hoc settings

Per-Henrik Lundblom per-henrik.lundblom at connectblue.com
Fri Nov 19 03:11:34 EST 2010


On 2010-11-18 20:28, Jouni Malinen wrote:

> Are you suggesting that wpa_supplicant would take more active role in
> IBSS BSSID generation, merges, and channel selection?

No, not really. I suggest that wpa_supplicant, when configured for 
adhoc, should provide all information available down to the driver. In 
the case where a matching IBSS network is found that information would 
be BSS ID, ESSID, frequency and mode (ad-hoc). In the case no network is 
found the information would be ESSID, frequency (if available from the 
frequency config directive) and mode (ad-hoc).

> Which the is the part I was referring to with it being possible to
> extend this..

OK. Don't get me wrong here. I'm not the one complaining about missing 
features or such. I just want to understand why certain things are 
working in the way they do.

> Depends on what you including in handling IBSS.. wpa_supplicant takes
> care of some parts, driver others.. I don't see that ever changing; the
> border between the modules may move, but frankly, IBSS is not really
> that high on my interest list and I would much rather use my time on
> station and AP mode.

Unfortunately I think that is true for most WLAN users, both consumer 
and enterprise. Still I think the wpa_supplicant would be a greater 
piece of software with (in my eyes) better ad-hoc support.

Regards,

PH

-- 
Per-Henrik Lundblom
System engineer

connectBlue AB
Norra Vallgatan 64 3V, SE-211 22 Malmö, Sweden
Tel. +46 40 6307100, Direct tel. +46 40 6307126
Cellular +46 733 207126, Fax +46 40 237137
per-henrik.lundblom at connectblue.com
www.connectblue.com



More information about the HostAP mailing list