New issue
Advanced search Search tips

Issue 884267 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Kevin and Elm do not identify their wireless interface correctly

Project Member Reported by baileyberro@chromium.org, Sep 14

Issue description

Elm and Kevin devices (and potentially others I haven't identified) hace ConnectionType::Unknown on their wifi interface.

Steps To Reproduce:
1- Call GetNetworkInterfaceList()
2- Check type of all the interfaces


Expected Result: Wifi interface should have type= CONNECTION_WIFI

Actual Result: Wifi interface has type CONNECTION_UNKNOWN

An easy way to see this issue is to run iwconfig on a kevin/elm and compare it to the result of running iwconfig on another device (eve)
 
Cc: zentaro@chromium.org
Components: -Internals>Network Internals>Network>Connectivity OS>Systems>Network
Since this looks to be a ChromeOS kernel-side issue, I think OS>Systems>Network is the right label, though I'm attaching the relevant net/ label, too.
Can you clarify which GetNetworkInterfaceList() function you are referring to?
The only GetNetworkInterfaceList() function I see is a private method in chromeos::smb_client::NetBiosHostLocator.

The interface type identification code in network_interfaces_linux.cc is best-effort.  Looking at the types of interfaces is far less accurate than NetworkChangeNotifier::GetConnectionType(). NetworkChangeNotifier::GetConnectionType() should be accurate for ChromeOS devices.  The types of interfaces may or may not be; on linux and ChromeOS it uses some ancient ioctls that are deprecated.
Sorry- we are currently calling net::GetNetworkList to get interfaces.


What we are trying to do is enumerate the network interfaces on the device, and use all WIFI or Ethernet connections to discover devices on the local network. Is there another way we could do this? It seems like GetConnectionType only returns the type of the default network.
What kind of devices are you trying to discover?  Why just WiFi and Ethernet?

Comment 7 Deleted

We're using NetBios Name Discovery to find network attached storage devices on local networks
A couple possible solutions:
1. update Kevin and Elm kernels to support SIOCGIWNAME
2. update the device discovery code so that if there is only one network interface and NetworkChangeNotifier::GetConnectionType() indicates CONNECTION_WIFI, then you can assume the one device is WiFi.
This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.
Status: Untriaged
Labels: Enterprise-Triaged

Sign in to add a comment