| 1b854e0747723352fa60d107da5ef3662511caf8 |
|
26-Sep-2015 |
Eric Caruso <ejcaruso@chromium.org> |
cros/network/interface: Add Broadcom 4371 device info
Since we are testing out this chip we should have its name show
up instead of treating it like an unknown device.
BUG=None
TEST=Run network_WiFi_RxFrag, make sure the test does not complain
that the wifi device is unrecognized
Change-Id: I4ff5cdf4d9bd260930378db4d58f62e6c0028621
Reviewed-on: https://chromium-review.googlesource.com/302775
Commit-Ready: Eric Caruso <ejcaruso@chromium.org>
Tested-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 3e4e0ab0cc2097523c8554b2f7df6d90f3a8cf7c |
|
14-Jul-2015 |
Filipe Brandenburger <filbranden@chromium.org> |
autotest: Do not fail trying to find the module of wlan0
If the Linux kernel is non-modular and the driver is built into the
kernel, the "driver/module" symlink for that device in sysfs will not
exist.
In that case, fail gracefully by setting the kernel_module field (which
is only used for debugging purposes) to a sensible textual description
indicating that the name of the module is unknown.
BUG=chrome-os-partner:42310
TEST=Ran network_WiFi_SimpleConnect against a machine with a kernel with
drivers linked into the kernel and modules disabled.
Ran suite:wifi_matfunc against a Samus in a wifi cage.
Change-Id: If3b822eef5b62238e4094d0f03b6978354a4a1ba
Reviewed-on: https://chromium-review.googlesource.com/284007
Trybot-Ready: Filipe Brandenburger <filbranden@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Filipe Brandenburger <filbranden@chromium.org>
Tested-by: Filipe Brandenburger <filbranden@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 33bec44544051a82f658569d61c80342e30abff7 |
|
02-Apr-2015 |
Peter Qiu <zqiu@chromium.org> |
network_WiFi_ChannelScanDwellTime: disable wifi device in shill
Disable wifi device in shill to prevent shill and wpa_supplicant
from managing it . This will stop shill and wpa_supplicant from
initiating scans on that device which could interfere with the scans
to be triggered by this test.
BUG=chromium:471792
TEST=Run network_WiFi_ChannelScanDwellTime test
Change-Id: I151da4e66f96d83ac457b2af6d480ea7a91cc140
Reviewed-on: https://chromium-review.googlesource.com/263559
Reviewed-by: Zeping Qiu <zqiu@chromium.org>
Tested-by: Zeping Qiu <zqiu@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| af2fe4d810e1cc2db02a3412af6989793b8527ac |
|
13-Feb-2015 |
Ben Chan <benchan@chromium.org> |
Fix an I/O redirection issue.
autotest_lib.client.common_lib.cros.network.Interface.device_description
has an 'exists' lambda function, which uses `ls` to determine if a path
exists on a local or remote machine. However, the `ls` command uses a
bash specific I/O redirection syntax '&>', which doesn't work when dash
is used. Under dash, `ls foo &> /dev/null` is executed as `ls foo &` and
`> /dev/null` separately. As the latter command always returns 0, the
'exists' function returns True even if the given path doesn't exist.
This CL fixes the issue by using 'test -e' instead.
BUG=chromium:458678
TEST=Run network_WiFi_SimpleConnect.
Change-Id: Id93e3de12f5faaec2c31980249d71ebee03004b7
Reviewed-on: https://chromium-review.googlesource.com/249888
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Ben Chan <benchan@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 3d9780e4991dd7efd0c38108feb0cd8643ecc7d1 |
|
04-Feb-2015 |
Tien Chang <tienchang@google.com> |
Mapping Glimmer's device info with Stonepeak
Got the hex pairs from error messages
while running/failing wifi_perf tests
BUG=None
TEST=Passed wifi_perf
Change-Id: I5763d2a7663d11ec55870c78bda6f6e3cd02cf9a
Reviewed-on: https://chromium-review.googlesource.com/245974
Tested-by: Tien Chang <tienchang@chromium.org>
Reviewed-by: Kris Rambish <krisr@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Tien Chang <tienchang@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 9a63a8bd7e6c6cd49e673f40f1ae40234bea7321 |
|
03-Feb-2015 |
Peter Qiu <zqiu@chromium.org> |
apmanager: add autotest for bridge mode configuration
For testing configuration of the AP in bridge mode, a DHCP server is setup
on one end of the virtual ethernet pair, and the bridge interface is
configured on the othe end. hostapd will also add the AP interface to the
bridge interface, which allows the DHCP server configured on the virtual
etherenet pair to service all DHCP requests coming to the AP interface.
With this approach, the configuration support for virtual ethernet pair
and bridge mode interface are added to SiteLinuxSystem, where a linux
system will support at most one virtual ethernet pair and one bridge
mode interface.
Note that the current Stumpy router image (version b16) doesn't support
bridge mode interface in kernel (CONFIG_BRIDGE is not enabled).
BUG=chromium:448959
TEST=Run apmanager_SimpleConnect.bridge test
Change-Id: Ib462001ec7c4a9fd79ba59a2aa6ed8344a5c3d0b
Reviewed-on: https://chromium-review.googlesource.com/245756
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
Trybot-Ready: Zeping Qiu <zqiu@chromium.org>
Tested-by: Zeping Qiu <zqiu@chromium.org>
Reviewed-by: Zeping Qiu <zqiu@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 21529ce4b0851467ae2ea18c93776b90d1b3a986 |
|
26-Jan-2015 |
Paul Stewart <pstew@chromium.org> |
Add MTU test for DHCP client
Ensure that the DHCP client imports the MTU parameter from the
DHCP config. Also ensure that this parameter modifies the state
of the interface.
BUG=chromium:450759
TEST=Run this test
Change-Id: I471b4c4f124d7400356a71624f09e3fda7aaf89d
Reviewed-on: https://chromium-review.googlesource.com/243315
Reviewed-by: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 6176ca51fadc660fdc8b55e007c05f3f73f3d992 |
|
22-Jan-2015 |
Christopher Grant <cjgrant@google.com> |
Add a utility to return the prioritized default route
Returned is the route's interface name, gateway and routing metric
value.
BUG=None
TEST=Local testing
Change-Id: Iced3ec5b188d33fe22c08bedfabd42c1afef89bd
Reviewed-on: https://chromium-review.googlesource.com/242610
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Tested-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| ae3c07f40dbf695cdb6e72c1c63ed0672a763558 |
|
21-Jan-2015 |
Ben Chan <benchan@chromium.org> |
Handle non-existent vendor/device file in sysfs.
cros.network.Interface.device_description expects the WiFi interface to
expose the 'vendor' and 'device' files via sysfs and throws an exception
if it fails to read the content of those files. This CL modifies
device_description to handle the file read error more gracefully.
BUG=None
TEST=Run network_WiFi_SimpleConnect.
Change-Id: I5c42bcb55f48274abcf66d871946ea18a0c01f45
Reviewed-on: https://chromium-review.googlesource.com/242120
Reviewed-by: Paul Stewart <pstew@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Queue: Ben Chan <benchan@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| b8cf387c8a721668929d15ff506dc0b4a9747e64 |
|
30-Dec-2014 |
Christopher Wiley <wiley@chromium.org> |
autotest: Tolerate no IP address in interface.py
network_WiFi_DisconnectClearsIP expects that Interface will return None
when asked for an IP address on an interface that has None. This was
broken when netblock parsing was refactored to add validation logic.
BUG=chromium:433621
TEST=network_WiFi_DisconnectClearsIP now passes.
Change-Id: I1f302197b2cf37370bccc2fd9b76e3d61b93e4ef
Reviewed-on: https://chromium-review.googlesource.com/238040
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Kris Rambish <krisr@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 659b56f331522190a53716115d60fd3262fc060e |
|
12-Dec-2014 |
Paul Stewart <pstew@chromium.org> |
network_WlanDriver: Add Marvell 8887
Add a configuration for the Marvell 8887.
BUG=None
TEST=network_WlanDriver
Change-Id: I45be22037389ac63a07a61f60092f5e804ee7748
Reviewed-on: https://chromium-review.googlesource.com/235021
Reviewed-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 684878e13d16aa904a6045fca344782497738631 |
|
18-Dec-2014 |
Christopher Wiley <wiley@chromium.org> |
autotest: Validate netblock strings before parsing
Consolidate all construction paths into a single helper function and
do some limited validation of passed in arguments before attempting to
parse them. This should get us more meaningful messages when tests
attempt to use invalid netblock strings in logic.
BUG=chromium:433621
TEST=network_BasicProfileProperties still passes.
Change-Id: Ic5887ed72ddd46b6dd14cb97c8e2f9747eea10ab
Reviewed-on: https://chromium-review.googlesource.com/236656
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| dac0a2ce8be69f8e311f80e6cbe80bd5725475b4 |
|
29-Jul-2014 |
Daniel Kim <dekim@broadcom.com> |
autotest: Correct Broadcom 4356 device ID
Update the device ID of Broadcom 4356 PCIE with correct value(0x43ec).
BUG=chrome-os-partner:30066
TEST=Run this test on 4356-equipped system.
Change-Id: I6fb818d8e19e1547561dc81d92256f2c37623f7e
Reviewed-on: https://chromium-review.googlesource.com/210092
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Daniel Kim <dekim@broadcom.com>
Tested-by: Daniel Kim <dekim@broadcom.com>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 772a8d6f90ca00e6d9d7c1365f1e2fcac870bdb1 |
|
01-Jul-2014 |
Christopher Wiley <wiley@chromium.org> |
Tolerate slightly different WP2 part number in network_WlanDriver
This seems to be a functioning part number, although it is unclear why
it is slightly different from the rest of our boards.
TEST=network_WlanDriver passes against leon (not affected by this
change).
BUG=chromium:387349
Change-Id: I3c5079ed15ca19fab9c7eb95e35d9f955e96386d
Reviewed-on: https://chromium-review.googlesource.com/206162
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 0138fa681700b164747016bc276ca4384d6c6b74 |
|
28-Jun-2014 |
Christopher Wiley <wiley@chromium.org> |
Log WiFi device type to server logs in every WiFi test
This costs us nothing and makes debugging a little easier.
To enable this, make not recognizing a device not be a fatal
error until we hit network_WlanDriver, since some devices (Android)
might not have cards we recognize.
TEST=network_WlanDriver still passes. Normal WiFi tests also pass.
BUG=None
Change-Id: Ic38ca04af9dee69511f3adfaebb87a0a46e7846d
Reviewed-on: https://chromium-review.googlesource.com/206015
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Tested-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| f53fffb46c83431ad30c6aed8ca4b6a23bbdc69c |
|
27-Jun-2014 |
Daniel Kim <dekim@broadcom.com> |
autotest: Add Broadcom 4356 PCIE to network_WlanDriver
Add vendor/product IDs and associate it with the kernel 3.10(wireless-3.8)
driver.
BUG=chrome-os-partner:30066
TEST=Run this test on 4356-equipped system.
Change-Id: I9ad311a6263b4a7d140c40af50b0af83cd41b18b
Reviewed-on: https://chromium-review.googlesource.com/205837
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Daniel Kim <dekim@broadcom.com>
Tested-by: Daniel Kim <dekim@broadcom.com>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 4e1d6e94ad5ba2bc32a4f48523db5ff7fed1b706 |
|
18-Jun-2014 |
Christopher Wiley <wiley@chromium.org> |
Refactor logic to detect DUT WiFi chip type to be usable remotely
BUG=chromium:385942
TEST=network_WlanDriver still passes against my lumpy.
Change-Id: I13c82651178b8deb3069b3a2066051d1804a58e8
Reviewed-on: https://chromium-review.googlesource.com/204394
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Tested-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 9a2e80c01120abd0f4ffa25bfc1e3e59efaad349 |
|
15-Apr-2014 |
Paul Stewart <pstew@chromium.org> |
Fix access to the prefix of the netblock
Trivial typo fix.
BUG=chromium:363492
TEST=Visual
Change-Id: I3a129125715abe184dca7e2a3f2daf110319d0ca
Reviewed-on: https://chromium-review.googlesource.com/194941
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 594570dc4b2a3445054b58e50545416e4bc48f36 |
|
15-Mar-2014 |
Christopher Wiley <wiley@chromium.org> |
Wait for correct IP subnet changes during roaming
This allows roaming tests to pass when run against drivers
that do roaming without involving userspace. In these situations
we're briefly associated with the roaming target before we detect
that our DHCP lease is invalid and re-negotiate the lease. Tolerate
that window by also waiting for the IP address on the WiFi interface
to move to the correct subnet.
Add a library to make common netblock->mask/subnet/broadcast address
calculations. Pull duplicate logic to do this out of interface.py
and site_linux_router.py.
BUG=chromium:352847
TEST=wifi_matfunc continues to pass with this change.
Change-Id: I2e6786514aee533e36eb84e1329f19891d3744ba
Reviewed-on: https://chromium-review.googlesource.com/190173
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| ef7cda0869049ef94031ce2cdf9dbb31de79aa8c |
|
26-Sep-2013 |
Wade Guthrie <wdg@chromium.org> |
Autotest: Adds wifi_noise_level method to wifi_client.
This new method returns the noise level for a specified frequency on
the DUT. Currently, this method only returns valid values for versions
of ChromeOS with drivers that report the value. On other devices, this
method returns None.
While I was there (and due to an excellent code review comment), I
did a tiny refactor to keep from repeating the 'iw' command that checks
a device to see if it's a wifi device.
BUG=None
TEST=manual:
* add a line in an autotest that looks like:
log.logging('NOISE: %r',
self.context.client.wifi_noise_level(frequency))
'frequency' needs to be a valid WiFi frequency.
* on the DUT in a separate window, type 'ifconfig -a'
* Then, using the wifi interface reported by ifconfig, type:
'iw dev <wifi-xface> survey dump'
* Verify that the noise value under the frequency used in the autotest
is about the same (it will vary a little from call to call) as that
reported by the autotest.
Change-Id: I028cd1d0440c6a3ea67245856d0a80b84c9a6223
Reviewed-on: https://chromium-review.googlesource.com/170682
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Wade Guthrie <wdg@chromium.org>
Commit-Queue: Wade Guthrie <wdg@chromium.org>
Tested-by: Wade Guthrie <wdg@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| db16beb49dd1a4bcf98793635d63226019338f8d |
|
22-Aug-2013 |
Christopher Wiley <wiley@chromium.org> |
autotest: Add WiFi signal level property to WiFi client
TEST=A test that consumes this property is able to do so effectively on
daisy.
BUG=chromium:279395
Change-Id: I916492df83e61cedd0fbbaf273c94970bf03e2dd
Reviewed-on: https://chromium-review.googlesource.com/66713
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 61a0e5b9bd692fd76e34f974a5cef400b51ed775 |
|
07-Aug-2013 |
Christopher Wiley <wiley@chromium.org> |
autotest: Fix network_BasicProfileProperties flake
This will now work when the device has multiple ethernet devices.
TEST=Ran this test on a device with multiple ethernet devices. It
passes.
BUG=chromium:268662
Change-Id: I8a74ed82e7a8f7656fcd50cc23c2def8be1c4b0e
Reviewed-on: https://gerrit.chromium.org/gerrit/64972
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| d11c59cc90ebf2a31b9033881b6d3555ce4cb615 |
|
17-Jul-2013 |
Christopher Wiley <wiley@chromium.org> |
autotest: Migrate network_WiFiManager/091_ProfileProperties
Convert this to a client test, since it has no client restarts and
doesn't need a router.
TEST=This is a passing test.
BUG=chromium:259487
Change-Id: I56be3024b4392bd33ebe74c806ce035445f69bea
Reviewed-on: https://gerrit.chromium.org/gerrit/62411
Tested-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| dfd16712628fcd4fb73d94a43588e04abf6a2c8a |
|
29-Apr-2013 |
Tan Gao <tgao@chromium.org> |
Add method to expose wifi interface IP as a propery in WiFiClient.
- looks up a DUT's WLAN interface MAC and IPv4 addresses using interface.py
- add optional host object to interface.py
- expose a DUT's ipv4 address as a property
BUG=chromium:236447
TEST=Manual (added print lines in check11b test to confirm WLAN
ip addr and mac addr are returned correctly)
Change-Id: Ib22c9083648fb2c6f67153bba22d068f28037d14
Reviewed-on: https://gerrit.chromium.org/gerrit/49493
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Tested-by: Tan Gao <tgao@chromium.org>
Commit-Queue: Tan Gao <tgao@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|
| 07f577a1061b2f448e20cead9bde500d51821821 |
|
22-Apr-2013 |
Paul Stewart <pstew@chromium.org> |
Expand tests for 802.1x wired networks
The first version of this test only verified successful
authentication when a) the credentials were available, then
b) an EAP authenticator was detected. The test only
validated by checking the device's authentication state, and
required a relatively long "sleep". This change:
- Fixes the sleep by using shill_proxy's internal
"wait_for_property_in" functionality.
- Checks hostapd's state to make sure the client is actually
authenticated.
- Temporarily removes EAP credentials and makes sure hostapd
receives an EAPOL logout event, then re-authenticates.
- While here, move IP and MAC address querying out to a new
separate module that can be shared.
CQ-DEPEND=CL:48803
BUG=chromium:234290
TEST=This is a test. Also run network_DhcpNegotiationSuccess for
regression testing of IP address query functions.
Change-Id: I76dd4f0753986914824e0cdcbcf3583d08a4f7cb
Reviewed-on: https://gerrit.chromium.org/gerrit/48806
Commit-Queue: Paul Stewart <pstew@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
/external/autotest/client/common_lib/cros/network/interface.py
|