Re: [Captive-portals] Not good....

[David Bird <dbird@google.com>]

Sorry, the true issue is just the DNS. The capport detection should be working in this case... But, the DNS limitation is what is preventing my laptop and android from getting capport notification.

On Fri, Mar 31, 2017 at 12:27 PM, David Bird <dbird@google.com> wrote:

Wi-Fi at Chicago O'Hare Airport defeating Chome captive portal check. They also require using their DHCP assigned DNS (why don't they just DNAT DNS to their server, I don't know -- chilli will do that :)

It is impossible for my to get the portal using Android... 

GET /generate_204 HTTP/1.1
Host: captive-portal-check.appspot.com
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Accept: /
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8

HTTP/1.1 302 Found
Location: https://via.boingohotspot.net/login
Connection: close
Content-Type: text/html; charset=utf-8
Content-Length: 343


<!--<?xml version="1.0" encoding="UTF-8"?><WISPAccessGatewayParam xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.acmewisp.com/WISPAccessGatewayParam.xsd"><Redirect><LoginURL>https://via.boingohotspot.net/login</LoginURL><MessageType>100</MessageType></Redirect></WISPAccessGatewayParam>-->