#18408: Connection as STA via ath10k fails for AP running CC but works for Zyxel
firmware
-----------------------+------------------------
 Reporter:  anonymous  |      Owner:  developers
     Type:  defect     |     Status:  new
 Priority:  normal     |  Milestone:
Component:  kernel     |    Version:  Trunk
 Keywords:             |
-----------------------+------------------------
 Hi,

 I have two Zyxel NBG6716 devices running CC r43392- one as AP and one as
 STA (with STA firmware) and try to connect them via IEEE 802.11ac (wlan0).

 Now I observe the following (reproducible) behaviour: in case I connect to
 the CC AP, my client says:
 {{{

 [  131.530000] wlan0: authenticate with ec:43:f6:f9:ab:09
 [  131.530000] ------------[ cut here ]------------
 [  131.540000] WARNING: CPU: 0 PID: 1258 at /home/lui/openwrt/trunk-
 nbg6716/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_nand
 /compat-wireless-2014-11-04/net/mac80211/sta_info.c:453
 sta_info_insert_rcu+0x84/0xd8 [mac80211]()
 [  131.560000] Modules linked in: pppoe ppp_async iptable_nat ath9k pppox
 ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_MASQUERADE
 ath9k_common xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac
 xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT
 slhc nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv6 nf_defrag_ipv4
 nf_conntrack_irc nf_conntrack_ftp nf_conntrack iptable_raw iptable_mangle
 iptable_filter ipt_REJECT ip_tables crc_ccitt ath9k_hw ath10k_pci
 ath10k_core ath mac80211 cfg80211 compat ip6t_REJECT ip6table_raw
 ip6table_mangle ip6table_filter ip6_tables x_tables ipv6 arc4
 crypto_blkcipher gpio_button_hotplug
 [  131.620000] CPU: 0 PID: 1258 Comm: iw Tainted: G        W    3.14.18 #3
 [  131.620000] Stack : 00000000 00000000 00000000 00000000 803fc146
 0000003b 807a6c58 00000008
 [  131.620000]    80339198 8038dc7f 000004ea 803f3bfc 807a6c58 00000008
 807c4ae0 00000000
 [  131.620000]    807c5f70 802d4f0c 00000003 8020e5d0 000001c5 00000008
 8033c360 8e56b7f4
 [  131.620000]    00000000 00000000 00000000 00000000 00000000 00000000
 00000000 00000000
 [  131.620000]    00000000 00000000 00000000 00000000 00000000 00000000
 00000000 8e56b780
 [  131.620000]    ...
 [  131.660000] Call Trace:
 [  131.660000] [<8024cd3c>] show_stack+0x48/0x70
 [  131.670000] [<802e76c8>] warn_slowpath_common+0x84/0xb4
 [  131.670000] [<802e7780>] warn_slowpath_null+0x18/0x24
 [  131.680000] [<8f60440c>] sta_info_insert_rcu+0x84/0xd8 [mac80211]
 [  131.680000] [<8f604470>] sta_info_insert+0x10/0x6a4 [mac80211]
 [  131.690000] [<8f630610>] ieee80211_ap_probereq_get+0x1208/0x127c
 [mac80211]
 [  131.700000]
 [  131.700000] ---[ end trace c608d13aeb3906b9 ]---
 [  131.700000] wlan0: failed to insert STA entry for the AP (error -22)
 }}}

 However, an AP running the original Zyxel firmware results for the client
 in:

 {{{
 [   27.250000] wlan0: authenticate with fc:f5:28:d3:ab:51
 [   27.260000] wlan0: send auth to fc:f5:28:d3:ab:51 (try 1/3)
 [   27.270000] wlan0: authenticated
 [   27.300000] wlan0: associate with fc:f5:28:d3:ab:51 (try 1/3)
 [   27.380000] wlan0: RX AssocResp from fc:f5:28:d3:ab:51 (capab=0x401
 status=0 aid=1)
 [   27.410000] wlan0: associated
 [   27.440000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
 [   27.450000] wlan0: Limiting TX power to 17 (20 - 3) dBm as advertised
 by fc:f5:28:d3:ab:51
 }}}
 and I am connected:
 {{{
 root@OpenWrt-13:~# iw dev wlan0 link
 Connected to fc:f5:28:d3:ab:51 (on wlan0)
         SSID: ikt80211ac_03
         freq: 5180
         RX: 159989 bytes (1116 packets)
         TX: 1190 bytes (11 packets)
         signal: -37 dBm
         tx bitrate: 6.0 MBit/s

         bss flags:      short-slot-time
         dtim period:    1
         beacon int:     100
 }}}

--
Ticket URL: <https://dev.openwrt.org/ticket/18408>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to