Hi, We have an ongoing issue which is holding up the deployment of a customer project, in that the guest splash page configured on ISE does not work on IOS devices, it works fine on Android and Windows based PCs.
When the IOS devices join the Guest WI-Fi, they obtain an ip from the guest vlan, the mini browser then pops up for the redirect but then nothing happens further on the device, just blank screen.
ISE Version 3.0 (Patch 7)
Meraki AP 29.5.1
The configuration applied to the ISE and Meraki networks, for the deployment is as per the Meraki configuration guide:
CWA - Central Web Authentication with Cisco ISE - Cisco Meraki
We have also attempted the work around by adding the additional URLS into the walled garden to disable the CNA.
However nothing works.
As a last resort, we opened both TAC cases with Meraki and CIsco (who have also liaised internally with each other on this) and both state that based on the packet captures conducted from the AP (Wireless and Wired) the coms between the IOS/Meraki AP/ and ISE are all fine - Reposne from Meraki TAC:
As you can see, the client device sends the DNS request for neverssl.com, which is then followed by a redirect DNS for the ISE splash page. The device then communicates with the ISE server, exchanging the certificates and sending a FIN, ACK at the end of the exchange. This is pretty much exactly what we are seeing when the walled garden is setup in the alternative configuration
I have engaged directly with the Cisco TAC engineer for the case that was raised as well. They reached the same conclusion as we did before; we are seeing the full exchange of information between the client and the ISE server from the AP logs. The fact that the client send back a FIN packet indicates that it is done with the transaction and would like to end that TCP stream. When it begins the RADIUS exchange again with an Access-Request, this is completely out of our view and we cannot determine why we are seeing that behaviour from the iPhone.
Therefore, i am at a total loss on this now and so was wondering if anyone else has or as had this issue with IOS devices using the same setup as detailed above. Googling IOS issues with Meraki does reveal that there are similar issues dating back to 2017 which makes me wonder if this solution does actually work in the real world.
Thanks
Scott