
Wireless Client Connections |
33
Name
Server
Port
Url
Auth Text
Redirect Url
Server Fail
Through
Disable Auto Whitelist
Use HTTPs
In Use
Redirect Mode
----
------
----
---
---------
------------
------------
-------
----------------------
---------
------
-------------
default
10.64.18.200
80
/guest/bmrpl.php
Disable
Enable
No
No
Yes
bwang1
10.64.18.200
80
/guest/bmrpl.php
Disable
Enable
No
Yes
Yes
"a a a a a"
10.64.18.200
80
/guest/bmrpl.php
Disable
Disable
No
Yes
No
amigoport
10.64.17.246
80
/aruba.php
Disable
Enable
No
No
Yes
bwang2
10.64.18.200
80
/
Disable
Enable
No
No
Yes
bwang3
10.64.18.200
80
/
Disable
Enable
No
No
Yes
Networks using ECP redirect mode are marked
Yes
in the
Redirect Mode
column and networks using
ECP tinyproxy mode are marked
No
.
Debug ECP Mode Behavior on Client PC
Check if the client is redirected to the expected URL as defined by the captive portal ECP mode using
developer tools provided by the browser.
The following procedure describes how to debug captive portal communication between the client and the
webserver on the client browser:
1. Open
Developer Tools
in your browser and navigate to
Network Monitor
.
2. Input a URL in the address bar and press
Enter
.
3. Click on the URL entry in the
Network Monitor
and check the header messages exchanged between
the web server and the client. Depending on the ECP mode of the captive portal, you should get the
following responses:
Captive Portal ECP Mode
Expected Header Response
ECP tinyproxy mode
Status Code: 200 OK
Location in Header Response — Aruba AP captive portal URL
(securelogin.arubanetworks.com)
ECP redirect mode
Status Code: 302 OK
Location in Header Response — Captive portal server URL
If the client browser fails to resolve DNS, open command prompt on the client PC and run
nslookup
to
check the status of DNS server.
Wireless Client Fails Captive Portal Authentication
Captive portal authentication on ECP tinyproxy mode is mediated by the AP and can be troubleshooted on
the AP. Whereas captive portal authentication on ECP redirect mode has no AP mediation and can be
troubleshooted only using a packet capture software.
The following procedure describes how to troubleshoot issues, if the client fails captive portal
authentication on ECP tinyproxy mode:
Check Authentication Process Logs on the AP