[PATCH V2 21/23] nl80211: verify P2P-GO/CLIENT address with all interface addresses

Arend van Spriel arend at broadcom.com
Tue Jul 2 10:20:14 EDT 2013


On 07/02/2013 04:18 PM, Johannes Berg wrote:
> On Tue, 2013-07-02 at 16:11 +0200, Arend van Spriel wrote:
>> On 07/02/2013 03:56 PM, Johannes Berg wrote:
>>> On Tue, 2013-07-02 at 15:46 +0200, Arend van Spriel wrote:
>>>
>>>>> An earlier thread  seemed to already imply that some people may believe
>>>>> that this new dedicated P2P_DEVICE is needed for some concurrent P2P
>>>>> operations which is simply not the case; it just adds another option for
>>>>> internal driver/firmware/hardware design which should not add or remove
>>>>> any functionality and the only externally observable difference should
>>>>> be in MAC addresses potentially being different (but even those could be
>>>>> assigned using the same style between P2P_DEVICE and p2p-mgmt-netdev).
>>>>
>>>> The last sentence is confusing to me. To me the P2P_DEVICE is a
>>>> replacing solution to the p2p-mgmt-netdev, right?
>>>
>>> That was never needed either though -- you can do P2P management on
>>> wlan0 (i.e. the BSS client netdev)
>>
>> You mean to say there is no real usage scenario for the P2P Device
>> interface?
>
> No, not really, just that it's not fundamentally necessary if the driver
> works without one.

Phew :-)

Gr. AvS




More information about the HostAP mailing list