captive portal requirement for chormeOS is pain point for end user |
||||||
Issue descriptionChromeOS require update to the firewall to whitelist "alt*.gstatic.com". ( se https://support.google.com/chrome/a/answer/7623757) is a pain point for end user. Imagine you are traveling and trying to explain the the front desk that they need to whitelist "alt*.gstatic.com". I am not sure the reason why this white list is needed, but most other devices do not need this: android, iphone, mac, windows. To put this responsibility between the front desk and the user is not acceptable. We need to make this work as good as (or better) then all other counter part.
,
Jun 15 2018
I believe this should have been fixed with https://bugs.chromium.org/p/chromium/issues/detail?id=776409 earlier this year. What build are you running?
,
Jun 18 2018
Platform 10452.99.0 (Official Build) stable-channel eve
,
Jun 18 2018
aashutoshk@ / dsunkara@ - Please try repro this.
,
Jun 19 2018
@Danny: Was this on login screen or OOBE? If you are hitting http://crbug/776409 you should see something like this in the logs, >> 2017-09-28T16:24:48.089965-07:00 ERR shill[953]: [ERROR:http_request.cc(188)] Could not resolve hostname alt16.gstatic.com: The network connection was timed out And network not available(Dinosaur) pop-up while logging in. If not, then this may be an entirely different issue. Can you share logs or a screenshot? Also, The help page at https://support.google.com/chrome/a/answer/7623757 is deprecated. The CL's for the captive portal URL randomization were reverted. We should update or remove the support page. p.s. I am able to login fine on a captive portal network (Eve-10452.99.0). Will try to repro after getting more details. Other similar issues, https://crbug/851013
,
Jun 27 2018
Who should own the removal of the support page ?
,
Jun 27 2018
@mattwerner: Can you look into updating/removing the support page?
,
Jun 30 2018
Removing UI>Browser>Interstitials because this sounds like a networking issue, not related to the interstitial UI.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dchan@google.com
, Jun 15 2018