| 8f668216f3a43d60fa50f8e85c6ffa028f270d67 |
|
16-Jul-2015 |
mukesh agrawal <quiche@chromium.org> |
autotest (wifi): support beacon injection on more APs
Some APs won't let us inject beacon frames, unless we
have an AP interface up along with the monitor interface.
To enable beacon injection on such APs, we have
FrameSender set up an AP interface along-side its monitor
interface.
The AP interface isn't necessary for other frame types.
But I'd like to avoid having the code think about that,
if possible.
BUG=chromium:510883
TEST=suite:wifi_matfunc (on new hardware)
TEST=network_WiFi_ConnectionIdentifier (on stumpy)
TEST=network_WiFi_DisconnectClearsIP (on stumpy)
TEST=network_WiFi_ProfileBasic (on stumpy)
TEST=network_WiFi_RoamEndToEnd (on stumpy)
TEST=network_WiFi_ChannelScanDwellTime (on stumpy)
Change-Id: I9b9c60773fd799dee2df3a21316f068fd3eb85ef
Reviewed-on: https://chromium-review.googlesource.com/287305
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Queue: mukesh agrawal <quiche@chromium.org>
Trybot-Ready: mukesh agrawal <quiche@chromium.org>
Tested-by: mukesh agrawal <quiche@chromium.org>
/external/autotest/server/cros/network/frame_sender.py
|
| 194b4585d71052bb706e67eaf7a60f816fae1530 |
|
17-Jun-2015 |
Rebecca Silberstein <silberst@chromium.org> |
autotest (wifi): test malformed probe responses
Add autotest for malformed probe response packets. This test covers
probe responses that include an element with an incorrect tag length.
This test covers a case where a malformed probe response may have been
the cause of a lucas device wifi disconnect. The probe response had
an incorrect length field. This test reproduces the scenario by
triggering a valid probe request. The AP in the test is configured to
repeatedly send out unsolicited (malformed) probe responses. To reduce
test flake, multiple attempts are made to receive a probe response.
The test fails if no probe responses are received, the device
disconnects or if the wifi card resets.
BUG=chromium:498018
TEST=tested on pit and lucas in wifi dev cell
Change-Id: Ib1902ab21503c65ce5028b3395ddf6f37de6888c
Reviewed-on: https://chromium-review.googlesource.com/278251
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Tested-by: Rebecca Silberstein <silberst@chromium.org>
Commit-Queue: Rebecca Silberstein <silberst@chromium.org>
/external/autotest/server/cros/network/frame_sender.py
|
| c4beba05d7e439bfb9e9c7bd28e7d248782a4531 |
|
24-Mar-2014 |
Peter Qiu <zqiu@chromium.org> |
Channel scan dwell time test
This test instructs a router to continually send beacon frames for a
predefined set of BSSes at a specific interval. The BSSes are named
with an index suffix in hex numerical order. The device under test is
instructed to perform a single channel scan while the beacon frames are
being sent by the router. Based on the SSIDs in the scan results, we
can estimate the device dwell time.
BUG=chromium:354685
TEST=Run this test
Change-Id: Ib8034a112b37ba6584a2b1d8009b2126f2dbd5e4
Reviewed-on: https://chromium-review.googlesource.com/191287
Reviewed-by: Paul Stewart <pstew@chromium.org>
Tested-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Peter Qiu <zqiu@chromium.org>
/external/autotest/server/cros/network/frame_sender.py
|