Yep, same thing here, when doing a scan using 2.4GHz radio, you can only see the turning wheel starting wireless scan.....no result output. Not sure if it because I have assigned the 2.4GHz to be a dedicated mesh backhaul, and scanning is disabled.
However 5Hz radio's wireless scanning is working
How did you get Mesh0 & Mesh1 listed like that?
Mine one is showing WLAN0 & WLAN1
If you want to make progress on this, please show the contents of: /etc/config/wireless
and /etc/config/network
Remember to use the "</>" option in the top line of the text box to make sure the contents are formatted correctly here.
It might be, that is the nature of snapshots.
By the way, I see you are using 22.03-snapshot. You do realise this is not even officially available - ..... It might be better to wait for the first release candidate before trying it.
To get the hostname, Luci must do a reverse lookup of the ip address of the remote mesh node.
The mesh network (layer 2) neither knows nor cares about the layer 3 ip networking.
Have you added the mesh network to the lan bridge?
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option packet_steering '1'
option ula_prefix 'fd81:6440:7553::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'wan'
option ipv6 '0'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.1.180'
option gateway '192.168.1.1'
list dns '192.168.1.1'
Yes, I notice, I am not using the official OpenWrt firmware, if I am going to use the official one, the
5GHz radio settings will be crashing Luci. 2.4GHz radio doesn't suffer this problem.
You can't use Luci to do any setting within the 5GHz radio. Configuration done on Luci will display
error message.
You are right, disabling the mesh gets wireless scanning working again. This wasn't necessary in earlier versions.
I edited the wireless file, but in luci, setting the mesh point's "Interface Name" in its wireless settings "Interface Configuration"->"Advanced Settings" tab should achieve the same effect.
Appreciated your info given.
But as much as I like to solve the problem, I don't possess the technical
know-how in understanding solutions given to me, as I am not a developer.
I am just a Windows guy(nor a Linux guru), or just an average guy who is trying to learn OpenWrt as much as possible. Please don't be offended, your information is too overwhelming for me to comprehend.
My router is a Wifi 6 802.11 AX router, so it should be using High Efficiency (HE) standard rather than using HT or High Throughput which is 802.11n standard
You don't have to go deep into dts fille or hotplug to override the MAC, just add an option macaddr to the wifi-iface, using the factory MAC address from the sticker.
If you've been copying configs between the two units you may have ended up with a duplicate option macaddr in /etc/config/network. This should also be fixed by using the sticker MAC or a close one by increasing the last number by one or two.
Let's simply work through the problems one by one.
Mac address problem. This looks like a firmware image issue as @anon69880279 suggested and does not effect the mesh, but causes problems with the 5GHz network.
We can work around this problem easily by setting the mac for the 5G radios on both routers.
On each mesh node (router) in turn, in a terminal session do the following -
On the one with the 5c:92:5e:37:e8:70 mac:
uci set wireless.wlan1.macaddr='5c:92:5e:37:e8:70'
uci commit wireless
On the one with the 5c:92:5e:b7:7a:d8 mac:
uci set wireless.wlan1.macaddr='5c:92:5e:b7:7a:d8'
uci commit wireless
For simplicity, reboot both then check if the mac problem is fixed.
The encryption problem.
802.11s mesh has an additional dependency and an addon to make it work properly.
To install these you need to make sure both routers in turn are connected to an Internet feed.
It looks like you have both configured as pure AP/Meshnodes so all you need to do is connect, each in turn to your isp router with an ethernet cable (lan port to lan port)
In a terminal session on each meshnode in turn do (making sure you do net get any errors):
Making sure you did both, then put the meshnodes back where you want them (only one connected to the isp router by ethernet) and power them both back up.
Hello, 1st of all, thank you for helping me troubleshoot the problem
Can you tell me on what basis, that you use to determine which router should have the
correct MAC address on the 5GHz radio?
Is it based on the ip link command or the iw dev wlan0 mpath dump output?
I am confused, as to why I am setting MAC address on the wlan1 (5GHz Radio) using MAC address from the 2.4GHz Radio?
Both 5c:92:5e:37:e8:70 & 5c:92:5e:b7:7a:d8 Both these MAC addresses are actually referring to the 2.4GHz Radios coming from the OpenWrtX5000R180 and OpenWrtX5000R182
Shouldn't I should be setting the ACTUAL(or REAL) MAC address for the 5GHz Radio?
