Fail setting up P2P connection with VHT-80MHz
Blanquicet-Melendez Jose (MM)
jose.blanquicet-melendez at magnetimarelli.com
Wed Aug 24 03:15:30 PDT 2016
Hi,
I am working on a PATCH to enable VHT when setting up an AP mode operation. Looking how it is done for p2p-go, I tried to enable VHT 80MHz for P2P operation but suddenly it did not work appropriately. I used the following configuration from wpa_cli:
p2p_connect XX:XX:XX:XX:XX:XX pbc go_intent=15 freq=5180 max_oper_chwidth=80 ht40 vht
The connection finished successfully but it did not set 80 MHz. I checked it by looking at the IEs of the beacons and I saw that 40 MHz was there. But, in the VHT Operation IE the value for the Channel Width was 0 (20 MHz or 40 MHz operating channel width) instead of 1 (80 MHz).
I had a look at the code for setting 80MHz as channel width and I found that it fails when it checks if all the involved channels are available, in p2p_supplicant.c, wpas_p2p_verify_80mhz(). In particular I noticed that it fails because the channels do not have the flags HOSTAPD_CHAN_VHT_*, they only have HOSTAPD_CHAN_HT40, HOSTAPD_CHAN_HT40PLUS and/or HOSTAPD_CHAN_HT40MINUS. What is the propose of the flags HOSTAPD_CHAN_VHT_*?
Thanks in advance.
Best Regards,
Jose Blanquicet
________________________________
VISITA IL NOSTRO NUOVO SITO WEB! - VISIT OUR NEW WEB SITE! www.magnetimarelli.com
Confidential Notice: This message - including its attachments - may contain proprietary, confidential and/or legally protected information and is intended solely for the use of the designated addressee(s) above. If you are not the intended recipient be aware that any downloading, copying, disclosure, distribution or use of the contents of the above information is strictly prohibited.
If you have received this communication by mistake, please forward the message back to the sender at the email address above, delete the message from all mailboxes and any other electronic storage medium and destroy all copies.
Disclaimer Notice: Internet communications cannot be guaranteed to be safe or error-free. Therefore we do not assure that this message is complete or accurate and we do not accept liability for any errors or omissions in the contents of this message.
More information about the Hostap
mailing list