HotSpot 2.0
General
Feature is about adding support for HotSpot 2.0 (Wi-Fi Alliance Certified Passpoint) to OpenSync.
Controller has to set up HotSpot 2.0 configuration through Passpoint_Config
table. Then one of the BSS-es have to be configured with Wifi_VIF_Config::passpoint_config
UUID pointing to the entry in Passpoint_Config
table.
Please note, that Key Management (WPA2-EAP, WPA3-EAP, …) and all other BSS (VIF) specific configurations still have to be set in Wifi_VIF_Config
table.
Northbound API
Passpoint_Config |
| Comments |
---|---|---|
enabled | bool reqiured | Enables/disables HotSpot 2.0 and Interworking Elements. Note that it controls HS2.0 for all the VIF’s referring to this row. |
osen | bool | Enables/disables OSU Server-Only Authenticated L2 Encryption Network (deprecated) |
anqp_domain_id | integer [0..65535] | A number within a range of It is mutually exclusive with pps_mo_id! |
pps_mo_id | integer [0..65535] | A number within a range of It is mutually exclusive with anqp_domain_id! |
operator_friendly_name | string max: 16 entries “{3}:{1..252}” | Defines a list of Examples:
|
adv_wan_status | bool reqiured | Sets a value for HotSpot 2.0 ANQP WAN Metrics subelement field named Link Status.
|
adv_wan_symmetric | bool reqiured | Sets a value for HotSpot 2.0 ANQP WAN Metrics subelement field named Symmetric Link.
|
adv_wan_at_capacity | bool reqiured | Sets a value for HotSpot 2.0 ANQP WAN Metrics subelement field named At Capacity.
|
t_c_filename | string | Terms and Conditions filename. BSS adds this value while sending RADIUS Access-Request message so that the AAA server knows which T&C the AP requires its users to accept. |
t_c_timestamp | integer | AP adds this value while sending RADIUS Access-Request message so that the server knows the timestamp of T&C the AP requires its users to accept. Value is an Unix Epoch timestamp of the last T&C file modification. |
osu_ssid | string | SSID of the ESS used for Online Sign-Up (deprecated) |
osu_providers | list of uuid’s | Specifies list of Online Sign-Up Providers. UUID’s in this list refer to the Passpoint_OSU_Providers table entries. This field and referenced table was designed, but never used due to deprecation of the OSU feature. (deprecated) |
|
|
|
access_network_type | integer [0-15] | 0 - Private Network IEEE Std 802.11-2020 table 9-236 |
asra | bool | Controls
|
venue_group | integer [0-255] | Indicate the type of Venue advertised in the Interworking Element e.g.
IEEE Std 802.11-2020 table 9-65. |
venue_type | integer [0-255] | |
hessid | string “xx:xx:xx:xx:xx:xx” where each xx is an 8-bit hexadecimal value {17} required | Homogeneous Extended Service Set Identifier. Specifies the target specific HESSID network identifier or the wildcard network identifier. |
roaming_consortium | list of strings up to 8 RCOIs supported | A list of Roaming Consortium Organization Identifiers to advertise. Note that only 3 values are advertised in Beacon frames. The remaining list is available only through ANQP Query. |
venue_name | list of strings up to 16 values supported {4..255} | Provides zero or more (up to 16) Venue Names associated with BSS. Supplied string must match the format e.g.
|
venue_url | list of strings up to 16 values supported {2..255} | The list of one or more (up to 16) URLs that can be used for web page advertising services or providing information, particular to a venue’s BSS. Field must match the format |
network_auth_type | list of integers [0-255]
| List of Network authentication Type identifiers. # Network Authentication Type Indicator values:
00 = Acceptance of terms and conditions
01 = On-line enrollment supported
02 = http/https redirection
03 = DNS redirection only valid when ASRA is set to IEEE Std 802.11-2020 table 9-332 |
network_auth_t_c_url | string {0-255} | Formatted in accordance to IETF RFC 3986. Specifies a URL to obtain Terms and Conditions if Additional Step Required for Access is |
network_auth_redirect_url | string {0-255} | Formatted in accordance to IETF RFC 3986. Specifies a redirect URL if Additional Step Required for Access is |
domain_name | list of strings up to 16 {2-255} | List of domain names supported for authentication with this AP. It’s defined in accordance to “Preferred Name Syntax” defined in IETF RFC 1035. |
list_3gpp | list of strings up to 64 {2-15} | Corresponds to 3GPP Cellular Network ANQP-element values. Each entry is a Mobile Country Code (MCC) and Mobile Network Code (MNC) pair in |
nairealm_list | list of strings up to 64 {2-64} | A list of network access identifier (NAI) realms corresponding to Service Providers or other entities whose networks or services are accessible via this AP. encoding:
Example:
EAP methods (for this context) are defined in table |
anqp_elem | string {1-1024} | Used for testing! Any arbitrary ANQP element can be added using syntax ANQP Element ID’s are defined in Table 9-331 of IEEE Std 802.11-2020. |
Southbound API
Feature uses hostapd daemon with nl80211 driver to configure parameters of HotSpot2.0 included in Beacons, Probe Req/Res and ANQP messages.
Implementation follows closely an interface defined by hostapd so for further guidance please refer to hostap's official Git repository.
Implementation errata for Broadcom
Broadcom platforms have to be treated with a special attention, because BCM proprietary driver does not support nl80211 configuration interface that allows setting up ANQP parameters. Instead Broadcom delivers a proprietary binary that reads parameters from nvram memory, attaches itself to wireless interface, intercepts ANQP requests and responds to requestors. Additionally it adds required parameters to management frames, so HotSpot 2.0 configuration has to be removed from hostapd configuration file (if used), otherwise Beacon frame will contain a HotSpot 2.0 Indication IE twice.
Broadcom support comes with OpenSync 6.4.2 version.
Requirements
No special attention is needed while using OpenSync 6.4 native implementation of HotSpot 2.0 on platforms that fill below requirements:
use hostapd to construct IEEE802.11u Information Elements in Beacon frames e.g.
Interworking IE
Advertisment Protocol IE
Roaming Consortium IE
use hostapd to add Wi-Fi Alliance’s Vendor Specific HotSpot 2.0 Indication Element
support ANQP elements defined in Passpoint Specification v3.3 in the Wi-Fi driver
Remarks for integration:
Customers need to use their own RADIUS/AAA infrastructure and tools for generating HotSpot 2.0 end-device configuration profiles.
Any additional network configuration control e.g. network zones, traffic separation, throughput throttling etc. is not a subject of HotSpot2.0 configuration.
Limited security features support with HotSpot 2.0