cernekee/stevenjb: This Tether network is getting disconnected, but we are unsure why.

Here are the relevant logs. On the first line, we see that we successfully are connected to a Wi-Fi network. On the last line, we see that we have lost connection to that Wi-Fi network. Are there any indications in these logs that hint why this occurs?

2017-09-08 14:50:48.646 6 4010:4010: active_host_network_state_updater.cc(67): Active host: Connected successfully to device with ID CAESR...XY5E=. Tether network GUID: CAESRgohAI5rEgRu6Iz+kiARYoGuA3CueVAzEU2L0YEGKsvA80lBEiEAvSqF0JR1SSw1LS06/isMSnUXxlUaNsowqQSkMDUXY5E=, Wi-Fi network GUID: <UUID: 7>
2017-09-08 14:50:48.647 3 4010:4010: host_resolver_impl_chromeos.cc(69): DefaultNetworkChanged: Network missing device: CAESRgohAI5rEgRu6Iz+kiARYoGuA3CueVAzEU2L0YEGKsvA80lBEiEAvSqF0JR1SSw1LS06/isMSnUXxlUaNsowqQSkMDUXY5E=
2017-09-08 14:50:48.647 3 4010:4010: host_resolver_impl_chromeos.cc(69): DefaultNetworkChanged: Network missing device: CAESRgohAI5rEgRu6Iz+kiARYoGuA3CueVAzEU2L0YEGKsvA80lBEiEAvSqF0JR1SSw1LS06/isMSnUXxlUaNsowqQSkMDUXY5E=
2017-09-08 14:50:48.648 8 4010:4010: arc_net_host_impl.cc(676): New default network: CAESRgohAI5rEgRu6Iz+kiARYoGuA3CueVAzEU2L0YEGKsvA80lBEiEAvSqF0JR1SSw1LS06/isMSnUXxlUaNsowqQSkMDUXY5E=
2017-09-08 14:50:48.648 3 4010:4010: device_event_log_impl.cc(156): [14:50:48.648] Network: managed_network_configuration_handler_impl.cc:830 GetDeviceProperties: no device: : CAESRgohAI5rEgRu6Iz+kiARYoGuA3CueVAzEU2L0YEGKsvA80lBEiEAvSqF0JR1SSw1LS06/isMSnUXxlUaNsowqQSkMDUXY5E=
2017-09-08 14:50:48.648 3 4010:4010: device_event_log_impl.cc(156): [14:50:48.648] Network: managed_network_configuration_handler_impl.cc:830 GetDeviceProperties: no device: : CAESRgohAI5rEgRu6Iz+kiARYoGuA3CueVAzEU2L0YEGKsvA80lBEiEAvSqF0JR1SSw1LS06/isMSnUXxlUaNsowqQSkMDUXY5E=
2017-09-08 14:50:48.648 8 4010:4010: arc_net_host_impl.cc(63): Required parameter MacAddress was not found.
2017-09-08 14:50:48.648 3 4010:4010: arc_net_host_impl.cc(197): NOTREACHED() hit.
2017-09-08 14:50:48.648 3 4010:4010: arc_net_host_impl.cc(197): NOTREACHED() hit.
2017-09-08 14:50:48.648 8 4010:4010: arc_net_host_impl.cc(63): Required parameter MacAddress was not found.
2017-09-08 14:50:48.648 3 4010:4010: arc_net_host_impl.cc(197): NOTREACHED() hit.
2017-09-08 14:50:48.648 3 4010:4010: arc_net_host_impl.cc(197): NOTREACHED() hit.
2017-09-08 14:50:48.648 8 4010:4010: signin_screen_handler.cc(570): OnNetworkReady() call.
2017-09-08 14:50:48.649 6 4010:4010: ble_connection_manager.cc(218): Register - Device ID: "CAESR...XY5E=", Reason: [KeepAliveTickle]
2017-09-08 14:50:48.673 I chatty  : uid=1002(bluetooth) com.android.bluetooth expire 272 lines
2017-09-08 14:50:48.682 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.682 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.686 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.686 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.704 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.704 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.707 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.707 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.787 3 bluetoothd[1508]:  Unable to register device interface for 04:52:c7:00:00:8a
2017-09-08 14:50:48.787 3 bluetoothd[1508]:  Unable to create object for found device 04:52:c7:00:00:8a
2017-09-08 14:50:48.813 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.813 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.821 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.822 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.826 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.826 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.832 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.832 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.857 6         : shill[1175]: [INFO:portal_detector.cc(125)] Portal detection completed attempt 1 with phase==Content, status==Success, failures in content==0
2017-09-08 14:50:48.858 6         : shill[1175]: [INFO:service.cc(400)] Service 68: state Connected -> Online
2017-09-08 14:50:48.858 6         : shill[1175]: [INFO:manager.cc(1452)] Service 68 updated; state: Online failure Unknown
2017-09-08 14:50:48.869 6         : arc-networkd[4589]: [INFO:manager.cc(89)] Binding to interface wlan0
2017-09-08 14:50:48.897 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.897 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.928 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.928 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.932 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.932 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:48.998 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:48.998 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.068 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.068 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.126 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.126 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.195 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.195 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.333 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.333 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.338 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.338 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.446 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.446 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.452 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.453 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.516 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.516 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.741 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.741 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.754 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.754 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.821 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.821 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.843 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.843 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.869 3 bluetoothd[1508]:  Unable to register device interface for 04:52:c7:00:00:8a
2017-09-08 14:50:49.869 3 bluetoothd[1508]:  Unable to create object for found device 04:52:c7:00:00:8a
2017-09-08 14:50:49.918 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.918 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.930 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.930 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.968 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.968 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:49.997 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:49.997 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.058 3 bluetoothd[1508]:  Unable to register device interface for 60:6d:c7:00:00:35
2017-09-08 14:50:50.058 3 bluetoothd[1508]:  Unable to create object for found device 60:6d:c7:00:00:35
2017-09-08 14:50:50.152 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.152 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.292 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.292 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.309 I chatty  : uid=1002(bluetooth) BT Service Call expire 75 lines
2017-09-08 14:50:50.321 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.321 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.361 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:50.361 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:50.370 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.371 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.458 3         : arc-networkd[3076]: [ERROR:arc_ip_config.cc(135)] SIOCGIFFLAGS failed
2017-09-08 14:50:50.458 3 arc-networkd[3076]:  [ERROR:arc_ip_config.cc(135)] SIOCGIFFLAGS failed
2017-09-08 14:50:50.520 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.520 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.561 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.561 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.641 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.641 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.647 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.647 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.830 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.830 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.837 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.837 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:50.844 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:50.844 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.083 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.083 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.107 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.107 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.109 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.109 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.172 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.172 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.178 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.178 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.182 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.182 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.330 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.330 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.391 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.391 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.393 3 bluetoothd[1508]:  Unable to register device interface for dc:a9:04:00:00:33
2017-09-08 14:50:51.393 3 bluetoothd[1508]:  Unable to create object for found device dc:a9:04:00:00:33
2017-09-08 14:50:51.421 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.421 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.457 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.457 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.466 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.466 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.524 3 bluetoothd[1508]:  Unable to register device interface for 04:52:c7:00:00:8a
2017-09-08 14:50:51.524 3 bluetoothd[1508]:  Unable to create object for found device 04:52:c7:00:00:8a
2017-09-08 14:50:51.601 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:51.601 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:51.685 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.685 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.698 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.698 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.767 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.767 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.783 3 bluetoothd[1508]:  Unable to register device interface for dc:a9:04:00:00:33
2017-09-08 14:50:51.784 3 bluetoothd[1508]:  Unable to create object for found device dc:a9:04:00:00:33
2017-09-08 14:50:51.812 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.812 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:51.937 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:51.937 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.010 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.010 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.090 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.090 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.200 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.200 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.298 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.298 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.486 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.486 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.496 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.496 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.502 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.502 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.604 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:52.604 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:52.620 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.620 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.630 3 bluetoothd[1508]:  Unable to register device interface for 04:52:c7:00:00:8a
2017-09-08 14:50:52.630 3 bluetoothd[1508]:  Unable to create object for found device 04:52:c7:00:00:8a
2017-09-08 14:50:52.724 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.724 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.750 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.750 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.790 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.790 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.796 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.796 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.906 I chatty  : uid=1002(bluetooth) com.android.bluetooth expire 269 lines
2017-09-08 14:50:52.910 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.910 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.918 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.918 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.924 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.924 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:52.991 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:52.991 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.004 6         : shill[1175]: [INFO:wifi.cc(326)] Scan on wlan0 from RequestScan
2017-09-08 14:50:53.132 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.132 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.143 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.143 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.148 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:53.148 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:53.149 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.149 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.240 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.240 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.338 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.339 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53       Battery History: 070 80880000 +tmpwhitelist=u0a13:"broadcast:u0a13:com.google.android.intent.action.GCM_RECONNECT"
2017-09-08 14:50:53.443 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.443 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.565 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.565 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.626 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.626 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.629 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.629 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.738 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.738 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.745 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.745 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.751 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.751 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.751 D BluetoothEventManager: DeviceFoundHandler created new CachedBluetoothDevice: d9:61:13:00:00:24
2017-09-08 14:50:53.757 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.757 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.850 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.850 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.872 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:53.872 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:53.924 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.925 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.931 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.931 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.965 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:53.965 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:53.998 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:53.998 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:54.010 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.010 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.097 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.097 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.102 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.102 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.110 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.110 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.125 I gtalk_connection: 16974847
2017-09-08 14:50:54.131 I am_pss  : [1217,10013,com.google.android.gms.unstable,28630016,19648512,0]
2017-09-08 14:50:54.141 I am_pss  : [1687,10060,com.google.android.videos,20919296,17752064,0]
2017-09-08 14:50:54.165 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.165 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.259 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.259 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.264 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.264 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.269 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.269 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.284 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:54.284 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:54.353 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.353 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.360 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.360 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.364 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.364 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.386 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.386 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.429 I chatty  : uid=1002(bluetooth) BT Service Call expire 76 lines
2017-09-08 14:50:54.523 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.523 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.605 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.605 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.610 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.611 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.618 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.618 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.796 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.796 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.827 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.827 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.837 3 bluetoothd[1508]:  Unable to register device interface for 04:52:c7:00:00:8a
2017-09-08 14:50:54.837 3 bluetoothd[1508]:  Unable to create object for found device 04:52:c7:00:00:8a
2017-09-08 14:50:54.895 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.895 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.902 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.902 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:54.911 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:54.911 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:54.916 6 4010:4010: ble_connection_manager.cc(462): Connection attempt timeout - Device ID "CAESR...+AwDS"
2017-09-08 14:50:54.917 6 4010:4010: ble_connection_manager.cc(499): Status change - Device ID: "CAESR...+AwDS": [connecting] => [disconnected]
2017-09-08 14:50:54.919 6 4010:4010: message_transfer_operation.cc(114): Connection attempt failed for device with ID CAESR...+AwDS. Number of failures so far: 3
2017-09-08 14:50:54.919 6 4010:4010: message_transfer_operation.cc(119): Connection retry limit reached for device with ID CAESR...+AwDS. Unregistering device.
2017-09-08 14:50:54.920 6 4010:4010: ble_connection_manager.cc(245): Unregister - Device ID: "CAESR...+AwDS", Reason: [TetherAvailabilityRequest]
2017-09-08 14:50:54.921 6 4010:4010: ble_connection_manager.cc(430): Attempting connection - Device ID: "CAESR...EFw=="
2017-09-08 14:50:54.922 6 4010:4010: ble_connection_manager.cc(499): Status change - Device ID: "CAESR...EFw==": [disconnected] => [connecting]
2017-09-08 14:50:54.924 4 4010:4098: exported_object.cc(215): Unknown method: message_type: MESSAGE_METHOD_CALL
2017-09-08 14:50:54.924 4 4010:4098: destination: :1.88
2017-09-08 14:50:54.924 4 4010:4098: path: /org/chromium/bluetooth_advertisement/cf9b92ec745f4455b8cb2d148322e5a8
2017-09-08 14:50:54.924 4 4010:4098: interface: org.freedesktop.DBus.ObjectManager
2017-09-08 14:50:54.924 4 4010:4098: member: GetManagedObjects
2017-09-08 14:50:54.924 4 4010:4098: sender: :1.27
2017-09-08 14:50:54.924 4 4010:4098: serial: 5169
2017-09-08 14:50:54.924 4 4010:4098: 
2017-09-08 14:50:54.924 4 4010:4098: 
2017-09-08 14:50:54.926 6 4010:4010: ble_advertiser.cc(176): Advertisement registered. Device ID: "CAESR...EFw==", Service data: 0x3bfd1366
2017-09-08 14:50:54.988 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:54.988 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.000 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.000 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.005 3 bluetoothd[1508]:  Unable to register device interface for ac:9e:17:00:00:93
2017-09-08 14:50:55.005 3 bluetoothd[1508]:  Unable to create object for found device ac:9e:17:00:00:93
2017-09-08 14:50:55.032 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.032 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.071 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.071 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.171 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.171 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.181 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.181 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.234 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.234 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.243 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.243 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.248 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.248 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.312 3 bluetoothd[1508]:  Unable to register device interface for dc:a9:04:00:00:33
2017-09-08 14:50:55.312 3 bluetoothd[1508]:  Unable to create object for found device dc:a9:04:00:00:33
2017-09-08 14:50:55.325 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.325 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.366 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.366 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.370 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.370 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.387 3 bluetoothd[1508]:  Unable to register device interface for 04:52:c7:00:00:8a
2017-09-08 14:50:55.387 3 bluetoothd[1508]:  Unable to create object for found device 04:52:c7:00:00:8a
2017-09-08 14:50:55.423 6         : shill[1175]: [INFO:service.cc(292)] wifi service 71 constructed.
2017-09-08 14:50:55.423 6         : shill[1175]: [INFO:wifi_service.cc(181)] Constructed WiFi service 71 name: [SSID=24]
2017-09-08 14:50:55.423 6         : shill[1175]: [INFO:wifi_service.cc(783)] Rep ep updated for 71. [SSID=24], bssid: 08:86:3b:00:00:ae, sig: -48, sec: rsn, freq: 2432
2017-09-08 14:50:55.429 6         : shill[1175]: [INFO:wifi.cc(393)] ScanDone
2017-09-08 14:50:55.431 6         : shill[1175]: [INFO:service.cc(292)] wifi service 72 constructed.
2017-09-08 14:50:55.432 6         : shill[1175]: [INFO:wifi_service.cc(181)] Constructed WiFi service 72 name: [SSID=12]
2017-09-08 14:50:55.432 6         : shill[1175]: [INFO:wifi_service.cc(783)] Rep ep updated for 72. [SSID=12], bssid: ec:08:6b:00:00:a1, sig: -66, sec: 802_1x, freq: 2437
2017-09-08 14:50:55.456 6         : shill[1175]: [INFO:service.cc(292)] wifi service 73 constructed.
2017-09-08 14:50:55.456 6         : shill[1175]: [INFO:wifi_service.cc(181)] Constructed WiFi service 73 name: [SSID=51]
2017-09-08 14:50:55.456 6         : shill[1175]: [INFO:wifi_service.cc(783)] Rep ep updated for 73. [SSID=51], bssid: 94:b4:0f:00:00:cf, sig: -92, sec: rsn, freq: 5240
2017-09-08 14:50:55.466 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.466 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.470 6         : shill[1175]: [INFO:wifi_service.cc(783)] Rep ep updated for 34. [SSID=13], bssid: 00:1f:1f:00:00:a2, sig: -50, sec: none, freq: 2412
2017-09-08 14:50:55.473 6         : shill[1175]: [INFO:wifi_service.cc(783)] Rep ep updated for 39. [SSID=62], bssid: e0:91:f5:00:00:e2, sig: -80, sec: none, freq: 2462
2017-09-08 14:50:55.474 3         : arc-networkd[3076]: [ERROR:arc_ip_config.cc(135)] SIOCGIFFLAGS failed
2017-09-08 14:50:55.474 3 arc-networkd[3076]:  [ERROR:arc_ip_config.cc(135)] SIOCGIFFLAGS failed
2017-09-08 14:50:55.475 D LocalBluetoothProfileManager: Current Profiles[]
2017-09-08 14:50:55.475 D LocalBluetoothProfileManager: New Profiles[]
2017-09-08 14:50:55.477 D WifiService: Scan Completed
2017-09-08 14:50:55.479 6         : shill[1175]: [INFO:service.cc(321)] Connect to service 13: ConnectToBestServicesTask
2017-09-08 14:50:55.480 6 kernel  :  [  182.169195] wlan0: deauthenticating from ac:37:43:00:00:1f by local choice (Reason: 3=DEAUTH_LEAVING)
2017-09-08 14:50:55.488 5 wlan0   : wpa_supplicant[577]: wlan0: CTRL-EVENT-DISCONNECTED bssid=ac:37:43:00:00:1f reason=3 locally_generated=1
2017-09-08 14:50:55.488 6         : shill[1175]: [INFO:service.cc(400)] Service 13: state Idle -> Associating
2017-09-08 14:50:55.488 6         : shill[1175]: [INFO:manager.cc(1452)] Service 13 updated; state: Associating failure Unknown
2017-09-08 14:50:55.488 5 wlan0   : wpa_supplicant[577]: wlan0: SME: Trying to authenticate with 6c:f3:7f:00:00:1d (SSID='1' freq=5660 MHz)
2017-09-08 14:50:55.488 6         : shill[1175]: [INFO:service.cc(400)] Service 68: state Online -> Idle
2017-09-08 14:50:55.488 6         : shill[1175]: [INFO:manager.cc(1452)] Service 68 updated; state: Idle failure Unknown
2017-09-08 14:50:55.489 6 kernel  :  [  182.178039] wlan0: authenticate with 6c:f3:7f:00:00:1d
2017-09-08 14:50:55.490 6         : shill[1175]: [INFO:manager.cc(1696)] Default physical service: 13 (not connected)
2017-09-08 14:50:55.491 6         : shill[1175]: [INFO:service.cc(314)] Suppressed autoconnect to service 13 (connecting)
2017-09-08 14:50:55.491 6         : shill[1175]: [INFO:wifi.cc(863)] WiFi wlan0 supplicant updated DisconnectReason to -3
2017-09-08 14:50:55.492 6 4010:4010: tether_network_disconnection_handler.cc(41): Connection to active host (Wi-Fi network GUID <UUID: 7>) has been lost.

Looking at the network_event_log section:

UUID: 7 = /service/68

/service/68 went online @ 14:50:48.862
Google-A (/service/13) went to 'association' @ 14:50:55.489 and 'online' @ 14:50:56.337

Google-A is preferred over insecure networks and we will automatically switch once credentials are available.

I'm not sure why a tether network would be considered insecure, maybe cernekee@ can answer that.

We may be able to prevent this behavior by setting the Priority property of the tether network to 1 (assuming we actually want to avoid this behavior).

Interesting...

cernekee@: Why is the Tether network considered insecure?

stevenjb@: Would we just add some setter to NetworkState to set the priority? Where in the code do we choose a higher priority over a lower one?

I just remembered, the switch to a more secure network is done explicitly during login. The event is 'ConnectToBestServices' which occurred @ 14:50:55.478, 5 seconds after we connected to the Tether network. (The delay is because we wait for certificates to load and for a WiFi scan result to complete before switching to the 'Best' network).

[14:50:55.478] EVENT: auto_connect_handler.cc:277 ConnectToBestServices

So the correct fix is to have the tether configuration tell AutoConnectHandler not to call ConnectToBestServices. Usually we do that in AutoConnectHandler::ConnectToNetworkRequested() which is triggered from  NetworkConnectionHandlerImpl::ConnectToNetwork() when the UI requests a connection. Since Tether is presumably using a different code path it needs to do something similar.

(FYI, but no longer important: When you configure the network, 'Priority' is a Shill and ONC property; I don't recall where/how you configure tethered wifi networks)

> Google-A is preferred over insecure networks

I believe the managed_credentials_ check in Service::Compare will cause Google-A to outrank other networks regardless of priority, technology, security level, etc.  shill tries pretty aggressively to connect to managed networks when they are available.  I don't think we want to mess with that ranking.

From what I can tell, the bigger problem is that Chrome invokes ConnectToBestServices too readily.  ConnectToBestServices will override the previous decision to connect to a lower-ranked network.  For instance, you can open up the system menu -> Network, then click on GoogleGuest, and leave the menu open.  After the next periodic (5-second) scan, Chrome will invoke ConnectToBestServices.  That will cause shill to disconnect from GoogleGuest and attempt to reconnect to Google-A.

Does that explanation make sense?

That's basically what I intended to suggest in comment #5; we just need to signal to AutoConenctHandler when we connect to a Tether network, the same as we do if a user explicitly connects to any other network before ConnectToBestServices is called (via NetworkConnectionObserver::ConnectToNetworkRequested).

Also, to clarify, the second paragraph in comment #6 is incorrect. If a user explicitly connects to, e.g. GoogleGuest, NetworkConnectionObserver::ConnectToNetworkRequested will be called which will cancel the ConnectToBestServices call.

https://cs.chromium.org/chromium/src/chromeos/network/auto_connect_handler.cc?dr=C&l=114

Do you know what is causing the unwanted disconnection from GoogleGuest in this case?  I am still able to reproduce this phenomenon on a corp-enrolled device running M62.

Which phenomenon exactly? The logic *should* be:

If a user logs in and *then* *explicitly* connects to *any* network (i.e. including GoogleGuest), then we should *not* call ConnectToBestServices().

If that is not true, please file a separate bug (which this may turn out to be a duplicate of) with a specific repro.

Also, to clarify, ConnectToBestServices() may be called:
a) After login
b) After policies are applied
c) After certificates are resolved

It is possible that there is a bug where one of those events is occurring significantly after the others and the logic in ConnectToNetworkRequested() is getting overriden.

That said, I only see one call to ConnectToBestServices in my chrome://device-log.

I tested this with a corp account and was able to reproduce the issue.

Here's the series of events:
(1) User logs in.
(2) User connects to a Tether network.
(3) Policy is applied. Scan starts up, but there are no networks in the policy, so nothing happens.
(4) Certificate #1 is resolved. Scan starts up.
(5) Certificate #2 is resolved. I'm not sure why there are multiple certificates, but this is what happened for a google.com account.
(6) Scan finishes up, and Google-A is now a valid network.
(7) Connection starts to Google-A, disconnecting the Tether network.

From step 1 to step 7, I saw a gap of around 10 seconds (sometimes as little as 5s, sometimes as much as 15s).


Now, what should be done? stevenjb@'s comment #10 implies that if the user connects to any network explicitly, we should not attempt an auto-connect. However, in issue 709664 comment #4, he also describes a situation which seems to be suggesting the opposite. What should be the correct path forward? Here are 3 solutions I have:

(1) If the user explicitly connects to a Wi-Fi or Tether network, do not attempt an auto-connect, even if there is a more secure network available. This will remove any confusion that the user might have about why the network switched when the user didn't ask for it to be switched. However, it has the potential to leave the user on a less secure network.

(2) Special-case Tether networks: If the user explicitly connects to a Tether network, do not attempt an auto-connect. CrOS treats Tether networks as a new connection type, and the user does not get an indication that they are actually Wi-Fi networks underneath the hood. Thus, it could be especially confusing for users why their connection medium changed. This solution leaves the status quo for normal Wi-Fi networks: we will still "upgrade" their connection to a more secure network if possible.

(3) Always auto-connect to the most secure network. This ensures the user is connected to the most secure network, but it creates UX problems where users will be confused why they were disconnected from an active Tether network. This has the potential to make Instant Tethering appear broken.


I'm personally a fan of option 1, with option 2 as a fallback. I don't think we should keep option 3 as we currently have today.

I'm not sure how I suggested "the opposite" (I didn't intend to). We clearly want to cancel any "ConnectToBest" requests if a user explicitly connects to a network (Tether or otherwise).

I think we are overthinking this. I think the code just evolved to the point where we need a separate boolean to indicate "user has explicitly connected to a network, don't call ConnectToBestServices".

Ah, I see - I may have misunderstood the other comment. Sorry for the confusion! :)

Your suggestion sounds good to me. I'll spin up a CL today to fix this.

After chatting with TPMs, I'm moving this to M-63 since it's too late for all but launch-blocking fixes. This is mostly a minor issue that only affects people with enterprise network certificates.

Pasting some comments from the CL here:

I think that the steps in comment #12 are expected behavior. e.g. the Tether (or open wifi) connection may be required to download the policy and configure the secure network. In that case we absolutely (or at least -generally-) want to connect to the more secure network. I think it is reasonable to assume that intentionally connecting to a Tether network when a secure WiFi network is available (and before the configuration or credentials for that network are loaded) is an edge case.

I do think it is reasonable to protect against spurrious ConnectToBestNetwork requests once ConnectToBestNetwork is successfully called, but if we want to change the behavior more aggressively we will want to loop in a PM from the enterprise team.

#13 SGTM, I see dskaram@ as the final decision maker for this since it's explicitly enterprise issue.

Seems fine. +1 to not overcomplicating things for an edge case.

So, I was a bit hasty in comment #13. All (or some anyway) of the edge cases have been coming back to me from when we originally implemented this.

Here I think is the fundamental scenario that is challenging:

1. User brings their Chromebook to work or to school. Their policy configuration or credentials are not up to date, or it's a slower Chromebook where certificates can take up to 30 seconds to load.
2. User opens their device and logs in, not connected.
3. User explicitly connects to Tether or some random insecure WiFi network.
4. Policy updates and/or certificates load and a secure network becomes available.

What do we do?

The current behavior is to switch to the secure network. IIRC, this was an explicit decision we made in the past.

This is an edge case, but it does have security implications. If we want to reverse that decision that is fine, I just want to make sure we have considered this scenario (and we should document it and reference this issue in the code).

Our options:
a) Leave things as they are. (Argument: staying connected to Tether or an insecure WiFi network is rarely desired by users).
b) Disable auto-switch after a user has explicitly connected to any network.
c) a + notify on auto-switch.
d) b + notify when a secure network becomes available.

I believe that c + d were considered before but never prioritized.

Thanks Steven. We def want to retain the network switch logic. But having a notification would be very helpful to the user. Something on the order of:

"Your connection is switching to a more secure managed network".


The WiFi signal would be a good icon to have on that notification.


Assigning to Kyle who said he wanted to take a stab at this.

sgtm

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/dbf7ad751d5587abdc896cb56e3d2b843014abd1

commit dbf7ad751d5587abdc896cb56e3d2b843014abd1
Author: Kyle Horimoto <khorimoto@google.com>
Date: Wed Jan 10 20:18:37 2018

[CrOS Tether] Alert observers when AutoConnectHandler attempts to connect.

This CL causes AutoConnectHandler to alert observers when it
successfully initiates an auto-connection. Note that this does not imply
that a connection has actually succeeded; rather, this notification is
delivered when the auto-connect process has been initiated. This will be
used by the following CL to alert users when this occurs:
https://chromium-review.googlesource.com/c/chromium/src/+/853293

Bug:  764000 , 672263
Change-Id: Id957087db618e952888c194fb5690aaf42bd1b46
Reviewed-on: https://chromium-review.googlesource.com/809769
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#528407}
[modify] https://crrev.com/dbf7ad751d5587abdc896cb56e3d2b843014abd1/chromeos/network/auto_connect_handler.cc
[modify] https://crrev.com/dbf7ad751d5587abdc896cb56e3d2b843014abd1/chromeos/network/auto_connect_handler.h
[modify] https://crrev.com/dbf7ad751d5587abdc896cb56e3d2b843014abd1/chromeos/network/auto_connect_handler_unittest.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9931bb29eb1e56332d8026bfb66fb46e9962cdb4

commit 9931bb29eb1e56332d8026bfb66fb46e9962cdb4
Author: Kyle Horimoto <khorimoto@google.com>
Date: Fri Jan 12 01:19:27 2018

[CrOS Tether] Alert the user upon successful auto-connection.

Now, when a network is auto-connected (e.g., due to an enterprise
policy which includes a managed network), the user is notified of this
change. Previously, the user was not alerted to what was happening.

This change especially improves the following situation:
  (1) User logs in and connects to a network (possibly a Tether
      network).
  (2) User's policy loads and contains some some auto-connect networks.
  (3) AutoConnectHandler disconnects from the network in part (1) and
      instead connects to the network in part (2).

This logic is unexpected to the user because the user will be confused
that the device is actually connected to a different network than was
requested. This condition is especially confusing for users connecting
to Tether networks because a policy could auto-connect the user to a
different connection medium altogether (namely, Wi-Fi).

Bug:  764000 , 672263
Change-Id: I38d9bb900417305dfb2e438e39f4d8737388e2d4
Reviewed-on: https://chromium-review.googlesource.com/853293
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#528835}
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/app/chromeos_strings.grdp
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/chromeos/net/DEPS
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/ui/BUILD.gn
[add] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/ui/ash/auto_connect_notifier.cc
[add] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/ui/ash/auto_connect_notifier.h
[add] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/ui/ash/auto_connect_notifier_unittest.cc
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/ui/ash/chrome_browser_main_extra_parts_ash.cc
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/browser/ui/ash/chrome_browser_main_extra_parts_ash.h
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chrome/test/BUILD.gn
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chromeos/network/auto_connect_handler.h
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chromeos/network/network_handler.cc
[modify] https://crrev.com/9931bb29eb1e56332d8026bfb66fb46e9962cdb4/chromeos/network/network_handler.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f3825f1481544e11dff6941a488e3110c65900b0

commit f3825f1481544e11dff6941a488e3110c65900b0
Author: Kyle Horimoto <khorimoto@google.com>
Date: Wed Jan 17 19:06:53 2018

[CrOS Tether] Correct auto-connect notification icon.

The previous icon was an incorrect color. This change was suggested by
estade@ as part of:

https://chromium-review.googlesource.com/c/chromium/src/+/853293.

Bug:  764000 , 672263
Change-Id: Ieb777da5cff292cbe455d78ea16f40408c4527a9
Reviewed-on: https://chromium-review.googlesource.com/865566
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#529836}
[modify] https://crrev.com/f3825f1481544e11dff6941a488e3110c65900b0/chrome/browser/ui/ash/auto_connect_notifier.cc