You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2025. It is now read-only.
I ran into a few networks that whitelist the clients3.google.com endpoint that we currently use to detect captive portals. We should evaluate if probing <18-random-characters>.com generally results in redirects as well or if the captive portals are able to detect that those records do, in fact, not exist. This might be more reliable than the current captive portal detection which has false-negatives occasionally.
The text was updated successfully, but these errors were encountered:
kpcyrd
changed the title
Decap: Probe non-existant dns names to detect portal
Decap: Probe non-existent dns names to detect portal
Jul 1, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I ran into a few networks that whitelist the
clients3.google.com
endpoint that we currently use to detect captive portals. We should evaluate if probing<18-random-characters>.com
generally results in redirects as well or if the captive portals are able to detect that those records do, in fact, not exist. This might be more reliable than the current captive portal detection which has false-negatives occasionally.The text was updated successfully, but these errors were encountered: