Beryl MT1300 log warnings: ADDBA Resp Ba Policy[0] not support

andres · 2022-01-18T18:55:14.324Z

Hello all,

I have two identical MT-1300s. A couple of weeks ago I upgraded one to 3.211 trying to get it more stable, previous version (201 I think?) was super unstable. All worked out well, so today I decided to upgrade the second one to 3.211 as well.

The upgrade in both has been smooth, all legacy/existing (I kept settings for the upgrade) configurations are working including some Wireguard and routing customizations. No complaints there.

Checking all the settings page by page now to make sure they both were configured as I want them to, I found a lot (tons of) messages on the logs (both System and Kernel) as below, on both routers. I can’t tell if the old firmware was issuing those - chances are not or I would have noticed, and I do check logs every once in a while.

[some timestamp] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support

They come about every two seconds. Below is a list of timestamps (decimal part removed for clarity):

[49231.] [49233.] [49236.] [49238.] [49240.] [49242.] [49244.] [49258.] [49261.] [49263.] [49265.] [49267.] [49269.] [49271.] [49351.] [49353.] [49356.] [49358.] [49360.] [49362.] [49364.] [49379.] [49381.] [49383.] [49385.] [49387.] [49389.] [49391.] [49472.] [49474.] [49476.] [49478.] [49480.] [49482.] [49484.] [49499.] [49501.] [49503.] [49505.] [49507.] [49510.] [49512.] [49595.] [49597.] [49599.] [49601.] [49603.] [49605.] [49607.] [49619.] [49621.] [49624.] [49626.] [49628.] [49630.] [49632.]

So far, I have noticed no odd behaviour (they seem to be warnings after all), but I would like to know what is going on.

At the very least, I’d rather not have those on the System log so it does not get as polluted and unreadable.

Firmware (identical on both)

|Model|GL-MT1300|
|---|---|
|Architecture|MediaTek MT7621 ver:1 eco:3|
|Firmware Version|OpenWrt 19.07.8 r11364-ef56c85848 / LuCI openwrt-19.07 branch git-21.189.23240-7b931da|
|Kernel Version|4.14.241|

Thanks all,

[Edit: Readability]

andres · 2022-01-22T01:53:19.695Z

BUMP

Still happening after factory reset and reconfiguration.

alzhao · 2022-01-22T03:36:26.015Z

I don’t know the meaning of the log.

@JerryZhao can you have a check?

JerryZhao · 2022-01-22T03:45:50.538Z

Block Ack.

mrn-cciew – 1 Nov 14

CWAP – 802.11 : Block Ack

The Block Ack mechanism improves channel efficiency by aggregating several acknowledgments into one frame. There are two types of Block Ack mechanisms, immediate and delayed. Immediate Block Ack is…

andres · 2022-01-22T05:38:36.545Z

Following up on that article, now that it is clear it is a wifi related situation. Looking at the log events around the issue, I can see that always the same device is present on the logs.

That device is a Ring camera-bell and it has been there since 2018, so much before the Beryls.

Reading at those logs, is that the device that is issuing all those AddBAReq requests?

Does this message (the log warning) comes from the Beryl Wifi driver?

Those warnings can be safely ignored then?

The Beryl’s default Logging level is set to debug, I have changed to to Error (the level just above Warning) ----- and … the messages still show on both System and Kernel logs

Warning messages with events before and after:

21:27:27 2022 kern.warn kernel: [ 9012.216981] Rcv Wcid(4) AddBAReq
21:27:27 2022 kern.warn kernel: [ 9012.220387] Start Seq = 00000046
21:28:51 2022 kern.warn kernel: [ 9096.284836] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
21:28:53 2022 kern.warn kernel: [ 9098.263656] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
. . . . . . .
21:31:02 2022 kern.warn kernel: [ 9226.941243] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
21:31:04 2022 kern.warn kernel: [ 9229.091617] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
21:31:54 2022 kern.warn kernel: [ 9278.460016] c2b, flush one!
21:32:36 2022 user.notice mtk-wifi: del_station 34:03:de:4e:82:93 rax0
21:32:37 2022 kern.warn kernel: [ 9321.699689] AP SETKEYS DONE - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=4 from 34:03:DE:4E:82:93
21:32:37 2022 kern.warn kernel: [ 9321.699689]
21:32:37 2022 user.notice mtk-wifi: new_station 34:03:de:4e:82:93 rax0
21:32:37 2022 user.notice mtk-wifi: del_station 34:03:de:4e:82:93 rax0
21:32:38 2022 kern.warn kernel: [ 9322.669275] AP SETKEYS DONE - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=4 from 34:03:DE:4E:82:93
21:32:38 2022 kern.warn kernel: [ 9322.669275]
21:32:38 2022 user.notice mtk-wifi: new_station 34:03:de:4e:82:93 rax0
21:32:40 2022 kern.warn kernel: [ 9325.350107] Rcv Wcid(4) AddBAReq
21:32:40 2022 kern.warn kernel: [ 9325.353520] Start Seq = 00000011
21:32:52 2022 kern.warn kernel: [ 9336.914122] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
21:32:54 2022 kern.warn kernel: [ 9338.892729] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
. . . . . . .
21:33:04 2022 kern.warn kernel: [ 9349.406258] PeerAddBARspActionSanity(): ADDBA Resp Ba Policy[0] not support
21:33:37 2022 kern.warn kernel: [ 9381.527788] a99, flush one!
21:34:46 2022 kern.warn kernel: [ 9450.613228] bd3, flush one!

alzhao · 2022-01-22T06:01:32.967Z

This comes from the wifi driver so system log does not control it.

If wifi works good you can omit these.