Monitor interface for P2P

Jouni Malinen j
Thu May 26 14:08:20 PDT 2011

On Thu, May 26, 2011 at 10:44:48AM -0700, Ecco (Inhyang) Park wrote:
> > What do you mean with "p2p interface" and how would you receive (and
> > send) management frames using it?
> I mean p2p-eth0-x for p2p virtual interface.
> We can receive management frames using NL80211_CMD_FRAME, but need to modify some codes in driver_nl80211.c

OK, that sounds fine. I would assume this would be used only for P2P
Action frames in that specific group while other P2P (Public) Action
frames would be delivered similarly on the first interface (eth0 in this
case?). Frames to (and from) both the P2P Device Address and one or more
P2P Interface Addresses could be received/sent when a group is running.

> Yes, I already comment out in wpa_driver_nl80211_hapd_send_eapol to prevent sending EAPOL frame through monitor interface.
> Instead of that, we can use p2p virtual interface(p2p-eth0-x) for sending EAPOL frame.

OK. Though, this needs to be done dynamically at runtime based on driver

> Do you mean that we need driver capability in cfg80211 to check whether the driver support monitor interface or not ?

Yes, or well, some other flag indicating that monitor mode is not needed
in AP mode would probably be better way of handling this. In other
words, if this new flag is not indicated, the old mechanism (monitor
mode) will be used. If it is indicated, nl80211 commands would be used

> In my opinion, we can define some flags like MONITOR_SUPPORT  in Makefile of wpa_supplicant to check monitor capability at compile time.

No, that's not acceptable. The same binary needs to work both with
drivers that use monitor interface and with drivers that don't.

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list