Access Point wifi connection that hangs up


#1

Hello,

I am trying to set up a reliable connection between two DB410c (for which one will be the Access Point (AP)).

The AP configuration uses hostapd, for which the configuration file is the following:

interface=wlan0
ssid=myDragonAP
hw_mode=g
wpa=2
wpa_passphrase=12345678
wpa_key_mgmt=WPA-PSK
channel=10
macaddr_acl=0
auth_algs=3
driver=nl80211
ieee80211n=1
wmm_enabled=1
beacon_int=100
rsn_pairwise=CCMP
wpa_pairwise=CCMP
ignore_broadcast_ssid=0

while the dnsmasq configuration is the following:

interface=wlan0
dhcp-authoritative
dhcp-range=192.168.10.10,192.168.10.150,255.255.255.0,24h

The problem I noticed that sometimes (actually it’s just happened while I am writing), from the client, I loose connection with the access point.
The client connects to the AP using wpa_supplicant, simply generated with wpa_passphrase:

network={
	ssid="myDragonAP"
	#psk="12345678"
	psk=acaef7241b2922cd975d75baf6a0a905cff4179604cf8854328522ea1e30a5e8
}

but I think the problem is related with the AP configuration.
Do you have any suggestion for my problem ?

EDIT: the following is the output of dmesg after AP hangs up:

[ 1215.305416] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[ 1218.181315] wcn36xx: WARNING STA with addr 02:00:26:c9:2d:18 and index 0 not found

I also will try to figure out if this can be a problem of antennas coupling (since the AP is very near to the client).

Thank you in advcance.
Simon


Wcn36xx AP Dropout
#2

Just seen this bug report:

https://bugs.96boards.org/show_bug.cgi?id=319

Simon


#3

Have you switched to the new 18.01 release? IIRC there are some fairly significant WiFi fixes in this release, mostly linked to problems during scans for new base stations coming into/out-of range.


#4

Hello @danielt,

To which software or distribution version are you referring to ?
The Debian release seems to be the same I am using, #283:
http://builds.96boards.org/releases/dragonboard410c/linaro/debian/latest/

Regards,
Simon


#5

That’s not the right server anymore…

http://releases.linaro.org/96boards/dragonboard410c/linaro/debian/latest/


#6

btw could you try disabling group rekeying in hostapd config file (wpa_group_rekey=0) and see if connection is more stable.


#7

Hi Simon

Sorry for the slightly brusque (maybe even graceless) reply yesterday. Since posting I have since realized that the documentation was out of date and that the transition to the new server was half-hearted at best.

We are working on fixing it (once we do that mistakes can go back to being the user’s fault again :wink: ).

Daniel.


#8

@danielt no problem. Thank you for your helpful support.

Thanks also to @Loic.
I am going to make the required tests.

Regards,
Simon


#9

Hi again !

I made a few test and I am going to report the results here…

Test #1
I tried the suggestion of @Loic to add wpa_group_rekey=0 to /etc/hostapd.conf using the #283 release, but the connection hungs again.

Test #2
I tried the last distribution as @danielt suggested (of course I recompiled the kernel to have the 4.14.15 following the 359’s instructions).
The driver’s bug seems to be still there (dmesg output):

[   10.343846] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   10.471123] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   12.003987] Bluetooth: hci0 command 0xfc0b tx timeout
[   19.321620] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[   21.084009] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[   22.447593] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[  244.023149] random: crng init done

In fact, after I run the AP, I am able to connect, but the connection remains stable for a few ms (the times of 3/4 pings). This is the output of the pings from my workstation to the Dragonboard AP:

:~$ ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=0.627 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=64 time=1.06 ms

From 192.168.10.130 icmp_seq=55 Destination Host Unreachable
From 192.168.10.130 icmp_seq=56 Destination Host Unreachable
From 192.168.10.130 icmp_seq=57 Destination Host Unreachable
From 192.168.10.130 icmp_seq=58 Destination Host Unreachable
From 192.168.10.130 icmp_seq=59 Destination Host Unreachable
From 192.168.10.130 icmp_seq=60 Destination Host Unreachable
From 192.168.10.130 icmp_seq=61 Destination Host Unreachable
From 192.168.10.130 icmp_seq=68 Destination Host Unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.10.1: icmp_seq=103 ttl=64 time=2.16 ms
64 bytes from 192.168.10.1: icmp_seq=104 ttl=64 time=2.09 ms
64 bytes from 192.168.10.1: icmp_seq=105 ttl=64 time=1.09 ms
64 bytes from 192.168.10.1: icmp_seq=106 ttl=64 time=1.04 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.10.1: icmp_seq=159 ttl=64 time=2.04 ms
64 bytes from 192.168.10.1: icmp_seq=160 ttl=64 time=0.906 ms
64 bytes from 192.168.10.1: icmp_seq=161 ttl=64 time=1.02 ms
64 bytes from 192.168.10.1: icmp_seq=162 ttl=64 time=1.20 ms
From 192.168.10.130 icmp_seq=212 Destination Host Unreachable
From 192.168.10.130 icmp_seq=213 Destination Host Unreachable
From 192.168.10.130 icmp_seq=214 Destination Host Unreachable
From 192.168.10.130 icmp_seq=215 Destination Host Unreachable
From 192.168.10.130 icmp_seq=216 Destination Host Unreachable
From 192.168.10.130 icmp_seq=217 Destination Host Unreachable
From 192.168.10.130 icmp_seq=218 Destination Host Unreachable
From 192.168.10.130 icmp_seq=219 Destination Host Unreachable
From 192.168.10.130 icmp_seq=220 Destination Host Unreachable
From 192.168.10.130 icmp_seq=221 Destination Host Unreachable
From 192.168.10.130 icmp_seq=222 Destination Host Unreachable
From 192.168.10.130 icmp_seq=223 Destination Host Unreachable
From 192.168.10.130 icmp_seq=224 Destination Host Unreachable
From 192.168.10.130 icmp_seq=225 Destination Host Unreachable
From 192.168.10.130 icmp_seq=226 Destination Host Unreachable
From 192.168.10.130 icmp_seq=227 Destination Host Unreachable
From 192.168.10.130 icmp_seq=228 Destination Host Unreachable
From 192.168.10.130 icmp_seq=229 Destination Host Unreachable
From 192.168.10.130 icmp_seq=234 Destination Host Unreachable
From 192.168.10.130 icmp_seq=235 Destination Host Unreachable
From 192.168.10.130 icmp_seq=236 Destination Host Unreachable
From 192.168.10.130 icmp_seq=237 Destination Host Unreachable
From 192.168.10.130 icmp_seq=238 Destination Host Unreachable
From 192.168.10.130 icmp_seq=239 Destination Host Unreachable
From 192.168.10.130 icmp_seq=240 Destination Host Unreachable
From 192.168.10.130 icmp_seq=241 Destination Host Unreachable
From 192.168.10.130 icmp_seq=242 Destination Host Unreachable
From 192.168.10.130 icmp_seq=243 Destination Host Unreachable
From 192.168.10.130 icmp_seq=244 Destination Host Unreachable
From 192.168.10.130 icmp_seq=245 Destination Host Unreachable
From 192.168.10.130 icmp_seq=249 Destination Host Unreachable
From 192.168.10.130 icmp_seq=250 Destination Host Unreachable
From 192.168.10.130 icmp_seq=251 Destination Host Unreachable
From 192.168.10.130 icmp_seq=252 Destination Host Unreachable
From 192.168.10.130 icmp_seq=253 Destination Host Unreachable
From 192.168.10.130 icmp_seq=254 Destination Host Unreachable
From 192.168.10.130 icmp_seq=255 Destination Host Unreachable
From 192.168.10.130 icmp_seq=258 Destination Host Unreachable
From 192.168.10.130 icmp_seq=261 Destination Host Unreachable
From 192.168.10.130 icmp_seq=264 Destination Host Unreachable
From 192.168.10.130 icmp_seq=265 Destination Host Unreachable
From 192.168.10.130 icmp_seq=267 Destination Host Unreachable
From 192.168.10.130 icmp_seq=270 Destination Host Unreachable
From 192.168.10.130 icmp_seq=273 Destination Host Unreachable
From 192.168.10.130 icmp_seq=274 Destination Host Unreachable
From 192.168.10.130 icmp_seq=275 Destination Host Unreachable
From 192.168.10.130 icmp_seq=279 Destination Host Unreachable
From 192.168.10.130 icmp_seq=280 Destination Host Unreachable
From 192.168.10.130 icmp_seq=281 Destination Host Unreachable
From 192.168.10.130 icmp_seq=282 Destination Host Unreachable
From 192.168.10.130 icmp_seq=285 Destination Host Unreachable
From 192.168.10.130 icmp_seq=288 Destination Host Unreachable
From 192.168.10.130 icmp_seq=289 Destination Host Unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.10.1: icmp_seq=311 ttl=64 time=2.26 ms
64 bytes from 192.168.10.1: icmp_seq=312 ttl=64 time=1.08 ms
64 bytes from 192.168.10.1: icmp_seq=313 ttl=64 time=1.14 ms
From 192.168.10.130 icmp_seq=342 Destination Host Unreachable
From 192.168.10.130 icmp_seq=343 Destination Host Unreachable
From 192.168.10.130 icmp_seq=344 Destination Host Unreachable
From 192.168.10.130 icmp_seq=345 Destination Host Unreachable
From 192.168.10.130 icmp_seq=349 Destination Host Unreachable
From 192.168.10.130 icmp_seq=350 Destination Host Unreachable
From 192.168.10.130 icmp_seq=351 Destination Host Unreachable
From 192.168.10.130 icmp_seq=355 Destination Host Unreachable
From 192.168.10.130 icmp_seq=356 Destination Host Unreachable
From 192.168.10.130 icmp_seq=357 Destination Host Unreachable
From 192.168.10.130 icmp_seq=358 Destination Host Unreachable
From 192.168.10.130 icmp_seq=364 Destination Host Unreachable
From 192.168.10.130 icmp_seq=365 Destination Host Unreachable
From 192.168.10.130 icmp_seq=366 Destination Host Unreachable
From 192.168.10.130 icmp_seq=367 Destination Host Unreachable
From 192.168.10.130 icmp_seq=368 Destination Host Unreachable
From 192.168.10.130 icmp_seq=369 Destination Host Unreachable
From 192.168.10.130 icmp_seq=370 Destination Host Unreachable
From 192.168.10.130 icmp_seq=371 Destination Host Unreachable
From 192.168.10.130 icmp_seq=373 Destination Host Unreachable
From 192.168.10.130 icmp_seq=374 Destination Host Unreachable
From 192.168.10.130 icmp_seq=376 Destination Host Unreachable
From 192.168.10.130 icmp_seq=377 Destination Host Unreachable
From 192.168.10.130 icmp_seq=378 Destination Host Unreachable
From 192.168.10.130 icmp_seq=382 Destination Host Unreachable
From 192.168.10.130 icmp_seq=383 Destination Host Unreachable
From 192.168.10.130 icmp_seq=384 Destination Host Unreachable
From 192.168.10.130 icmp_seq=388 Destination Host Unreachable
From 192.168.10.130 icmp_seq=389 Destination Host Unreachable
From 192.168.10.130 icmp_seq=390 Destination Host Unreachable
From 192.168.10.130 icmp_seq=391 Destination Host Unreachable
From 192.168.10.130 icmp_seq=394 Destination Host Unreachable
From 192.168.10.130 icmp_seq=395 Destination Host Unreachable
From 192.168.10.130 icmp_seq=400 Destination Host Unreachable
From 192.168.10.130 icmp_seq=403 Destination Host Unreachable
From 192.168.10.130 icmp_seq=404 Destination Host Unreachable
From 192.168.10.130 icmp_seq=405 Destination Host Unreachable
From 192.168.10.130 icmp_seq=406 Destination Host Unreachable
From 192.168.10.130 icmp_seq=407 Destination Host Unreachable
From 192.168.10.130 icmp_seq=408 Destination Host Unreachable
From 192.168.10.130 icmp_seq=409 Destination Host Unreachable
From 192.168.10.130 icmp_seq=410 Destination Host Unreachable
From 192.168.10.130 icmp_seq=412 Destination Host Unreachable
From 192.168.10.130 icmp_seq=413 Destination Host Unreachable
From 192.168.10.130 icmp_seq=414 Destination Host Unreachable
From 192.168.10.130 icmp_seq=418 Destination Host Unreachable
From 192.168.10.130 icmp_seq=419 Destination Host Unreachable
From 192.168.10.130 icmp_seq=420 Destination Host Unreachable
From 192.168.10.130 icmp_seq=424 Destination Host Unreachable
From 192.168.10.130 icmp_seq=425 Destination Host Unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.10.1: icmp_seq=452 ttl=64 time=2.25 ms
64 bytes from 192.168.10.1: icmp_seq=453 ttl=64 time=1.08 ms
64 bytes from 192.168.10.1: icmp_seq=454 ttl=64 time=1.03 ms
64 bytes from 192.168.10.1: icmp_seq=455 ttl=64 time=28.6 ms
From 192.168.10.130 icmp_seq=484 Destination Host Unreachable
From 192.168.10.130 icmp_seq=485 Destination Host Unreachable
From 192.168.10.130 icmp_seq=486 Destination Host Unreachable
From 192.168.10.130 icmp_seq=487 Destination Host Unreachable
From 192.168.10.130 icmp_seq=488 Destination Host Unreachable
From 192.168.10.130 icmp_seq=489 Destination Host Unreachable
^C
--- 192.168.10.1 ping statistics ---
491 packets transmitted, 17 received, +117 errors, 96% packet loss, time 501277ms
rtt min/avg/max/mdev = 0.627/2.989/28.688/6.446 ms, pipe 4

From this sequence we can see as I can connect, 3 / 4 pings later the connection hangs up (Destination Host Unreachable), I manually try reconnection (ping: sendmsg: Network is unreachable) and again, 3 / 4 pings connected and the connection hangs up again.

The documentation says that the release comes with “Many improvements to the WLAN driver, which drastically improve the stability of WLAN and BT.”

Is it possible that my hostapd configuration is not optimal ?
Am I the only one experiencing these issues ?

EDIT: The behavior described for the last distro seems to be different than a Dragonboard410c connected as a client to the Dragonboard410c AP… I mean that I experience the described issue of ping failing from my workstation (possibly due to desktop network manager software…).

Now I am testing the lest distro AP with a Dragonboard wifi client as well to check if hangs again or not.

Regards,
Simon


#10

It hangs up again from a Dragonboard410c wifi client:

64 bytes from 192.168.10.1: icmp_seq=510 ttl=64 time=0.818 ms
64 bytes from 192.168.10.1: icmp_seq=511 ttl=64 time=0.825 ms
64 bytes from 192.168.10.1: icmp_seq=512 ttl=64 time=1.08 ms
64 bytes from 192.168.10.1: icmp_seq=513 ttl=64 time=0.958 ms
64 bytes from 192.168.10.1: icmp_seq=514 ttl=64 time=0.663 ms
From 192.168.10.122 icmp_seq=563 Destination Host Unreachable
From 192.168.10.122 icmp_seq=566 Destination Host Unreachable
From 192.168.10.122 icmp_seq=569 Destination Host Unreachable

Simon


#11

This mainly concerns standard WiFi client role.

Instead of pinging, you can get low level wifi events (connect, disconnect, roaming…) with the iwevent command.

I will test on my side and let you know… did you see any specific pattern (e.g. every 20min). Does the client reconnect sucessfully after the disconnect ?


#12

Thanks you for your interest.

However, here it goes a mistake of mine: the IP forwarding into /etc/sysctl.conf:

net.ipv4.ip_forward = 1

I forgot to set it yesterday before posting. My bad. This seems to improve the stability of the connection also…

PS: would be useful to post it into the official doc. It’s pretty poor about wifi configuration suggestions.

I left the two boards powered on for approximately 12/13 hours, the client pinging to the AP all the night. The client lost connectivity for a while, 582 conscutive pings which I translate / estimate it to no more than 10, 15 minutes as much…
EDIT: The client was running the #283 Debian. I am repeating the test with both #359 Debian release.

No logs on AP side… :slightly_frowning_face:


#13

Hello, after many tests I confirm that I still exeperience AP connection issues, so the client loose connection after a while.

Here is a short dmesg output:

[   10.302823] Bluetooth: HCI device and connection manager initialized
[   10.302837] Bluetooth: HCI socket layer initialized
[   10.302847] Bluetooth: L2CAP socket layer initialized
[   10.302877] Bluetooth: SCO socket layer initialized
[   10.314103] btqcomsmd a204000.wcnss:smd-edge:wcnss:bt: BD address 02:00:a5:91:3c:51 retrieved from device-tree
[   10.325227] wcn36xx: mac address: 02:00:a5:91:3c:50
[   10.469940] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.469954] Bluetooth: BNEP filters: protocol multicast
[   10.469970] Bluetooth: BNEP socket layer initialized
[   10.602534] ax88179_178a 1-1.1:1.0 eth0: ax88179 - Link status is: 1
[   10.731125] wcn36xx: firmware WLAN version 'WCN v2.0 RadioPhy vRhea_GF_1.12 with 19.2MHz XO' and CRM version 'CNSS-PR-2-0-1-2-c1-00021'
[   10.731150] wcn36xx: firmware API 1.5.1.2, 41 stations, 2 bssids
[   10.734239] wcn36xx: FW Cap MCC
[   10.734254] wcn36xx: FW Cap P2P
[   10.734261] wcn36xx: FW Cap SLM_SESSIONIZATION
[   10.734267] wcn36xx: FW Cap DOT11AC_OPMODE
[   10.734278] wcn36xx: FW Cap SAP32STA
[   10.734288] wcn36xx: FW Cap TDLS
[   10.734299] wcn36xx: FW Cap P2P_GO_NOA_DECOUPLE_INIT_SCAN
[   10.734310] wcn36xx: FW Cap WLANACTIVE_OFFLOAD
[   10.734321] wcn36xx: FW Cap BEACON_OFFLOAD
[   10.734331] wcn36xx: FW Cap SCAN_OFFLOAD
[   10.734342] wcn36xx: FW Cap BCN_MISS_OFFLOAD
[   10.734353] wcn36xx: FW Cap STA_POWERSAVE
[   10.734364] wcn36xx: FW Cap STA_ADVANCED_PWRSAVE
[   10.734375] wcn36xx: FW Cap BCN_FILTER
[   10.734385] wcn36xx: FW Cap RTT
[   10.734396] wcn36xx: FW Cap RATECTRL
[   10.734406] wcn36xx: FW Cap WOW
[   10.734417] wcn36xx: FW Cap WLAN_ROAM_SCAN_OFFLOAD
[   10.734428] wcn36xx: FW Cap SPECULATIVE_PS_POLL
[   10.734439] wcn36xx: FW Cap IBSS_HEARTBEAT_OFFLOAD
[   10.734450] wcn36xx: FW Cap WLAN_SCAN_OFFLOAD
[   10.734461] wcn36xx: FW Cap WLAN_PERIODIC_TX_PTRN
[   10.734471] wcn36xx: FW Cap ADVANCE_TDLS
[   10.734482] wcn36xx: FW Cap BATCH_SCAN
[   10.734492] wcn36xx: FW Cap FW_IN_TX_PATH
[   10.734503] wcn36xx: FW Cap EXTENDED_NSOFFLOAD_SLOT
[   10.734514] wcn36xx: FW Cap CH_SWITCH_V1
[   10.734524] wcn36xx: FW Cap HT40_OBSS_SCAN
[   10.734535] wcn36xx: FW Cap UPDATE_CHANNEL_LIST
[   10.734546] wcn36xx: FW Cap WLAN_MCADDR_FLT
[   10.734561] wcn36xx: FW Cap WLAN_CH144
[   10.734591] wcn36xx: FW Cap TDLS_SCAN_COEXISTENCE
[   10.734618] wcn36xx: FW Cap LINK_LAYER_STATS_MEAS
[   10.734632] wcn36xx: FW Cap EXTENDED_SCAN
[   10.734643] wcn36xx: FW Cap DYNAMIC_WMM_PS
[   10.734653] wcn36xx: FW Cap MAC_SPOOFED_SCAN
[   10.734664] wcn36xx: FW Cap FW_STATS
[   10.734675] wcn36xx: FW Cap WPS_PRBRSP_TMPL
[   10.734685] wcn36xx: FW Cap BCN_IE_FLT_DELTA
[   10.756818] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   10.756890] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   10.866264] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   12.420492] Bluetooth: hci0 command 0xfc0b tx timeout
[   21.360436] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[  165.187617] wcn36xx: ERROR hal_remove_bsskey response failed err=6
[  199.016501] random: crng init done
[ 1817.354012] wcn36xx: WARNING STA with addr 02:00:26:9b:3c:50 and index 0 not found
[ 1817.354535] wcn36xx: WARNING STA with addr 02:00:26:9b:3c:50 and index 0 not found

It seems that after a while, the WCN hardware chip switch from AP to STA…

Do you have any further suggestion about this ?
Regards,
Simon


#14

Hi @simozz, I’ve just tested this use case with a db410c as Access Point and an other as client. I used same configuration as you with a latest snapshot (containing a bunch of WiFi fix for client role). I’m able to reproduce your issue, it’s seems related to wpa group rekey on AP side since the ping timeouts happen after this event on my side. Disabling wpa group rekey in hostapd.conf allows me to have a stable connection. I’m going to have a deeper look at this.

After capturing the air, It seems that AP does not ack client packet anymore after rekeying.

Snapshots: http://snapshots.linaro.org/96boards/dragonboard410c/linaro/debian/


#15

Hello @Loic

Thank you for updating this thread.
What distribution version are you testing ?

I am using the 359 (with the option disabled since you suggested it from the 28th of Febraury), but you are linking me the snapshots lists, which are non official releases, AFAIK.

Could you clarify this ensure me about it?
Thanks,
Regards,
Simon


#16

Debian

I linked a snapshot because it contains all last WiFi fixes contrary to release image. Snapshot 373 was stable on my side.