I have two Netgear WAX202 that uses 802.11s to bridge. Both were running 22.03.05 and it works flawlessly with package wpad-mesh-openssl installed. However, when upgrading one or both from 22.03.05 to 23.05.0-rc1 with package either wpad-mesh-openssl or wpad-mesh-mbedtls, the 802.11s bridge stops working. From the system log I can see the mesh peer connected successfully. However, it seems 23.05.0-rc1 fails to transmit any packets successfully. When I upgrade both to 23.05.0-rc1, the tx and rx rate stuck at 6Mbit/s. If I upgrade one to 23.05.0-rc1, the one got upgraded is receiving at 800Mbit/s while transmiting at 6Mbit/s. iw dev mesh0 station dump shows the following:
Station xx:xx:xx:xx:xx:xx (on mesh0)
inactive time: 30 ms
rx bytes: 1318623
rx packets: 9897
tx bytes: 485905
tx packets: 2947
tx retries: 0
tx failed: 590
rx drop misc: 24939
signal: -57 [-59, -61] dBm
signal avg: -57 [-58, -62] dBm
Toffset: 9645888375 us
tx bitrate: 6.0 MBit/s
tx duration: 15493845 us
rx bitrate: 864.8 MBit/s 80MHz HE-MCS 8 HE-NSS 2 HE-GI 0 HE-DCM 0
rx duration: 45338 us
last ack signal:-57 dBm
avg ack signal: -56 dBm
airtime weight: 256
mesh llid: 0
mesh plid: 0
mesh plink: ESTAB
mesh airtime link metric: 1823
mesh connected to gate: no
mesh connected to auth server: no
mesh local PS mode: ACTIVE
mesh peer PS mode: ACTIVE
mesh non-peer PS mode: ACTIVE
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: yes
TDLS peer: no
DTIM period: 2
beacon interval:100
connected time: 216 seconds
associated at [boottime]: 37.622s
associated at: 1686539830911 ms
current time: 1686540047263 ms
System log only shows the following. No errors or anything abnormal.
Sun Jun 11 20:17:10 2023 kern.info kernel: [ 37.291622] br-lan: port 7(mesh0) entered blocking state
Sun Jun 11 20:17:10 2023 kern.info kernel: [ 37.297009] br-lan: port 7(mesh0) entered forwarding state
Sun Jun 11 20:17:10 2023 daemon.notice wpa_supplicant[1585]: mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sun Jun 11 20:17:10 2023 daemon.notice wpa_supplicant[1585]: mesh0: MESH-GROUP-STARTED ssid="xxxxxxxx" id=0
Sun Jun 11 20:17:10 2023 kern.info kernel: [ 37.473581] br-lan: port 5(phy1-ap0) entered blocking state
Sun Jun 11 20:17:10 2023 kern.info kernel: [ 37.479200] br-lan: port 5(phy1-ap0) entered forwarding state
Sun Jun 11 20:17:10 2023 daemon.notice netifd: Network device 'phy1-ap0' link is up
Sun Jun 11 20:17:10 2023 daemon.notice wpa_supplicant[1585]: mesh0: new peer notification for xx:xx:xx:xx:xx:xx
Sun Jun 11 20:17:10 2023 daemon.notice wpa_supplicant[1585]: mesh0: new peer notification for xx:xx:xx:xx:xx:xx
Sun Jun 11 20:17:10 2023 daemon.notice wpa_supplicant[1585]: mesh0: mesh plink with xx:xx:xx:xx:xx:xx established
Sun Jun 11 20:17:10 2023 daemon.notice wpa_supplicant[1585]: mesh0: MESH-PEER-CONNECTED xx:xx:xx:xx:xx:xx
I also tried snapshot, and it is showing exactly the same problem.