BPI R3 - 802.11s mesh works only at channel 36

Banana Pi BPI-R4/BPI-R3 Mini/BPI-R3/BPI-R64/BPI-R2 OpenWRT
1

Hi, Im trying the mesh 802.11s with 23.05.03. BPI R3 v1.1, with sd card image.

Channel/ Frequency issue: a-)It doesnt emit beacons and can not be find by other mesh nodes, if its channel is not 36. When it is set to 36 bw 80Mhz and working, output of root@OpenWrt:/# iw dev phy1-mesh0 info is as follows:

Interface phy1-mesh0
        ifindex 16
        wdev 0x100000004
        addr a6:a6:52:82:7e:b4
        type mesh point
        wiphy 1
        channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
        txpower 20.00 dBm
        multicast TXQ:
                qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                0       0       33      0       0       0       0       3534            33

when it switched to channel 52 bw 80, as follows: output of root@OpenWrt:/# iw dev phy1-mesh0 info

Interface phy1-mesh0
        ifindex 17
        wdev 0x100000005
        addr a2:a6:52:82:7e:b4
        type mesh point
        wiphy 1
        txpower 20.00 dBm
        multicast TXQ:
                qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                0       0       0       0       0       0       0       0               0

as can be seen, the line starting with “channel” is missing at the second / problematic case.

b-)After trying several channels, the frequency shown does not match to channel number. see attached file - channel 52 - frequency 6210. In this case phy device(phy1-mesh0) is, can not bee seen via ifconfig or iwinfo.

incorrect frequencyvalue
incorrect frequencyvalue1101×530 48 KB

What could be the issue?

2

When I try to corner the issue, Im currently at a stage where uci command is processed and config goes to hostapd over a “global control interface”, a ubus based mechanism. (uci probably calling hostapd/netifd scripts) Im not sure if the problem is a “ubus call” issue (invalid channel/freq call string/parameter) occuring between uci-hostapd or below the hostapd down to cfg/mac80211 and to wifi card. If we could have intercept the “ubus calls” to hostapd, that would shed more light to the issue. Also I would also like to make direct calls to hostapd, but call format is not straighforward and couldnt see/find any examples. will spend more time on it.