Re: mac80211 ad-hoc mode problems

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]

On Tue, 2008-06-03 at 21:41 -0400, Dan Williams wrote:
> Hi,
> 
> While adding adhoc shared network support to NM, I ran into a few
> mac80211 problems.
> 
> 1) doesn't send SIOCGIWAP event on successful adhoc activation (patch
> forthcoming)

Thanks.

> 2) takes a _really_ long time to create an adhoc network.  This is
> controlled by IEEE80211_IBSS_JOIN_TIMEOUT.  Why is that 20 seconds?  The
> problem here is that wpa_supplicant has an association timer shorter
> than IEEE80211_IBSS_JOIN_TIMEOUT and will re-try the connection,
> causing mac80211 to reset ifsta->ibss_join_req.  FullMAC drivers will
> simply look in their scan list (and optionally perform one scan) and if
> the IBSS isn't found, create it.  I'd really like to
> take IEEE80211_IBSS_JOIN_TIMEOUT down to 5 or 7 seconds.  This is only
> the initial IBSS creation, IBSS merging will still be in effect.  I
> simply thing 20 seconds is really too long here.

Yeah, I don't know why it is that long. Jouni, do you remember maybe?
I'm ok with reducing it.

> 3) doesn't send NULL SIOCGIWAP disassoc events when the device goes down
> or the module is removed.  Where's the best place to put the event on
> module remove?

Huh? Why does that matter, the network interface is going away so...?

> 4) Is the association expected to survive a up->down->up sequence?  If
> not, then we should be sending NULL SIOCGIWAP event whenever dev_close()
> gets called.

No, it's not, yes, we probably should send that event somewhere. Is it
ok to send the event while not associated?

> 5) mac80211 requires the device to be down when changing modes.  That's
> fine; but requires a patch to wpa_supplicant to handle this.  This would
> cause failures when switching AP that were different modes from NM.
> See:
> 
> http://lists.shmoo.com/pipermail/hostap/2008-June/017894.html

Don't understand. How can you switch to an IBSS AP? :)

It's probably fairly easy to remove this restriction because they all
use ieee80211_if_sta internally (sta, ibss, mesh) but since I don't care
too much about IBSS and see mesh as being quite different, I have no
motivation to try (and test) this.

johannes

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]