Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

14
  • 6
    @RuiFRibeiro: there usually is a DNS hijacking being performed by captive portals, with all queries returning the captive portal IP address until passed. Note that you using 1.1.1.1/8.8.8.8 doesn't protect you from a MITM that goes after UDP packets to port 53.
    – Ángel
    Commented Oct 7, 2019 at 1:00
  • 1
    On all devices I have, the captive portal is opened using, I guess, a "browser view" rather than the regular browser. I some cases where I have to enter login details to get access, I would prefer to use a regular browser that remembers passwords but, especially on phones, it is hard or impossible to copy the URL (or even see the full address) for use in a regular browser. Is there a way around this?
    – d-b
    Commented Oct 7, 2019 at 7:17
  • 1
    What is ICMP Redirect? I’ve never heard about that before in the context of a captive portal.
    – jornane
    Commented Oct 7, 2019 at 8:19
  • 2
    For a long time, I have estabilished a practice for myself to enter http://www.example.com after connecting to public wifi exactly because the Captive portal wouldn't work for HTTPS pages, like superuser.com. Commented Oct 7, 2019 at 10:24
  • 6
    @TomášZato: NeverSSL employs another neat trick that example.com doesn't: it uses ECMAScript to redirect to a randomly generated subdomain, that way, when you see the website in your browser, you know that web surfing is working, as it is highly unlikely to be a cached copy. Commented Oct 7, 2019 at 10:54