Captive portal redirection issues at 5.9.2

[Vedran_Jurak]

Hi all,

Recently upgraded some sites to 5.9.2. Clients started complaining they are unable to login in the captive portal.

Captive portals being used are hosted on the APs. Some are using customized, some are running external pages.

Looks like it's a problem only with certain devices, mostly newer Androids. Clients are getting either timeouts or SSL protocol errors during redirection.

I'm seeing clients captive portal assistants trying to open http://1.1.1.1:880 which now gets redirected to https://1.1.1.1:880 by CloudFlare and that explains the SSL error and also the timeouts because there's nothing at that location.

Anyhow, did not see anything in the release notes but did notice article https://extremeportal.force.com/ExtrArticleDetail?an=000089675

I've set a virtual hostname for all captive portals which solves the issue, but do we need to change some setting for the new 1.1.1.2 redirection IP address to take effect? Recreate the captive portal?

Thanks.

Best regards.

[Andrew_Blomley]

[Andrew_Blomley]

please add a non resolvable RFQN to resolve the problem

[Ondrej_Lepa]

Hello Vedran,

as you upgrade to 5.9.2 it should automatically re-assing the IP to 1.1.1.2 instead of .1.
However, I did not notice this is behaves differently when no virtual hostname is used.

Could you give me some more details so I can edit the article?

Regards,
Ondrej

[Vedran_Jurak]

There is a cpstats ip 1.1.1.2 but In the CP debug I don't see redirect 1.1.1.2 just captive.test. so I did some packet capture:

Internet Protocol Version 4, Src: 192.168.150.101, Dst: 1.1.1.1
Transmission Control Protocol, Src Port: 49228, Dst Port: 880, Seq: 1, Ack: 1, Len: 626
Hypertext Transfer Protocol
[Full request URI: http://captive.test:880/CP-DS/agreement.html?