New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 839984 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

User unable to connect to wifi network with less signal strength when two known networks are present.

Project Member Reported by dsunk...@chromium.org, May 4 2018

Issue description

Chrome Version: M-67 10575.26.0, 67.0.3396.31 
OS: Chrome OS
DUT: Caroline

What steps will reproduce the problem?
(1) Connect to Network-A with AP next to DUT.
(2) Connect to Network-B (GoogleGuest)
(3) Add both the networks to known network list (if not automatically added).
(4) Connect to Network-A and then try to connect to GoogleGuest.

What is the expected result?
User should be able to connect to GoogleGuest.

What happens instead?
Network out of range failure message is displayed.

Device logs attached for more details

2018-05-04T12:08:36.260953-07:00 DEBUG wpa_supplicant[597]: nl80211: Set wlan0 operstate 0->0 (DORMANT)
2018-05-04T12:08:36.260972-07:00 DEBUG wpa_supplicant[597]: netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
2018-05-04T12:08:36.261133-07:00 DEBUG wpa_supplicant[597]: EAPOL: External notification - portEnabled=0
2018-05-04T12:08:36.261163-07:00 DEBUG wpa_supplicant[597]: EAPOL: External notification - portValid=0
2018-05-04T12:08:36.263123-07:00 INFO shill[1610]: [INFO:wifi.cc(649)] Disconnect pending service: credential changed
2018-05-04T12:08:36.263172-07:00 ERR shill[1610]: [ERROR:wifi.cc(975)] Disconnected due to inability to connect to the service.
2018-05-04T12:08:36.263362-07:00 INFO shill[1610]: [INFO:service.cc(398)] Service 151: state Associating -> Failure
2018-05-04T12:08:36.263650-07:00 INFO shill[1610]: [INFO:service.cc(984)] Noting an unexpected failure to connect.
2018-05-04T12:08:36.263713-07:00 INFO shill[1610]: [INFO:manager.cc(1487)] Service 151 updated; state: Failure failure out-of-range
2018-05-04T12:08:36.264928-07:00 INFO shill[1610]: [INFO:service.cc(398)] Service 151: state Failure -> Idle
2018-05-04T12:08:36.265095-07:00 INFO shill[1610]: [INFO:manager.cc(1487)] Service 151 updated; state: Idle failure Unknown
2018-05-04T12:08:36.268829-07:00 ERR shill[1610]: [ERROR:object_proxy.cc(582)] Failed to call method: fi.w1.wpa_supplicant1.Interface.Disconnect: object_path= /fi/w1/wpa_supplicant1/Interfaces/1: fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
2018-05-04T12:08:36.268888-07:00 ERR shill[1610]: [ERROR:dbus_method_invoker.h(112)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=fi.w1.wpa_supplicant1.NotConnected, Message=This interface is not connected
2018-05-04T12:08:36.268957-07:00 ERR shill[1610]: [ERROR:chromeos_supplicant_interface_proxy.cc(196)] Failed to disconnect: fi.w1.wpa_supplicant1.NotConnected This interface is not connected
2018-05-04T12:08:36.269467-07:00 INFO shill[1610]: [INFO:dhcp_config.cc(210)] Stopping 15030 (ReleaseIP)
2018-05-04T12:08:36.269588-07:00 INFO dhcpcd[15030]: received SIGTERM, stopping
2018-05-04T12:08:36.269615-07:00 INFO dhcpcd[15030]: wlan0: removing interface
2018-05-04T12:08:36.269644-07:00 INFO dhcpcd[15030]: status changed to Release
2018-05-04T12:08:36.270055-07:00 INFO dhcpcd[15030]: dhcpcd exited
 
net.log
1.1 MB View Download
debug-logs_20180504-120547.tgz
1.3 MB Download

Comment 1 by cindyb@chromium.org, May 22 2018

Need owner and updated status for this fix.
Labels: -Restrict-View-Google -ReleaseBlock-Stable
1. Why is this bug RBS? Is any user or canary/beta tester hit by this?
2. Is Network-A a protected network (WPA2/WEP)? If so, preferring Network-A over GoogleGuest is expected. I'll look into why the user gets "out of range" for GoogleGuest. 

Cannot reproduce this issue. Tested on Minnie (R67-10575.47.0) and Caroline device (R67-10575.40.0).

Cc: -rpattumani@chromium.org -cernekee@chromium.org jmuppala@chromium.org
Labels: Enterprise-Triaged

Sign in to add a comment