Mesh point disabled ( and other problems )

Hello there !

I am a newbie in mesh. I have a BTHH5A running OpenWRT 22.3.02. I have only 1 mesh node which is my BTHH5A router. In other words, I am not running a proper mesh network. My aim is to try out if mesh works with BTHH5A's current setup. If yes, I will introduce another AP. I am not looking for ft roaming 802.11r.

I could create a mesh point on one of the radioes. During the process I have a few questions :

Package wpad-mesh-openssl vs wpad-mesh-wolfssl : I already had wpad-basic-wolfssl installed. This package was in conflict with its natural successer wpad-mesh-wolfssl. So I had to remove existing package before installing mesh complient ssl. When I tried to install new one it gave a conflict error with wpad-mesh-openssl, which I never installed in the first place ! This error forced me to install wpad-mesh-openssl.

Here is the current list of ssl packages installed :


root@...:~# opkg list-installed | grep ssl
libopenssl-conf - 1.1.1q-1
libopenssl1.1 - 1.1.1q-1
libustream-wolfssl20201210 - 2022-01-16-868fd881-2
libwolfssl5.5.1.ee39414e - 5.5.1-stable-3
luci-ssl - git-20.244.36115-e10f954
openssl-util - 1.1.1q-1
openvpn-openssl - 2.5.7-3
px5g-wolfssl - 5.1
wget-ssl - 1.21.2-1
wpad-mesh-openssl - 2022-01-16-cff80b4f-13.1

Is the above list self consistent? Is wpad-mesh-openssl sufficient? If not how do I proceed.

Mesh point device on wlan0 always disabled. Not sure why. So I did an iw list and got this :

root@...:~# iw list
Wiphy phy1
        wiphy index: 1
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 1:
                Capabilities: 0x11ee
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm)
                        * 2472 MHz [13] (20.0 dBm)
                        * 2484 MHz [14] (disabled)
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Supported extended features:
                * [ RRM ]: RRM
                * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
                * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
                * [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
                * [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
                * [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying
                * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
                * [ DEL_IBSS_STA ]: deletion of IBSS station support
                * [ MULTICAST_REGISTRATIONS ]: mgmt frame registration for multicast
                * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
                * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
Wiphy phy0
        wiphy index: 0
        max # scan SSIDs: 16
        max scan IEs length: 199 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Available Antennas: TX 0x7 RX 0x7
        Configured Antennas: TX 0x7 RX 0x7
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * P2P-device
        Band 2:
                Capabilities: 0x19ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-23
                VHT Capabilities (0x338001b2):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        TX STBC
                        RX antenna pattern consistency
                        TX antenna pattern consistency
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Frequencies:
                        * 5180 MHz [36] (23.0 dBm)
                        * 5200 MHz [40] (23.0 dBm)
                        * 5220 MHz [44] (23.0 dBm)
                        * 5240 MHz [48] (23.0 dBm)
                        * 5260 MHz [52] (20.0 dBm) (radar detection)
                        * 5280 MHz [56] (20.0 dBm) (radar detection)
                        * 5300 MHz [60] (20.0 dBm) (radar detection)
                        * 5320 MHz [64] (20.0 dBm) (radar detection)
                        * 5500 MHz [100] (26.0 dBm) (radar detection)
                        * 5520 MHz [104] (26.0 dBm) (radar detection)
                        * 5540 MHz [108] (26.0 dBm) (radar detection)
                        * 5560 MHz [112] (26.0 dBm) (radar detection)
                        * 5580 MHz [116] (26.0 dBm) (radar detection)
                        * 5600 MHz [120] (26.0 dBm) (radar detection)
                        * 5620 MHz [124] (26.0 dBm) (radar detection)
                        * 5640 MHz [128] (26.0 dBm) (radar detection)
                        * 5660 MHz [132] (26.0 dBm) (radar detection)
                        * 5680 MHz [136] (26.0 dBm) (radar detection)
                        * 5700 MHz [140] (26.0 dBm) (radar detection)
                        * 5720 MHz [144] (26.0 dBm) (radar detection)
                        * 5745 MHz [149] (23.0 dBm)
                        * 5765 MHz [153] (23.0 dBm)
                        * 5785 MHz [157] (23.0 dBm)
                        * 5805 MHz [161] (23.0 dBm)
                        * 5825 MHz [165] (23.0 dBm)
                        * 5845 MHz [169] (disabled)
                        * 5865 MHz [173] (disabled)
        valid interface combinations:
                 * #{ managed, P2P-client } <= 16, #{ P2P-GO } <= 3, #{ AP } <= 16, #{ IBSS } <= 1,
                   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Maximum associated stations in AP mode: 0
        Supported extended features:
                * [ VHT_IBSS ]: VHT-IBSS
                * [ RRM ]: RRM
                * [ SET_SCAN_DWELL ]: scan dwell setting
                * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
                * [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
                * [ AQL ]: Airtime Queue Limits (AQL)
                * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
                * [ DEL_IBSS_STA ]: deletion of IBSS station support
                * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
                * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
root@...:~#

Valid interface combinations includes mesh point only for wiphy phy1 ( = wlan1 = radio1 = 2.4 GHz on channel 6 ). It seems wiphy phy0 ( = wlan0 = radio0 = 5 GHz on channel 161 ) does not have a valid interface for mesh. Is that intentional? Am I missing something here? I don't even know what that means.

I enabled the wlan0 mesh point device in LuCI --> Interfaces --> Wireless. However, its status always shows disabled. But wlan1's mesh point is 'started'. The mesh id for both is 'my-mesh'.

In addition to mesh points, I have two ssids on each wlan0 and wlan1 ( 1 for Lanif and 1 for Guestif ) and they are working fine. Should I disable them for mesh to work? If yes which ssid mesh will broadcast on? Is it 'my-mesh' ? If not, can I expect mesh to work with existing ssids?

Please let me know your views.

Thank you!

-Gamma

ath10k-ct does not support meshing on wave1 hardware (qca9880-br4a), but ath10k does, change kernel module and its corresponding firmware and you should be golden.

1 Like

@slh,

Ah, such a basic mistake I made. I have these two packages installed.

ath10k-firmware-qca988x-ct - 2020-11-08-1
kmod-ath10k-ct - 5.10.146+2022-05-13-f808496f-1

I should replace them with

ath10k-firmware-qca988x
kmod-ath10k

Right? Also I should be using ethernet and not wifi for the transition. Isn't it?

Thank you.

-Gamma

Yes.

@slh , Thanks for the reply. Will try out now. Found this thread :

The OP had some problems, but it was the Archer C6 router. Hopefully my BTHH5A won't complain. Fingers crossed.

-Gamma

Create a custom image via the online image builder, where you remove the unwanted modules, and add the ones you want.

Mission mesh on 5 GHz successful.

@frollic : Thanks for the tip. Will remember that.

@slh : Thanks for your guidence.

The 5GHz radio looks a bit slow ( 510 Mbps ). Will it remain that way or is there any way to prop it up?

-Gamma

The bthub5 isn't a fast device, it's unique in terms of having a (supported-) VDSL modem, it's cheap and plenty, but not a speed demon at all.

@slh , Thanks for the explanation. Actually the drop in the speed is not noticeable. What I noticed is lack of dual band connections. Often a dual band device such as iPhone will connect over both radioes. But after enabling mesh only single band connections are seen. Still I am not worried about it.

BTW, can my existing ssids work with mesh? Thank you again.

-Gamma

Basically no client device (aside from specially configured desktop linux) can participate in your mesh directly, the mesh only interconnects your APs with a wireless backhaul. For your clients to work, you need to create additional -normal- AP interfaces (e.g. WPA2PSK or WPA3SAE) on your bthub5 and the other APs.

Excellent. Will add second AP. The tutorials are already available. Thank you for the clarification. As of now, the only mesh node is 'working'.

-Gamma

Hello mates.

Here is the output of my mesh0 and mesh1 devices

:~# iw mesh0 info && iw mesh1 info
Interface mesh0
        ifindex 53
        wdev 0xe
        addr c8:91:f9:3b:1c:bf
        type mesh point
        wiphy 0
        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       60      0       0       0       0       8282            60
Interface mesh1
        ifindex 52
        wdev 0x10000000e
        addr c8:91:f9:3b:1c:be
        type mesh point
        wiphy 1
        channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
        txpower 18.00 dBm
        multicast TXQ:
                qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                0       0       60      0       0       0       1       8282            60

I downloaded this app on my iPhone : https://apps.apple.com/us/app/my-mesh/id1403736762

The app does not see the mesh0 or mesh1 points. It says only MeshForce, M1, M3, M3 Dot, M3S, M7 are supported. I am on BTHH5A.

Can I say my single node mesh is working but not recognised by the app?

But station and mpath dumps are empty. I found these wiki commands to check if mesh is working :

:~#iw dev mesh0 station dump
:~# iw dev mesh1 station dump
:~# iw dev mesh1 mpath dump
DEST ADDR         NEXT HOP          IFACE       SN      METRIC  QLEN    EXPTIME         DTIM    DRET    FLAGS   HOP_COUNT  PATH_CHANGE
:~# iw dev mesh0 mpath dump
DEST ADDR         NEXT HOP          IFACE       SN      METRIC  QLEN    EXPTIME         DTIM    DRET    FLAGS   HOP_COUNT  PATH_CHANGE

Are they empty because this is a single node mesh? Do I need to introduce another node to check if mesh is working? Thank you guys!

-Gamma

That iphone app is for proprietory "Meshforce WiFi", whatever that is. It is certainly nothing to do with 802.11s mesh networks.

You only have a single meshnode?
If so then you do not have a mesh network, just a single component that can be used to contribute to a mesh network.

Station dump lists the mesh nodes that this meshnode can see.

Mpath dump displays the mac-routing table entries for the meshnodes listed in station dump.

As you do not have any other meshnodes both station dump and mpath dump will be empty.

Why are you configuring 2 mesh interfaces?
This is only necessary if a particular meshnode is to be a bridge between 2 separate mesh networks.

Hi @bluewavenet ,

Thanks for the explanation. The second mesh node is for testing purpose. I am not yet sure which one to keep 5 GHz or 2.4 GHz.

Actually I have a spare BTHH5a which I planned to use as second mesh node. At the last moment I found that it is still running BT stock fw. In a few it will be ready with OpenWrt and then I can go ahead with a proper mesh network.

Thank you once again!

-Gamma

Once you get your second meshnode running, make sure you only have one mesh interface enabled at a time, otherwise you will end up with bridge loops and a broken network :wink:

Thanks for the alert. :slight_smile: Will remember that!

-Gamma

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.