topic ISE - iPhone/iPad in Network Access Control

ISE - iPhone/iPad

Mikael Gustafsson — Mon, 11 Mar 2019 02:38:58 GMT

Hi,

Im working on my CWA WebAuth for guest access and I have tested a windows PC, a OS X, iPhone and iPad.

But I get this redirect problem after the endpoint has authenticated once and it get profiled, MAC address added to the Endpoint list

When I try connect, after a client reboot and disconect client in the WLC, I get redirected to the guest portal page, I put in my credentials and get access granted.

After that the device get profiled and show up under Endpoints I now get a network error when I try to make a new connection, disconecting clients in WLC and a client reboot. If I wait to long with my credentials the MAC address gets in to the Endpoint list and it stops woking..

If I remove MAC addresses from the Endpoint list it work again, without reboot/WLC disconect client.

My policy is rather simple

Authentication Policy:

-Wireless-MAB allowed protocols Default and use internal users - If user not found Continue

Authorization Policy:

-If Guest and Wireless MAB then Gurst_acl (allow all acl, any-any)

-Default if no match then Wireless-CWA (redirect and acl for dns and ise portal)

Why is it behaving like this, I need profiling later on so it wold be nice to have it going.

Thanks

ISE - iPhone/iPad

vikasyad — Tue, 28 May 2013 00:20:26 GMT

There is no issues with the policies, It looks fine. Please review the below link which might be helpful:

http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns742/ns744/docs/howto_61_byod_provisioning.pdf

http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bba10d.shtml

ISE - iPhone/iPad

myanznki — Fri, 05 Jul 2013 07:26:36 GMT

can you post the error message ?

on what device that error happen ???

ISE - iPhone/iPad

Mikael Gustafsson — Fri, 05 Jul 2013 08:19:41 GMT

Hi,

If I remember right , this was the old wireless guest solution for that customer that hijacked and redirected some of the sessions going out. The wierd thing was that Mac and PC did not have any problems, iOS devices some, 50%, and Android no connection at all.

When we found out that what it was and turnd of that interface everything worked.

Cheers.