P2P: Include P2P IE in (Re)AssocReq to infra AP if it uses P2P IE
While this is not strictly speaking required by the P2P specification for a not-P2P Managed Device, this can provide useful information for the P2P manager AP and may be needed to pass certification tests.
This commit is contained in:
parent
5be5305b7e
commit
4c08c0bd57
6 changed files with 24 additions and 16 deletions
|
@ -1142,10 +1142,11 @@ int p2p_scan_result_text(const u8 *ies, size_t ies_len, char *buf, char *end);
|
|||
* @buf: Buffer for writing the P2P IE
|
||||
* @len: Maximum buf length in octets
|
||||
* @p2p_group: Whether this is for association with a P2P GO
|
||||
* @p2p_ie: Reassembled P2P IE data from scan results or %NULL if none
|
||||
* Returns: Number of octets written into buf or -1 on failure
|
||||
*/
|
||||
int p2p_assoc_req_ie(struct p2p_data *p2p, const u8 *bssid, u8 *buf,
|
||||
size_t len, int p2p_group);
|
||||
size_t len, int p2p_group, struct wpabuf *p2p_ie);
|
||||
|
||||
/**
|
||||
* p2p_scan_ie - Build P2P IE for Probe Request
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue