New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 751303 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

whirlwind testlab-ap: AP should not prevent HT/VHT

Project Member Reported by kirtika@google.com, Aug 1 2017

Issue description

Seeing this in recent Caroline testlab runs.
The "disabling HT/VHT as WMM/QoS is not supported by the AP" is not reassuring since Intel devices (esp. StP2) tend to pick VHT rates
in the field wherever possible, so we are not testing the correct
config.

2017-08-01T20:25:27.338517+00:00 INFO kernel: [  459.498138] smsc75xx 1-2.3:1.0 eth0: link up, 1000Mbps, full-duplex, lpa 0xC1E1
2017-08-01T20:25:27.341548+00:00 INFO kernel: [  459.501143] smsc75xx 1-2.3:1.0 eth0: link up, 1000Mbps, full-duplex, lpa 0xC1E1
2017-08-01T20:25:27.912885+00:00 INFO kernel: [  460.072443] wlan0: authenticate with 30:b5:c2:34:08:c1
2017-08-01T20:25:27.919550+00:00 INFO kernel: [  460.078642] wlan0: send auth to 30:b5:c2:34:08:c1 (try 1/3)
2017-08-01T20:25:27.924483+00:00 INFO kernel: [  460.084388] wlan0: authenticated
2017-08-01T20:25:27.926617+00:00 INFO kernel: [  460.085554] iwlwifi 0000:01:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
2017-08-01T20:25:27.926637+00:00 INFO kernel: [  460.085605] iwlwifi 0000:01:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
2017-08-01T20:25:27.926640+00:00 INFO kernel: [  460.085634] iwlwifi 0000:01:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
2017-08-01T20:25:27.926642+00:00 INFO kernel: [  460.086734] wlan0: associate with 30:b5:c2:34:08:c1 (try 1/3)
2017-08-01T20:25:27.931473+00:00 INFO kernel: [  460.091080] wlan0: RX AssocResp from 30:b5:c2:34:08:c1 (capab=0x411 status=0 aid=1)
2017-08-01T20:25:27.933479+00:00 INFO kernel: [  460.092919] wlan0: associated
2017-08-01T20:25:28.540045+00:00 INFO avahi-daemon[2835]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.

 
Components: OS>Systems>Network
What test were you running? Looks like at least part of this is complaining due to non-ideal security configuration ("WEP/TKIP use").
IIRC, 802.11 disallows the use of WEP/TKIP for higher data rate connections. So only "open" and "WPA-2" are valid for 802.11n and 802.11ac.

(However, I believe many APs fail to enforce this requirement.)

Comment 3 by yoshi@chromium.org, Jan 3 2018

Cc: -yoshi@chromium.org
Labels: Enterprise-Triaged

Sign in to add a comment