Page 1 of 1

Help in Decoding Wifi W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0

Posted: Mon Jan 22, 2024 3:37 pm
by barrerarodrigo
Dear community,

I am currently using the ESP-32 as a socket server, sending around 500 bytes every 500ms for each client that connects on the network.
Sometimes I receive the following warning repeatdly:

W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0

However, my network continues to work fine.

Does anyone know what this waning means?

Thank you,

Rodrigo

Re: Help in Decoding Wifi W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0

Posted: Mon Jun 17, 2024 9:18 am
by axellin
I got the same messages..
My device is running as an AP, but I sometime cannot connect to it.
Even the device shows "esp_netif_lwip: DHCP server assigned IP to a client, IP is: 192.168.10.2", I still cannot reach the device by ping.
Anything wrong in below log?

Code: Select all

I (46217) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (46217) wifi:<ba-del>idx:2, tid:0
I (51209) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (51209) wifi:<ba-del>idx:2, tid:0
I (51210) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (55340) wifi:station: 20:1e:88:5e:2b:3f leave, AID = 1, reason = 4, bss_flags is 167011, bss:0x3c1283a4
I (55341) wifi:new:<6,0>, old:<6,0>, ap:<6,0>, sta:<0,0>, prof:6, snd_ch_cfg:0x0
I (103282) wifi:removing station <20:1e:88:5e:2b:3f> after unsuccessful auth/assoc, AID = 0
W (103283) wifi:rm mis
I (103283) wifi:new:<6,0>, old:<6,0>, ap:<6,0>, sta:<0,0>, prof:6, snd_ch_cfg:0x0
I (138092) wifi:removing station <20:1e:88:5e:2b:3f> after unsuccessful auth/assoc, AID = 0
W (138093) wifi:rm mis
I (138093) wifi:new:<6,0>, old:<6,0>, ap:<6,0>, sta:<0,0>, prof:6, snd_ch_cfg:0x0
I (171455) wifi:new:<6,0>, old:<6,0>, ap:<6,0>, sta:<0,0>, prof:6, snd_ch_cfg:0x0
I (171455) wifi:station: 20:1e:88:5e:2b:3f join, AID=1, bgn, 20
I (171609) esp_netif_lwip: DHCP server assigned IP to a client, IP is: 192.168.10.2
I (174603) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (174604) wifi:<ba-del>idx:2, tid:0
I (177898) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (177898) wifi:<ba-del>idx:2, tid:0
I (177899) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (180711) telnet_server: Socket accepted, connected from 192.168.10.2:48022
I (181160) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (181161) wifi:<ba-del>idx:2, tid:0
I (181161) wifi:[ADDBA]RX DELBA, reason:37, delete tid:0, initiator:1(originator)
I (185156) wifi:<ba-add>idx:2 (ifx:1, 20:1e:88:5e:2b:3f), tid:0, ssn:137, winSize:64
I (221627) wifi:station: 20:1e:88:5e:2b:3f leave, AID = 1, reason = 3, bss_flags is 167011, bss:0x3c1283a4
I (221628) wifi:new:<6,0>, old:<6,0>, ap:<6,0>, sta:<0,0>, prof:6, snd_ch_cfg:0x0
I (221634) wifi:<ba-del>idx:2, tid:0

Re: Help in Decoding Wifi W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0

Posted: Tue Jun 18, 2024 2:30 pm
by Linetkux Wang
This is the A-MPDU related feature introduced into Wi-Fi since Wi-Fi4.
W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0

Means in the Rx direction, Block Ack Agreement is deleted because of reason(37). Look up the IEEE802.11 spec, you can find that 37 means "Requesting STA is no longer using the stream or session". TID 0 is the default Access Category, and mapped into Best Effort, from ToS field of your packet.

Re: Help in Decoding Wifi W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0

Posted: Sat Nov 02, 2024 6:23 pm
by dizcza
Linetkux Wang wrote:
Tue Jun 18, 2024 2:30 pm
This is the A-MPDU related feature introduced into Wi-Fi since Wi-Fi4.
W (223029) wifi:[ADDBA]rx delba, code:37, delete tid:0
Can you give a link to all A-MPDU related codes? I'm getting

Code: Select all

W (12755) wifi:[ADDBA]rx delba, code:1, delete tid:0
for the first time I connect

Code: Select all

esp_http_client_handle_t
to my HTTPS server. The app works fine but I'd like to know a bit more about this warning... and have a list for future warnings like this.

Thanks.