No wifi in A-Lab |
||||
Issue descriptionIssue 789523 and issue 791085 track how the test case that confirms wifi is up and available had to be turned off because there is no wifi in lab a. However from b/65431593 I see that wifi was marked as up and available on Oct 23. Vince can you please take a look? This is blocking some of our iOS11 testing because some of those devices are only in a lab.
,
Dec 4 2017
I'll take a look
,
Dec 4 2017
It's working.
From my laptop:
$ ./airport -I
agrCtlRSSI: -52
agrExtRSSI: 0
agrCtlNoise: -96
agrExtNoise: 0
state: running
op mode: station
lastTxRate: 450
maxRate: 450
lastAssocStatus: 0
802.11 auth: open
link auth: wpa2-psk
BSSID: a8:bd:27:bc:9f:b0
SSID: WL-chromelab
MCS: 23
channel: 161,-1
$ ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 3c:15:c2:b7:e9:8a
inet6 fe80::146b:4a54:e467:4ead%en0 prefixlen 64 secured scopeid 0x4
inet 100.107.220.102 netmask 0xffffffc0 broadcast 100.107.220.127
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
$ cat /etc/resolv.conf
#
# Mac OS X Notice
#
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
#
# This file is automatically generated.
#
search corp.google.com prod.google.com prodz.google.com google.com
nameserver 100.107.220.122
,
Dec 4 2017
I see that wifi is not enabled on any of the ios devices in the a-lab. Let me fix that.
,
Dec 4 2017
,
Dec 4 2017
All devices attached to build{1..16]-a7 are now connected to WL_chromelab
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vhang@chromium.org
, Dec 4 2017