New issue
Advanced search Search tips

Issue 821616 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Captive portal plays poorly with Google home's "Family Pause" feature.

Project Member Reported by abodenha@chromium.org, Mar 13 2018

Issue description

What steps will reproduce the problem?
(1) Connect to wifi on a Google home that you manage
(2) Enable the "family wifi" feature and pause wifi for your device.
(3) Try to use the network

What is the expected result?
The pause might cause captive portal to trigger. That's fine, but if so the captive portal UI should display the home's "Network is paused" screen.


What happens instead?
If captive portal triggers it shows a page that says "Not found" which is very unhelpful.

I suspect that the captive portal code is trying to open a page directly on the router's IP which is causing the router to 404.  One solution might be to check the return value on the captive portal page and if it's an error attempt to navigate to some well known public page (a help center page?).  Doing so would give the router another chance to show something useful and would show a potentially useful page if the router was allowing a subset of traffic through.
 
Screenshot 2018-03-13 at 10.14.43 AM.png
138 KB View Download
Screenshot 2018-03-13 at 10.16.12 AM.png
222 KB View Download

Comment 1 by warx@chromium.org, Mar 14 2018

What is "family wifi" feature? Is this a Google home or Google wifi or Chrome OS feature?
It's a Google WiFi feature. It allows you to block specific devices from accessing internet - either permanently or on specific schedule.

If you need a router to play with, I can bring one over.


Comment 3 by warx@chromium.org, Mar 14 2018

Thanks, that would be very helpful.

Comment 4 by warx@chromium.org, Jun 26 2018

Owner: ----
Status: Untriaged (was: Assigned)
Cc: -zelidrag@chromium.org
Labels: Enterprise-Triaged
Owner: r...@chromium.org
Cc: r...@chromium.org tbarzic@chromium.org
Owner: jessejames@google.com
Owner: jessejames@chromium.org
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment