[RFC 2/2] driver_nl80211: use nl80211 p2p interface types

Jouni Malinen j
Tue Feb 1 06:46:56 PST 2011

On Tue, Feb 01, 2011 at 04:22:11PM +0200, Jouni Malinen wrote:
> But this was not covered.. At this point, we should not really trigger
> the hostapd scan on P2P GO interface since we do not enable HT40. As far
> as P2P search is concerned, I do not really want to do it by changing
> the interface type and hopefully we can address this by moving to using
> a separate vif for P2P group (and alternatively, by enabling AP/P2P GO
> type interface to run through the scan).

Actually, mac80211 has already been modified to allow that scan before
beaconing is configured on AP interface (and will soon allow that with
P2P GO vif, too).

> For the HT40 case where AP will need to run a scan before enabling the
> interface, it would be useful to maintain that functionality for P2P,
> too, once we start enabling HT40 at some point. This requires changes to
> the P2P channel negotiation (new operating class). If someone is willing
> to rebase this part of the patch on top of the current hostap.git
> version, it would be useful to get this addressed so that both the AP
> and P2P GO iftypes have similar behavior and that they will end up
> restoring the previous iftype after the scan properly.

The HT40 with P2P case should actually be covered now because the scan
is done prior to configuring beaconing. The only remaining case would be
p2p_find on a P2P GO interface when not using separate vif for P2P
Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list