[PATCH] P2P: Set Concurrent Operation bit in Beacon/Probe Response

Jouni Malinen j
Tue Jun 5 10:59:30 PDT 2012


On Wed, Jun 06, 2012 at 12:10:35AM +0900, Masashi Honma wrote:
> If the Concurrent Operation is supported by the P2P Device's driver, the
> Concurrent Operation bit in the Device Capability is 1. But when the P2P Device
> will be GO, the Concurrent Operation bit is changed to 0 on Beacon/Probe
> Response. Because p2p_group_add_common_ies() doesn't care the bit. Is there any
> reason for it ?
> 
> If this is a bug, this patch solves this issue.

It looks fine to add this Device Capability into the Beacon/Probe
Response frames from the GO. Could you please re-send the patch with
Signed-hostap: line so that I can apply it? Though, it would likely be
even better to initialize dev_capab to group->p2p->dev_capab in
p2p_group_add_common_ies() to remain consistent with how this is set in
p2p_init().

-- 
Jouni Malinen                                            PGP id EFC895FA



More information about the Hostap mailing list