Google Play apps are unable to access network after restarting shill
Reported by
nerdsvi...@nerdsville.net,
Aug 9 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9592.71.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.80 Safari/537.36 Platform: 9592.71.0 (Official Build) beta-channel cave Example URL: Steps to reproduce the problem: 1. sudo stop shill 2. sudo start shill BLACKLISTED_DEVICES=tun0 3. Try to search in Google Play Store What is the expected behavior? What went wrong? Google Play could not connect to network Did this work before? N/A Chrome version: 60.0.3112.80 Channel: n/a OS Version: 9592.71.0 Flash Version:
,
Aug 9 2017
,
Dec 27 2017
,
Dec 27 2017
not sure if tun0 is OK to blacklist, will defer to cernekee@
,
Dec 28 2017
The user might be restarting shill in order to tell it not to mess with a tun0 device created by a non-CrOS service (such as openvpn running under crouton): https://github.com/dnschneid/crouton/issues/2215#issuecomment-162231565 This will prevent CrOS' builtin/thirdparty VPN implementations from working as intended. However, assuming that CrOS VPNs are not being used in this test, I would expect the link status from shill to percolate to Android after restarting shill. If Android apps cannot access wifi/wired networks after running those commands, it may be a bug. I'll test it myself and see what happens.
,
Jan 2 2018
> Chrome version: 60.0.3112.80 Channel: n/a > OS Version: 9592.71.0 I'm tried the repro steps a couple of times on samus 65.0.3294.0 / 10215.0.0 but couldn't reproduce the issue. If you see it again on a current Chrome OS release please attach logs + re-open the bug so we can take a look. Thanks!
,
Jan 3 2018
Thanks Kevin, I tried the same on M-64 10176.24.0 and could not reproduce the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nerdsvi...@nerdsville.net
, Aug 9 2017