How does WiNG Captive Portal (RADIUS) authentication work with locally bridged (self) mode and external captive portal web pages?

[Jeff_Lanza]

I'm operating a WiNG wireless controller to manage remote APs. I'm attempting to setup external captive portal pages, and in order to have the APs handle the captive portal capture and redirection process (and RADIUS authentication) without tunneling traffic through the controller.

So far, the setup works as expected, clients are getting redirected to the proper captive portal page by the AP.

The first question is, once the external pages perform their auth processes,
1) How does the authentication form submission work on the AP (or does it) in this configuration?

I'm currently testing form submission (POST) with these two endpoints:

https://1.1.1.1:444/cgi-bin/hslogin.cgi
http://1.1.1.1:880/cgi-bin/hslogin.cgi

and these parameters:
f_user =
f_pass =
f_Qv =
f_hs_server = 1.1.1.1

2) Is the script at 1.1.1.1 served by the AP, or is that supposed to supposed to be the controller?

3) Can I post to 880 when in http redirection mode and https mode or at all?

[Cristiano_Bevil]

Thanks! You helped me a lot understanding the situation!

[Cristiano_Bevil]

I'm using Centralized Controller mode.

[Jeff_Lanza1]

What mode are you using for the Captive Portal:
Internal(self)
Centralized
or Centralized Controller

see notes above.

[Cristiano_Bevil]

Thanks for your answer, Jeff.
In the case we have an AP managed by a controller, what would be 1.1.1.1?
Thanks in advance.

[Jeff_Lanza1]

The AP has a web server in 'self' mode that serves an unencrypted page to accept authentication requests at 1.1.1.1 over port 880. SSL requests would happen over port 444. I can't speak to the details of the web server on the AP that handles redirects to external captive portal pages.