You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The the geteduroam app for iOS didn't configure all the rcoi for passpoint. It only configured the first RCOI found in the eap-config file.
It should also configure the all the rcoi... otherwise user may not able to connect to OpenRoaming network as most of the ANP doesn't broacast eduroam's RCOI.
Thank you
The text was updated successfully, but these errors were encountered:
I used both eduroamCAT and letswifi-portal to generate the .eap-config file. Both were showing the same behavior.
This is the environment when I tested it:
SSID: OpenRoaming (broadcasting eduroam, OR and Cisco legacy RCOI)
SSID: OpenRoaming.dev (broadcasting OR RCOI)
When I used the the .eap-config file generated by the eduroamCAT (RCOI order eduroam, OR, OR education) , only OpenRoaming SSID appeared (in My Networks list). When I used the .eap-config file generated by the Letswifi portal (RCOI order OR,cisco legacy,eduroam) both OpenRoaming and OpenRoaming.dev appeared.
For comparison, I used .mobileconfig file generated by the eduroamCAT and letswifi-portal (the RCOI order is the same as the .eap-config file); the result: both SSIDs appeared in My Networks list regardless which .mobileconfig file I use (I used the .mobileconfig file one at a time).
Based on this finding, I assumed that the geteduroam app only configured the first RCOI only; otherwise it should shows the same result as the .mobileconfig file.
I hope this answer your question. Please let me know if you want me to do some more tests.
Hi,
The the geteduroam app for iOS didn't configure all the rcoi for passpoint. It only configured the first RCOI found in the eap-config file.
It should also configure the all the rcoi... otherwise user may not able to connect to OpenRoaming network as most of the ANP doesn't broacast eduroam's RCOI.
Thank you
The text was updated successfully, but these errors were encountered: