On Mon, Apr 24, 2006 at 03:01:48PM +0200, Jiri Benc wrote: > On Fri, 21 Apr 2006 19:44:31 -0700, Jouni Malinen wrote: > > On Fri, Apr 21, 2006 at 10:53:28PM +0200, Jiri Benc wrote: > > > Default management interface (wlanXap) confuses users. It is only needed > > > for > > > AP mode (and only until interfaces are converted to use native 802.11 > > > frames). > > > > Or when using user space MLME in client mode which is something that I > > just got working as far as scanning and association is concerned. In > > other words, wpa_supplicant will be needing this interface.. > > I think we can (and should) wait with userspace MLME until the netlink > interface is implemented. > > > That sounds like something that could break multi-BSSID/SSID aware > > hostapd. Are you saying that there would be new wlanXap like interface > > for each BSS/VLAN interface? What are the problems this is fixing with > > multiple AP interfaces? > > Thinking about it more, only implementation problems. I was just lazy > and implementing things the way I did seemed to be easier. My fault, > sorry, didn't realize hostapd is aware of multiple BSSes. > > > So far, hostapd has been responsible for > > receiving all management from a single interface and then internally > > decide which BSS/multi-SSID entry to use for each. > > > > I would assume that hostapd could be changed to process frames from > > multiple interfaces (at least if this is only for multi-BSSID, not for > > multi-SSID/VLAN case). > > There is no point in changing hostapd as this solution is temporary only > and hostapd will need to be changed for netlink anyway. > > I will fix the patch.
I'm going to skip this patch for now. I'll merge the rest. John -- John W. Linville [EMAIL PROTECTED] - 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
