topic wlc redirection in Wireless

wlc redirection

mbeena-kp — Mon, 05 Jul 2021 11:06:44 GMT

Hi,

I can see redirect url has created on the wlc "https://isetest.test.com:8446/portal/gateway?sessionId=0a007c0a562357510001566e&portal=27963fb0-e96e-11e4-a30a-005056bf01c9&action=cwa&token=9dfdf8
where iseservername.test.com is fqdn for the ise server .

But on the client browser if we type hp.com it wont transfer any traffic meaning it won't redirect .
I did packet capture on the client and i cound not see that client even t send a request to resolve the "iseservername.test.com"

i have permitted port 53 in the access list .

Thanks

Refer the link : http://www

mohanak — Mon, 19 Oct 2015 09:27:42 GMT

Refer the link : http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wlan-security/115951-web-auth-wlc-guide-00.html#anc27

Hi ,Is there something for

mbeena-kp — Tue, 20 Oct 2015 06:33:46 GMT

Hi ,

Is there something for AIR-CT5760

https://ise-server:8446/portal/gateway?sessionId=0a007c0a5625d5d5000099c6&portal=27963fb0-e96e-11e4-a30a-005056bf01c9&action=cwa&token=0bdd929bc68fb6f59908e32ed958095d

" Redirection Issue

There is a variable within the HTML bundle that allows the redirection. Do not put your forced redirection URL there. For any redirection issues in custom WebAuth, Cisco recommends to check the bundle. If you enter a redirect URL with += in the WLC GUI, this could overwrite or add to the URL defined inside the bundle. For example, in the WLC GUI, the redirectURL field is set to www.cisco.com; however, in the bundle it shows: redirectURL+= 'www.google.com'. The += redirects users to www.cisco.comwww.google.com, which is an invalid URL. "

below is the redirect url parameter value found on the wlc for the paricular client .

https://ise-server:8446/portal/gateway?sessionId=0a007c0a5625d5d5000099c6&portal=27963fb0-e96e-11e4-a30a-005056bf01c9&action=cwa&token=0bdd929bc68fb6f59908e32ed958095d

And i verified the following
---------------------------------------

a valid DNS server has been assigned to the client via DHCP (ipconfig /all)?
YES

that the DNS is reachable from the client (nslookup<www.website.com>)
YES

that the user entered a valid URL in order to be redirected
YES

reach ability to the ise server ?

yes

Thanks