Hello OpenWRTers,
I have been trying to get 802.11s to work in my D-Link Covr-x1860 (Add support for D-Link COVR-X1860) with brief success.
During the first configuration run I got it working with wpad-mesh-openssl and mesh11sd, however, due to a misconfiguration, I had to re-flash the firmware and start from scratch. Now, I cannot get the nodes to associate.
The configuration is pretty simple. I have used this snapshot (https://github.com/RolandoMagico/openwrt-build/releases/tag/COVR-X1860_Build_20230724) as the device is on the way to be officially supported, configured the br-lan as DHCP-Client in the master and slave nodes, then connect the master node directly to the router via ethernet and the slave node temporarily to the master node via ethernet as well.
After that, I jumped directly to the mesh configuration in the 5Ghz band without much success (tested 2.4Ghz as well). I have tried as many combinations as possible but I am pretty frustrated with the configuration at this point and I would appreciate a helping hand if someone has the knowledge to guide me in order to troubleshoot the issue.
The configuration is pretty standard in both nodes:
uci set wireless.wifinet0=wifi-iface
uci set wireless.wifinet0.device=radio1
uci set wireless.wifinet0.mode='mesh'
uci set wireless.wifinet0.encryption='sae'
uci set wireless.wifinet0.mesh_id=my-mesh
uci set wireless.wifinet0.mesh_fwding='1'
uci set wireless.wifinet0.mesh_rssi_threshold='0'
uci set wireless.wifinet0.key=TestingPassword
uci set wireless.wifinet0.network='lan'
uci set "wireless.radio1.channel"=40
uci delete "wireless.radio1.disabled"
I have checked logread command output as well and I have found some errors in the slave node that may be related, but I am not sure if that is the case or how to fix them as there are no references on the internet. The logread content is as follows:
Fri Aug 4 21:41:27 2023 daemon.notice netifd: Wireless device 'radio1' is now down
Fri Aug 4 21:41:27 2023 daemon.notice mesh11sd[1991]: phy1-mesh0 is not up - giving up for now.
Fri Aug 4 21:41:47 2023 daemon.notice mesh11sd[1991]: mesh0 is not up - giving up for now.
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Command failed: Request timed out
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Command failed: Not found
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Interface 0 setup failed: WPA_SUPPLICANT_FAILED
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Failed to parse json data: unexpected end of data
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process path (/proc/exe)
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Command failed: ubus call network.wireless notify { "command": 2, "device": "radio1", "data": { "pid": 0, "exe": "\/usr\/sbin\/wpad", "required": true, "keep": true } } (Invalid argument)
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Usage: ubus [<options>] <command> [arguments...]
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Options:
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): -s <socket>: Set the unix domain socket to connect to
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): -t <timeout>: Set the timeout (in seconds) for a command to complete
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): -S: Use simplified output (for scripts)
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): -v: More verbose output
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): -m <type>: (for monitor): include a specific message type
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): (can be used more than once)
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): -M <r|t> (for monitor): only capture received or transmitted traffic
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055):
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): Commands:
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - list [<path>] List objects
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - call <path> <method> [<message>] Call an object method
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - subscribe <path> [<path>...] Subscribe to object(s) notifications
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - listen [<path>...] Listen for events
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - send <type> [<message>] Send an event
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - wait_for <object> [<object>...] Wait for multiple objects to appear on ubus
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): - monitor Monitor ubus traffic
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055):
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): command failed: Link has been severed (-67)
Fri Aug 4 21:41:58 2023 daemon.notice netifd: radio1 (3055): command failed: Link has been severed (-67)
Fri Aug 4 21:41:58 2023 daemon.notice netifd: Wireless device 'radio1' is now up
Fri Aug 4 21:41:58 2023 kern.info kernel: [ 80.435064] br-lan: port 3(mesh0) entered blocking state
Fri Aug 4 21:41:58 2023 kern.info kernel: [ 80.440498] br-lan: port 3(mesh0) entered disabled state
Fri Aug 4 21:41:58 2023 kern.info kernel: [ 80.446404] device mesh0 entered promiscuous mode
Where should I start troubleshooting this issue?.
Thanks in advance!