3 ms·
...and that captive portal link can be replaced by the user if so desired (which it is by me, I don't see why Google needs to know when I try to connect to any
by the_third_wave 4y ago
...and that captive portal link can be replaced by the user if so desired (which it is by me, I don't see why Google needs to know when I try to connect to any network):
settings put global captive_portal_http_url http://captive.example.org/generate_204
settings put global captive_portal_https_url https://captive.example.org/generate_204
settings put global captive_portal_fallback_url http://another.example.org/generate_204
Or, for Android <6.0.1
settings put global captive_portal_server captive.example.org
No Google, no cry. Of course you need to replace those domains with some of your own choice, I use my own server with a bit of nginx configuration to provide this functionality:
server {
listen 80;
listen [::]:80 ipv6only=on;
server_name captive.example.org;
# Apple CNA
location /hotspot-detect.html {
return 200 '<HTML><HEAD><TITLE>Success</TITLE></HEAD><BODY>Success</BODY></HTML>';
add_header Content-Type text/html;
}
# Apple CNA
location /library/test/success.html {
return 200 '<HTML><HEAD><TITLE>Success</TITLE></HEAD><BODY>Success</BODY></HTML>';
add_header Content-Type text/html;
}
# ChromeOS, Android
location /generate_204 {
return 204;
}
# Windows
location /ncsi.txt {
return 200 'Microsoft NCSI';
}
location / {
return 302 http://www.example.org/;
}
}