Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Vendors that do support Hotspot 2.0 are Aruba, Meraki and , Cisco (obviously) Ciscoand Ubiquiti. This list is not exclusive. We know that some vendors are categorically not supporting Hotspot 2.0

Some vendors only make Hotspot 2.0 features available on request. One example is Meraki, where you must contact support through the Meraki online management portal to request that Hotspot 2.0 is enabled. 

...

  • Third-party hotspots which are onboarded in the OpenRoaming ecosystem by a third party need to take no further action. An OpenRoaming ANP uses the normal NAPTR discovery for users from an eduroam realm. This means that eduroam IdPs will need to publish a NAPTR record (see further down) and have it point to an eduroam ↔ OpenRoaming ANP proxy. (eduroam OT provides one such proxy for all eduroam participants; eduroam NROs may provide their own for their own institutional user base).
  • Existing eduroam hotspots wishing to make use of eduroam infrastructure as their OpenRoaming uplink provider currently need to connect the Wi-Fi network that has these RCOIs to a proxy run by the eduroam OT Ops Team - contact points for this are Paul Dekkers and Stefan Winter.
  • If you intend to be an ANP, depending on your network access provision conditions, you may need to arrange for additional network provision that allows you to route network traffic that does not comply with your existing provision conditions. For example, organisations receiving network access through the UK JANET network must ensure that non-research/educational users are not routed over the existing network connection, but via separate network access (such as a broadband connection from a commercial provider).

Access Point Configuration examples

  • Also, if you intend to be an ANP, you must forward accounting requests to your uplink, and they are required to send those on to the identity provider. 

Optional mobile network wireless offload

Mobile networks can use OpenRoaming to off-load wireless activity. Currently, only a very limited number of mobile carriers on the planet support this option. This ability is configured using the MCC/MNC Passpoint 2.0 options. The values for the MCC and MNC values can usually be derived from the '@wlan.mncXXX.mccYYY.3gppnetwork.org' username you can see on a network, any 0 prefix can be dropped. AT&T for example has two pairs, '310 280' and '310 410', while T-Mobile USA has one: '310 260'. The planet's MCC and MNC values can be looked up at https://mcc-mnc.net/

To date we are aware that in the US, AT&T and T-Mobile configure their SIMs to use OpenRoaming if their MCC/MNC pair is advertised, but we're also aware that Swisscom also potentially supports this. If you have a Swisscom phone, please let us know whether you can make this work!

Access Point Configuration examples

The configuration snippets that enable OpenRoaming with the "OpenRoaming All" and an uplink to the The configuration snippets that enable OpenRoaming with the "OpenRoaming All" and an uplink to the eduroam OT proxy are on the following pages:

...

FortiWiFi or FortiAP

Meraki OpenRoaming configuration snippet (cloud controller managed)

Ubiquiti UniFi OpenRoaming (Network controller managed)

eduroam SPs

Beacon Settings

...