Scanning with "iw" fails on whirlwind |
||||
Issue description06/26 00:27:34.018 DEBUG| ssh_host:0180| Running (ssh) '/usr/local/sbin/iw dev' 06/26 00:27:34.200 DEBUG| base_utils:0278| [stdout] phy#2 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] Interface wlan2 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] ifindex 8 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] wdev 0x200000001 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] addr 30:b5:c2:33:d6:0a 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] type managed 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] phy#1 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] Interface wlan1 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] ifindex 7 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] wdev 0x100000001 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] addr 30:b5:c2:33:da:75 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] type managed 06/26 00:27:34.201 DEBUG| base_utils:0278| [stdout] phy#0 06/26 00:27:34.202 DEBUG| base_utils:0278| [stdout] Interface wlan0 06/26 00:27:34.202 DEBUG| base_utils:0278| [stdout] ifindex 6 06/26 00:27:34.202 DEBUG| base_utils:0278| [stdout] wdev 0x1 06/26 00:27:34.202 DEBUG| base_utils:0278| [stdout] addr 30:b5:c2:33:d2:ec 06/26 00:27:34.202 DEBUG| base_utils:0278| [stdout] type managed 06/26 00:27:34.203 INFO | chaos_runner:0082| Performing a scan with a max timeout of 30 seconds. 06/26 00:27:34.204 DEBUG| ssh_host:0180| Running (ssh) '(time -p iw dev wlan0 scan) 2>&1' 06/26 00:27:34.357 DEBUG| base_utils:0278| [stdout] command failed: Network is down (-100) 06/26 00:27:34.360 DEBUG| base_utils:0278| [stdout] Command exited with non-zero status 156 06/26 00:27:34.360 DEBUG| base_utils:0278| [stdout] real 0.01 06/26 00:27:34.361 DEBUG| base_utils:0278| [stdout] user 0.00 06/26 00:27:34.361 DEBUG| base_utils:0278| [stdout] sys 0.01 06/26 00:27:34.363 DEBUG| iw_runner:0585| scan exit_status: 156 06/26 00:27:34.363 DEBUG| ssh_host:0180| Running (ssh) '(time -p iw dev wlan0 scan) 2>&1' 06/26 00:27:34.512 DEBUG| base_utils:0278| [stdout] command failed: Network is down (-100) 06/26 00:27:34.513 DEBUG| base_utils:0278| [stdout] Command exited with non-zero status 156 06/26 00:27:34.515 DEBUG| base_utils:0278| [stdout] real 0.01 06/26 00:27:34.515 DEBUG| base_utils:0278| [stdout] real 0.01 06/26 00:27:34.515 DEBUG| base_utils:0278| [stdout] user 0.01 06/26 00:27:34.515 DEBUG| base_utils:0278| [stdout] sys 0.00 06/26 00:27:34.517 DEBUG| iw_runner:0585| scan exit_status: 156 06/26 00:27:34.517 DEBUG| ssh_host:0180| Running (ssh) '(time -p iw dev wlan0 scan) 2>&1' 06/26 00:27:34.699 DEBUG| base_utils:0278| [stdout] command failed: Network is down (-100) 06/26 00:27:34.700 DEBUG| base_utils:0278| [stdout] Command exited with non-zero status 156 06/26 00:27:34.700 DEBUG| base_utils:0278| [stdout] real 0.01 06/26 00:27:34.700 DEBUG| base_utils:0278| [stdout] user 0.00 06/26 00:27:34.700 DEBUG| base_utils:0278| [stdout] sys 0.01 06/26 00:27:34.702 DEBUG| iw_runner:0585| scan exit_status: 156 06/26 00:27:34.702 DEBUG| ssh_host:0180| Running (ssh) '(time -p iw dev wlan0 scan) 2>&1' 06/26 00:27:34.847 DEBUG| base_utils:0278| [stdout] command failed: Network is down (-100) 06/26 00:27:34.848 DEBUG| base_utils:0278| [stdout] Command exited with non-zero status 156 06/26 00:27:34.848 DEBUG| base_utils:0278| [stdout] real 0.01 06/26 00:27:34.848 DEBUG| base_utils:0278| [stdout] user 0.00 06/26 00:27:34.848 DEBUG| base_utils:0278| [stdout] sys 0.01 06/26 00:27:34.850 DEBUG| iw_runner:0585| scan exit_status: 156 06/26 00:27:34.851 DEBUG| ssh_host:0180| Running (ssh) '(time -p iw dev wlan0 scan) 2>&1' 06/26 00:27:35.015 DEBUG| base_utils:0278| [stdout] command failed: Network is down (-100) 06/26 00:27:35.021 DEBUG| base_utils:0278| [stdout] Command exited with non-zero status 156 06/26 00:27:35.021 DEBUG| base_utils:0278| [stdout] real 0.01 06/26 00:27:35.021 DEBUG| base_utils:0278| [stdout] user 0.01 06/26 00:27:35.021 DEBUG| base_utils:0278| [stdout] sys 0.00 06/26 00:27:35.022 DEBUG| iw_runner:0585| scan exit_status: 156 06/26 00:27:35.022 DEBUG| ssh_host:0180| Running (ssh) '(time -p iw dev wlan0 scan) 2>&1' 06/26 00:27:35.175 DEBUG| base_utils:0278| [stdout] command failed: Network is down (-100) 06/26 00:27:35.177 DEBUG| base_utils:0278| [stdout] Command exited with non-zero status 156 ... . The command times out with all failed attempts to scan. Job link : http://cautotest/afe/#tab_id=view_job&object_id=67775064
,
Jul 11 2016
I would expect whirlwind to support scanning on any interface. But, if the network is down, then it's understandable that scanning fails. Do we know why the network is down?
,
Jul 11 2016
Assigning back to bmahadev@ for investigation of why the network is down. (i.e., why the interface is down.)
,
Jul 11 2016
It looks like all interfaces are down by default and am able to run scan after bringing them up with ifconfig. Do we have to scan on each interface to see all networks, since they are 2.4 and 5 ghz only ?
,
Jul 11 2016
I'm not familiar with the network_WiFi_ChaosConnectDisconnect test, and its goals w.r.t. scanning on the AP. krisr@, can I punt Bindu's question (#c4) to you?
,
Jul 11 2016
Actrually i know the purpose of this code, which is to do an initial scan and see how many possible router's are up, by looking at the ssid count. If there are way too many ssids we see then we dont start a new test either because someone else is running a test or because a lot of APs are simple let ON.
,
Jul 11 2016
If we need to differentiate whirlwind interfaces based on frequency this code will need to be updated too: https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/cros/network/chaos_clique_utils.py?l=244 I am not sure if we should look at a generic solution where site_linux_router.py or something handles this. I think there are a lot of places in the code where it assumes any wireless interface can scan both bands.
,
Jul 11 2016
The scans that happen in the rest of the code actually happen on the device which is unaffected. The only place we scan on the packet capturer is here https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/cros/chaos_lib/chaos_runner.py?l=84. Would it help if we bring up both interfaces and scan on them both ? or is the 2.4ghz interface capable of seeing/scanning 5hgz network also ?
,
Jul 11 2016
Whirlwind has three radio: one is 2.4 GHz only, one is 5 GHz only, and one is dual-band (but single stream). Scanning with the dual-band single-stream radio should be sufficient to find networks in both bands.
,
Jul 11 2016
@comment 8 that is not true. If you look at the code that I linked it is passed a capturer which performs the scan. I agree with comment9, as long as the single stream radio gets all of the scan information that should be fine.
,
Jul 11 2016
krisr@: Oh right! that scan is happening on the capturer. IS there a reason why we scan on the capturer not the device ? I kinda remember doing this on the device. Using the aux radio for scanning is a great idea. I can make those changes.
,
Jul 16 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/04d830a19a8e78435c3e5912291df250812408a3 commit 04d830a19a8e78435c3e5912291df250812408a3 Author: Bindu Mahadev <bmahadev@google.com> Date: Thu Jul 14 21:56:37 2016 [Interop_chaos]Fix scanning on the packet capturer. If the packet capturere is a whirwind use the aux radio interface 'wlan2' which is dual band, for scanning purposes. BUG= chromium:623641 TEST=Tested locally Change-Id: I5efa645615190463da068cf047908d94db2f18aa Reviewed-on: https://chromium-review.googlesource.com/360640 Commit-Ready: Bindu Mahadev <bmahadev@chromium.org> Tested-by: Bindu Mahadev <bmahadev@chromium.org> Reviewed-by: Kris Rambish <krisr@chromium.org> [modify] https://crrev.com/04d830a19a8e78435c3e5912291df250812408a3/server/cros/chaos_lib/chaos_runner.py
,
Sep 26 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bmahadev@chromium.org
, Jun 27 2016Status: Assigned (was: Untriaged)