[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Great idea. This list is also a good place to document a current state of things (?) - and IETF travels will see it all!

Disclaimers: While I recommend Wireshark for troubleshooting, and things like pcap files are valuable for reference and debugging, please do not post anything containing PII to the mailing list (or to anyone, delete it!).

On Sun, Apr 2, 2017 at 3:27 PM, Michael Richardson <[email protected]> wrote:

David Bird <[email protected]> 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 :)

One of the things we are going to need to do is to find a way use the
stick as well as the carrot when it comes to poorly behaved sites.

This requires that we have running code and RFCs to form the carrot first.
But, we do need a place to record the problems we and others see with
captive portals that there out there.   It would be lovely if we could
get one or more social media travel sites to introduce categories for
"poor captive portal" in their reviews.

--
Michael Richardson <[email protected]>, Sandelman Software Works
 -= IPv6 IoT consulting =-