On Wed, 3 May 2006 11:35:24 -0700, Jouni Malinen wrote: > I think it would be nice to get this in so that both client and AP modes > can use the same mechanism (user space MLME); hostapd already needs this > wmaster0ap interface. In other words, if we do not want to see that > interface by default, we could just add a generic mechanism for > registering wmaster0ap that both hostapd and wpa_supplicant could use. > The Host AP driver (driver/net/wireless/hostap) is doing this with > PRISM2_PARAM_HOSTAPD parameter. I don't care how it's done, but some > simple mechanism would be preferred.
Ok. So what about PRISM2_HOSTAPD_MGMT_IF ioctl that will add management interface (if not added yet) and return its ifindex? It would accept a boolean parameter (like PRISM2_PARAM_HOSTAPD) to add/remove that interface. If you agree with this, I will make a patch. Of course, both hostapd and wpa_supplicant needs to be changed for that. This should not be a problem now as the d80211 stack is not in a common use yet. > No, move of MLME to user space should not change this at all. As an > example, wpa_supplicant supports both cases and the patch I'm working on > for getting Prism2 (full MAC for client mode) working with d80211 is > modifying the kernel side to allow this to be done. Both changes are > touching the same areas in the code, but there is no major change in > whether fullmac can be supported or not. So wpa_supplicant needs to know if the card is softmac or fullmac and behave accordingly, right? > That is not up-to-date with wireless-dev.git anymore, though. The key > patch is d80211_fullmac_client.diff which is small enough to include > here. Please note that this is not yet complete, so consider it more an > example on what type of changes are needed. Oh, thanks, now I remember, I have seen that. Thanks, Jiri -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html