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

Masashi Honma masashi.honma
Tue Jun 5 08:10:35 PDT 2012


Hello.

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.

diff --git a/src/p2p/p2p_group.c b/src/p2p/p2p_group.c
index 44b387a..d3373bf 100644
--- a/src/p2p/p2p_group.c
+++ b/src/p2p/p2p_group.c
@@ -140,6 +140,8 @@ static void p2p_group_add_common_ies(struct
p2p_group *group,
 	/* P2P Capability */
 	dev_capab |= P2P_DEV_CAPAB_SERVICE_DISCOVERY;
 	dev_capab |= P2P_DEV_CAPAB_INVITATION_PROCEDURE;
+	if (group->p2p->cfg->concurrent_operations)
+		dev_capab |= P2P_DEV_CAPAB_CONCURRENT_OPER;
 	group_capab |= P2P_GROUP_CAPAB_GROUP_OWNER;
 	if (group->cfg->persistent_group) {
 		group_capab |= P2P_GROUP_CAPAB_PERSISTENT_GROUP;


Regards, Masashi Honma.



More information about the Hostap mailing list