aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/README-P2P
diff options
context:
space:
mode:
authorJithu Jance <jithu@broadcom.com>2014-02-20 11:43:25 (GMT)
committerJouni Malinen <j@w1.fi>2014-02-20 14:32:12 (GMT)
commitf667e031c960b45eb836d1cc983371f895abd3c2 (patch)
treea2ec7e79440cbedfcc6a5eaa133dc691943f43be /wpa_supplicant/README-P2P
parente9a6f18385e67c29d3c7921d0a502f630a364fa2 (diff)
downloadhostap-f667e031c960b45eb836d1cc983371f895abd3c2.zip
hostap-f667e031c960b45eb836d1cc983371f895abd3c2.tar.gz
hostap-f667e031c960b45eb836d1cc983371f895abd3c2.tar.bz2
P2P: Address few issues seen with P2P SD
Suppose we have multiple peers and we have peers advertising SD capability, but no services registered for advertising. In this case, even if there are multiple broadcast queries set, we might end up sending only the lastly added broadcast query to the same device (since SD_INFO won't get set for the first broadcast query). Add support for multiple wildcard queries to be tracked to enable this type of use case. Some times it is seen that before advancing to next device in the list, the scan results come and update SD_SCHEDULE flag. This will result in sending the already sent query to the same device without giving chance to other devices. This issue again is seen with peer devices advertising SD capability without any services registered. Signed-off-by: Jithu Jance <jithu@broadcom.com>
Diffstat (limited to 'wpa_supplicant/README-P2P')
-rw-r--r--wpa_supplicant/README-P2P5
1 files changed, 2 insertions, 3 deletions
diff --git a/wpa_supplicant/README-P2P b/wpa_supplicant/README-P2P
index 7354bbf..bfad501 100644
--- a/wpa_supplicant/README-P2P
+++ b/wpa_supplicant/README-P2P
@@ -230,9 +230,8 @@ discovery protocols and requests this to be sent to all discovered
peers (note: this can result in long response frames). The pending
requests are sent during device discovery (see p2p_find).
-Only a single pending wildcard query is supported, but there can be
-multiple pending peer device specific queries (each will be sent in
-sequence whenever the peer is found).
+There can be multiple pending peer device specific queries (each will be
+sent in sequence whenever the peer is found).
This command returns an identifier for the pending query (e.g.,
"1f77628") that can be used to cancel the request. Directed requests