aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/hs20_supplicant.h
Commit message (Collapse)AuthorAgeFilesLines
* HS 2.0: As a STA, do not indicate release number greater than the APJouni Malinen2018-12-081-1/+3
| | | | | | | | | | Hotspot 2.0 tech spec mandates mobile device to not indicate a release number that is greater than the release number advertised by the AP. Add this constraint to the HS 2.0 Indication element when adding this into (Re)Association Request frame. The element in the Probe Request frame continues to show the station's latest supported release number. Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
* HS 2.0: Process received Terms and Conditions Acceptance notificationJouni Malinen2018-04-231-0/+1
| | | | | | | | | | Extend wpa_supplicant WNM-Notification RX handling to parse and process received Terms and Conditions Acceptance notifications. If PMF is enabled for the association, this frame results in control interface indication (HS20-T-C-ACCEPTANCE <URL>) to get upper layers to guide the user through the required acceptance steps. Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
* HS 2.0: Add Roaming Consortium Selection element into AssocReqJouni Malinen2018-04-171-0/+2
| | | | | | | | This makes wpa_supplicant add Hotspot 2.0 Roaming Consortium Selection element into (Re)Association Request frames if the network profile includes roaming_consortium_selection parameter. Signed-off-by: Jouni Malinen <jouni@codeaurora.org>
* HS 2.0: Add optional no-scan parameter to FETCH_OSUJouni Malinen2016-07-121-1/+1
| | | | | | | | This is mainly for testing purposes to allow multiple FETCH_OSU ANQP operations to be ran without having to wait for full scan between each query. Signed-off-by: Jouni Malinen <j@w1.fi>
* HS 2.0: Make hs20_build_anqp_req() staticJouni Malinen2016-07-111-2/+0
| | | | | | This function is not used outside hs20_supplicant.c. Signed-off-by: Jouni Malinen <j@w1.fi>
* HS 2.0: Add support for configuring frame filtersMatti Gottlieb2016-04-081-0/+1
| | | | | | | | | | | | | | | When a station starts an association to a Hotspot 2.0 network, request the driver to do the following, based on the BSS capabilities: 1. Enable gratuitous ARP filtering 2. Enable unsolicited Neighbor Advertisement filtering 3. Enable unicast IP packet encrypted with GTK filtering if DGAF disabled bit is zero Clear the filter configuration when the station interface is disassociated. Signed-off-by: Matti Gottlieb <matti.gottlieb@intel.com>
* HS 2.0: Convert icon storage to use dl_listJouni Malinen2015-12-191-0/+1
| | | | | | This simplifies the list operations quite a bit. Signed-off-by: Jouni Malinen <j@w1.fi>
* HS 2.0: Add a command to retrieve icon with in-memory storageJan Nordqvist2015-12-191-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a new command based Hotspot 2.0 icon retrieval option. In short, here is the new command sequence: 1. REQ_HS20_ICON <bssid> <file-name> 2. event: RX-HS20-ICON <bssid> <file-name> <size> 3. GET_HS20_ICON <bssid> <file-name> <offset> <size> (if needed, repeat with larger offset values until full icon is fetched) 5. DEL_HS20_ICON <bssid> <file-name> REQ_HS20_ICON is a new command that is analogous to HS20_ICON_REQUEST with the slight difference that an entry to store the icon in memory is prepared. The RX-HS20-ICON event has been augmented with BSSID, file-name and size, and GET_HS20_ICON is used to retrieve a chunk of up to <size> bytes of icon data at offset <offset>. Each chunk is returned as a base64 encoded fragment, preceded by "HS20-ICON-DATA", BSSID, and file-name as well as the starting offset of the data. If there is no entry prepared for the icon when the ANQP result comes back, hs20_process_icon_binary_file falls back to legacy behavior. Finally the DEL_HS20_ICON command deletes (all) icons associated with BSSID and file-name (there could be several if retries are used and they have different dialog tokens). Signed-off-by: Jan Nordqvist <jannq@google.com>
* HS 2.0: Try to use same BSS entry for storing GAS resultsJouni Malinen2015-01-171-1/+2
| | | | | | | | | | | | | | Commit 17b8995cf5813d7c027cd7a6884700e791d72392 ('Interworking: Try to use same BSS entry for storing GAS results') added a mechanism to try to pair GAS request and response to a single BSS entry to cover cases where multiple BSS entries may exists for the same BSSID. However, that commit did not cover the Hotspot 2.0 ANQP elements. Extend this mechanism to all ANQP elements. This can help in cases where information in the Hotspot 2.0 specific ANQP elements got lost if a hidden SSID or some other reason of duplicated BSS entries was present while doing ANQP fetches. Signed-off-by: Jouni Malinen <j@w1.fi>
* Remove leftover timeouts on cleanupAlexandru Costache2014-05-121-0/+1
| | | | Signed-off-by: Alexandru Costache <alexandru.costache.100@gmail.com>
* HS 2.0: Extend ANQP_GET to accept Hotspot 2.0 subtypesDmitry Shmidt2014-03-251-0/+2
| | | | | | | | | | | | | This allows a single ANQP query to be used to fetch both IEEE 802.11 defined ANQP elements and Hotspot 2.0 vendor specific elements. ANQP_GET <addr> <info id>[,<info id>]... [,hs20:<subtype>][...,hs20:<subtype>] For example: ANQP_GET 00:11:22:33:44:55:66 258,268,hs20:3,hs20:4 Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
* HS 2.0R2: Try to scan multiple times for OSU providersJouni Malinen2014-02-251-0/+1
| | | | | | | Scan operation is not that reliable, so try couple of times if no OSU provider matches are found during fetch_osu command. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0R2: Add routine for fetching OSU provider informationJouni Malinen2014-02-251-1/+9
| | | | | | | | | The new wpa_cli fetch_osu command can be used to fetch information about all OSU providers and write that to a text file with the icons in separate files. cancel_osu_fetch command can be used to stop ongoing OSU provider list fetch. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0R2: Add STA support for Deauthentication Request notificationJouni Malinen2014-02-251-0/+2
| | | | | | | If requested, disable the network based on the HS 2.0 deauthentication request. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0R2: Add WNM-Notification Request for Subscription RemediationJouni Malinen2014-02-251-0/+3
| | | | | | | | Subscription remediation notification WNM-Notification Request is now shown in the following way in wpa_supplicant control interface: <3>HS20-SUBSCRIPTION-REMEDIATION http://example.com/foo/ Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0R2: Update Indication element to Release 2Jouni Malinen2014-02-251-1/+2
| | | | | | | | | | | | The HS 2.0 Indication element from wpa_supplicant now includes the release number field and wpa_supplicant shows the release number of the AP in STATUS command (hs20=1 replaced with hs20=<release>). The new update_identifier field in the cred block can now be used to configure the PPS MO ID so that wpa_supplicant adds it to the Indication element in Association Request frames. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0: Include HS 2.0 Indication element only for HS 2.0 associationJouni Malinen2013-05-051-0/+2
| | | | | | | | | | | | | The Hotspot 2.0 specification seems to mandate this element to be included in all (Re)Association Request frames if the station is Hotspot 2.0 capable. However, that results in conflicts with other requirements like no TKIP use when this element is present. The design is really supposed to include the indication element only for Hotspot 2.0 associations regardless of what the current specification implies. Remove the HS 2.0 Indication element from (Re)Association Request frame whenever the connection is not for Hotspot 2.0 purposes. Signed-hostap: Jouni Malinen <j@w1.fi>
* HS 2.0: Add Hotspot 2.0 indication into Probe RequestJay Katabathuni2012-05-081-0/+2
| | | | Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* HS 2.0: Add Hotspot 2.0 ANQP routinesJay Katabathuni2012-05-081-0/+18
Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>