Mac80211 : Wpa rekeying issue
Hi, My test plateform is: 2 equipements Both equipment used compat version 2015-07-21 from openwrt. Both equipment used security WPA2 The equipment #1 is an AP. The Group rekey interval is set to 3601s The Pair rekey interval set to 50s (I reduced this value to show the issue often) The Master rekey interval is set to 86400 s. The equipment #2 is a sta+wds I used a 5GHz channel to have a free channel (without other AP) I connected a computer on each equipment. To reproduce the issue: I ran iperf udp@50Mbps from computer connected to the AP to the computer connected to the sta. After several WPA2 rekeying, iperf server side didn't received any frame. I investigated in the driver. All packets are dropped in sta side, because the function ieee80211_crypto_ccmp_decrypt return Rx_DROP_UNUSABLE. This function return this code because the test if(memcmp(pn,key->u.ccmp.rx_pn[queue],IEEE8021_CCMP_PN_LEN) <=0) return true. Have you any idea to fix this issue? Thanks for your help. Cedric. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Mac80211 driver crash in monitor mode
Hi,
I'm using mac80211/ATH9K driver in monitor mode to inject some packets.
With the latest driver version my packet injector software generated a
kernel panic.
The reason of this crash is:
In mac80211/tx.c, function __ieee80211_tx:
case NL80211_IFTYPE_MONITOR:
if (sdata->u.mntr_flags & MONITOR_FLAG_ACTIVE) {
vif = &sdata->vif;
break;
}
sdata = rcu_dereference(local->monitor_sdata);
if (sdata) {
vif = &sdata->vif;
info->hw_queue =
vif->hw_queue[skb_get_queue_mapping(skb)];
} else if (ieee80211_hw_check(&local->hw,
QUEUE_CONTROL)) {
ieee80211_purge_tx_queue(&local->hw, skbs);
return true;
} else
vif = NULL;
break;
If I don't enable the MONITOR_FLAG_ACTIVE I'm going to the line vif =
null, this function will continue and will call ieee80211_tx_frags and
this function will call ieee80211_drv_tx.
In ieee80211_drv_tx function:
if (pubsta) {
u8 tid = skb->priority & IEEE80211_QOS_CTL_TID_MASK;
txq = pubsta->txq[tid];
} else if (vif) {
txq = vif->txq;
}
In my case pubsta == null so I'm going to else statement. The line
vif->txq generate kernel pannic because the VIF pointer have been
initialized to null in __ieee80211_tx function.
Do you have any suggestion to fix this crash?
Cedric Voncken.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ATH10K VLAN firmware issue
I'm testing to transmit frame with 802.1q tag (VLAN). My client is set in STA + WDS and the netdev is bridged with eth0. I have a computer with vlan configuration set connected to the STA eth0. If I try to transmit frames with 802.1q tag, the frames are not sent. I checked with wireless sniffer, and I don't see the frame with VLAN tag (the frames without VLAN tag are sent). I tested with firmware 10.2.4.70.14-2 from kale github, 10.1.467-ct-com-full-015 from candelatech and 10.2.4.70-2 from openwrt, and in all cases I have the same issue. Thanks for your help. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ATH10 firmware question
Hi, I have a simple test platform. One PC connected to an equipment. This equipment is set in AP mode. Another PC connected to another equipment. This equipment is set in STA + WDS mode. Both equipment use the same openwrt Firmware (compat 2015-07-21), I only changed the ath10k firmware (in /lib/firmware/ath10k/...). Both equipment has the same hardware. I used a clear channel, and VHT80. The radio was connected with a coaxial cable and I placed 40 dBm attenuation per Rf chain. I used the WLN350NX radio card from compex. First test : ATH10K firmware 10.2.4.70-2 on both equipment An iperf from PC connected to the AP to the PC connected to the STA give 919 Mbps. An iperf from PC connected to the STA to the PC connected to the AP give 500 Mbps. Second test : ATHK firmware 10.2.4.70.10-2 on both equipment An iperf from PC connected to the AP to the PC connected to the STA give 921 Mbps. An iperf from PC connected to the STA to the PC connected to the AP give 441 Mbps. If I cross the computer I have the same result. I did several time these test and I always have the same result. Is it the expected result? What is the recommanded firmware version for each mode? Thanks for your help. Cedric Voncken. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Ath10K issue
I'm using compat-wireless 2015-03-09 from openwrt. At the power up, these equipments worked in AP mode and several sta can do an association. Randomly it is not possible to make association to several AP. If I look the log file I see cyclically these error messages. Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.116104] ath10k_warn: 186 callbacks suppressed Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.133185] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.153058] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.157255] ath10k_pci 0001:02:00.0: reached WMI management transmit queue limit Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.157260] ath10k_pci 0001:02:00.0: failed to transmit packet, dropping: -16 Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.212297] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.232087] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.252874] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.286774] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.320914] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon Wed Sep 9 10:29:49 2015 kern.warn kernel: [17654.355043] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.167694] ath10k_warn: 193 callbacks suppressed Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.184778] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.204514] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.225098] ath10k_pci 0001:02:00.0: reached WMI management transmit queue limit Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.235968] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.264524] ath10k_pci 0001:02:00.0: failed to transmit packet, dropping: -16 Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.270094] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.303945] ath10k_pci 0001:02:00.0: failed to transmit management frame via WMI: -11 Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.304408] ath10k_pci 0001:02:00.0: reached WMI management transmit queue limit Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.304414] ath10k_pci 0001:02:00.0: failed to transmit packet, dropping: -16 Wed Sep 9 10:29:54 2015 kern.warn kernel: [17659.363876] ath10k_pci 0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon Wed Sep 9 10:29:59 2015 kern.warn kernel: [17664.219316] ath10k_warn: 208 callbacks suppressed To reestablish my access point I need to restart the Wifi (wifi up in openwrt). Have you any idea of this issue? Regards. Cédric Voncken. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ATH10K and VLAN
I'm testing to send a VLAN frame through ATH10K device. I'm using compat wireless 2015-03-09 from openWRT. The ATH10K firmware used is 10.2.4.45 My test platform is: Pc1 : IP 10.101.4.3 (without VLAN) VLAN 1 : IP 192.168.5.1 Equipment in AP mode. The netdev is bridged with eth0 Equipment in client mode with WDS mode enables. The client is connected to the AP. The netdev is bridged with eth0. AP and client use ATH10K wireless card. PC2: IP 10.101.4.4 (without VLAN) VLAN 1 : IP 192.168.5.2 The PC1 is connected to the equipment in AP mode and the PC2 is connected to the equipment in client mode. I can ping from PC1 to PC2 without vlan (ping 10.101.4.4). I cannot ping from PC1 to PC2 with VLAN. With tcpdump I checked the vlan frame is sent to the netdev but this frame is not send to the air. Is it possible to send a VLAN frame through ATH10K? If no, is it a driver limitation or firmware limitation? Thanks for your help. Cédric. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[mac80211]synchronize_net call in ieee_tx_ba_session_handle_start
The synchronize_net called in function ieee_tx_ba_session_handle_start generate a jiter after the association. I can observe a long period (100ms or more) where no data are sent because mac80211 is blocked in synchronize_net. My product has several network interface and processor with 4 cores. If I understood correctly, in case we use the ath9k driver, the function drv_ampdu_action will call the ath_tx_aggr_start and this function will flush the tx pending packet and return the next sequence number. So in this case it is not necessary to call this function. Is it possible to remove this function, or I need to consider another case? Thanks for your help. Cedric Voncken. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ath10k: What will happens when radar is detected ?
In 802.11ac standard, it is possible to dynamically reduce the channel width used. My question is: If I use a channel with 80 or 40 MHz width, what will happen if I detect radar? The ath10k card/driver reduces automatically the channel width. Cedric Voncken. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ARP dropped during WPA handshake
My test plateforme is very simple, One sta (with openwrt), one AP and a computer connected to the AP. I launch iperf on the sta and power up the AP. With wireshark I can observe 1 s delay between the frame EAPOL 4/4 and the arp request sent by the sta. I can observe the delay only if my sta uses architecture with more 1 cpu. When the sta received the Authentication response, mac80211 sets the iface on UP state. This state allows wpa_supplicant to send the EAPOL frame for WPA handshake but other frames are dropped. If an arp request is sent by the local ip stack during the WPA handshake this arp will be dropped and we need to wait the end of arp timeout (1 s). Have you any suggestion / pointer to fix this issue? Thanks for your help. Cedric Voncken -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ARP dropped during WPA handshake
My test plateforme is very simple, One sta (with openwrt), one AP and a computer connected to the AP. I launch iperf on the sta and power up the AP. With wireshark I can observe 1 s delay between the frame EAPOL 4/4 and the arp request sent by the sta. I can observe the delay only if my sta uses architecture with more 1 cpu. When the sta received the Authentication response, mac80211 sets the iface on UP state. This state allows wpa_supplicant to send the EAPOL frame for WPA handshake but other frames are dropped. If an arp request is sent by the local ip stack during the WPA handshake this arp will be dropped and we need to wait the end of arp timeout (1 s). Have you any suggestion / pointer to fix this issue? Thanks for your help. Cedric Voncken -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Question : WMM queue management in AP role
Hi all, The AP role can manage several sta. In case of WMM, each sta have a separate queue or all sta use the same queue? Where can I found any information on the WMM queue management in linux wireless? I'm using ath9k driver. Cedric Voncken -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ath10k firmware crash
Hi all, I'm trying to use ath10k in client mode and AP mode with 2 wireless cards (Ap on one card and client on another card). The AP mode work, but the client mode always crash. Please find below the ath10k crash information [ 79.131301] ath10k: hardware name qca988x hw2.0 version 0x4100016c [ 79.149420] ath10k: firmware version: 999.999.0.636 [ 79.167248] ath10k: target register Dump Location: 0x0040AC14 [ 79.185939] ath10k: target Register Dump [ 79.201804] ath10k: [00]: 0x4100016C 0x 0x009C4521 0x [ 79.220184] ath10k: [04]: 0x009C4521 0x00060330 0x0019 0x00955A00 [ 79.238566] ath10k: [08]: 0xD0CE 0x 0x0040CC94 0x0020 [ 79.256945] ath10k: [12]: 0x 0x 0x00958360 0x0095836B [ 79.275327] ath10k: [16]: 0x809A0978 0x0040AD94 0x00439304 0x0040D074 [ 79.293706] ath10k: [20]: 0x 0x 0x0041EFB8 0x [ 79.312086] ath10k: [24]: 0x809A0978 0x0040AD94 0x00439304 0x0343389A [ 79.330466] ath10k: [28]: 0x809AD1A2 0x0040ADE4 0x00439304 0x0043F68C [ 79.348845] ath10k: [32]: 0x809B01DA 0x 0x00410110 0x0041937C [ 79.367224] ath10k: [36]: 0x 0x 0x 0x [ 79.385604] ath10k: [40]: 0x 0x 0x0071 0x00412700 [ 79.403984] ath10k: [44]: 0x00439BB8 0x 0x 0x0040 [ 79.422364] ath10k: [48]: 0x809AE0B4 0x0040AE04 0x0040 0x0043F68C [ 79.440744] ath10k: [52]: 0x0001 0x 0x004231F0 0x0040 [ 79.459124] ath10k: [56]: 0x809AE17E 0x0040AE44 0x0040FE6C 0x0040D310 I'm using openwrt, and I have the same problem with/without configuration option "Firmware optimized for sta operation". Is it possible to use at the same time on 2 different cards the AP mode and client mode? Cedric Voncken -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ath9k: DFS pattern detector and ETSI EN 301 893 V1.7.1
Hi, I will test my equipment with the ETSI standard EN 301 893 1.7.1. I looked the DFS pattern detector set in ath9k driver and the "comment specifies" it compliant with the ETSI standard in V1.5.1. If I correctly understood the ath9k source code and the ETSI EN 301 893 standard, the table D.3 and D.4 in Annexes D of ETSI standard it uses to fill the ETSI_radar_ref_types_v15 structure. The difference between these tables in EN 301 893 v1.5.1 and EN 301 893 v1.7.1 is only the minimal pulse width (from 0.8 to 0.5). This value is set to 0 in many structure fields. Could you confirm the ETSI ath9k pattern detector is compatible with the ETSI EN 301 893 v1.7.1 standard? If it is right, I will send a patch to precise that in ath9k comment. Thanks for your help. Cedric Voncken -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
