Feature req: Passpoint 2.0

We want to enable passpoint 2.0 support. this to support OpenRoaming on Alta Lab. But this is not configurable in the current release.

I don’t use UBT because they no longer support Passpoint-enabled networks, and Passpoint 2.0 is not configurable in here also.

Thanks

Welcome to the community :slight_smile:

thanks!

Welcome! Did you check their Certified Partners list? We’re on there, support is present as of 2.0q+.

That said, the settings aren’t exposed in the controller directly (whether cloud or on-prem). Setting it up does require inputting the config in json format in the Power-User section on a per-SSID basis.

The configuration will vary depending on the RADIUS server in use.

You can register a profile with WBA to test against their RADIUS server by going HERE. Power-user settings are found within SSID settings, under Advanced>Power-User. Once you enable the toggle there will be an text box for input. The config below should work with OpenRoaming.

{
"hostapd": "
  hs20=1
  disable_dgaf=1
  hs20_oper_friendly_name=eng:JR1
  interworking=1
  access_network_type=3
  internet=1
  roaming_consortium=5A03BA0000
  radius_acct_interim_interval=300
  venue_name=eng:WBA
"
}

We will be creating a KB article soon so that this is publicly documented.

1 Like

Curious tbh, what’s the purpose of this? Is it even worth it for home users?

Thanks and I’m surprised about the fast reply. I like it :slight_smile:
I saw you guys on there that’s why I came to Alta Labs. But this is awesome!

I need a minimum 3 consortiums. And what will be the parameter syntax then?

roaming_consortium=5A03BA0000, 5A03BA0000 or something else?

We always need to add 004096 to have the Cisco OpenRoaming app working out of the box.

Can you maybe give a whole list of parameters and syntax, I will be able to set using the power user field regarding passpoint?

These we usually set:
NAI realm / domain name I don’t have that at my home (where this IE frame sample is from):

Thanks!

1 Like

No, but for residents, small schools, and hotspots, retail, restaurants locations absolutely. No one wants portal pain, just connect and go, seamlessly between mobile and WiFi.

Isn’t this home use?

I’m from the UK so could be different names :slight_smile:

1 Like

ah, I mean more hotels… Or buildings where the owner offers Wi-Fi in the lobby, but also optional as a service for the residents in their apartments

Ah fair enough, can you even signup as a home lol probs not worth it tbh

No problem! So it’s actually just hostapd parameters, they’ve got a great doc on that which you can find HERE.

Based on the doc it would be entered 3+ times, separate lines. I’ve highlighted the exact snippet specific to roaming_consortium, found below. NAI Realm, and other options are also present. Input format is simple, one variable per line, between the opening and closing quotes.

Hope that helps. This probably will lead to more questions, so please don’t hesitate to ask!

# Roaming Consortium List
# Arbitrary number of Roaming Consortium OIs can be configured with each line
# adding a new OI to the list. The first three entries are available through
# Beacon and Probe Response frames. Any additional entry will be available only
# through ANQP queries. Each OI is between 3 and 15 octets and is configured as
# a hexstring.
#roaming_consortium=021122
#roaming_consortium=2233445566
3 Likes

Okay, I tested this end-to-end with a real passpoint 2.0 production network and I can confirm this is working with the exact config as above including the quotation.

Used Equipment

AP6-PRO 2.0w
HW controller 1.0g

Device connect successfully:

The correct ie are passed into the beacons.


Cheers!

1 Like