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 }
The version of openwrt installed is 18.06.2
Wpa-supplicant is the only wpa installed.
The bat0 interface is present in adhoc mode but once I change it to mesh mode in wireless settings, the interface is no longer visible using the command ip link.
Cheers thanks any help appreciated.
Do not set a bssid on an 802.11s interface. It is based on the mesh_id (a required setting that you don't have) and the channel matching. Mesh_id is an arbitrary string with the same rules as ssid. Channel numbers must be explicitly set and the same on all the nodes. Your global radio config is the very old syntax which may not work on newer versions. On a 2 GHz n radio, use hwmode 11g along with htmode HT20. There is no need for ht_capab settings and hwmode 11n is not valid at all. You have tried to define an AP in the wifi-device section, remove that. It's defined in a separate wifi-iface section.
I’m using a laguana gateworks board its no longer supported, to install any new packages I have to build a new image using make config. Therefore before I take on building the new image I will end up with will be the version of openwrt installed is 18.06.2 with the propper packages such as wpad-mesh installed,
Do you think that this will work,
Read through the other wiki and still confused as to what version of openwrt support 802.11s.
The drivers I have are doodle lab drivers in their specks the show that the support mesh and their running on ath9k software.
Any advice appreciate.
The configuration changed on master at the beginning of 2019. batman-adv has been supported for several years now, with the version in the package changing over time, at least as far back as
commit 48f38ba
Author: Travis Kemen <thepeople@openwrt.org>
Date: Sat Mar 17 03:59:59 2007 +0000
add B.A.T.M.A.N. from #1448
You're sort of on your own with those to get support from the vendor if there are problems in the driver, especially on an older release of OpenWrt. It wouldn't be the first time that a driver claimed to support a feature and didn't.
Trying to see if my mesh is up and working in adhoc mode.
Below are the results from ifconfig -a and brctl show, I can log on to either of the 2 nodes and get internet. But bat0 is not connected to br-lan. does this mean that the mesh is not working.
If batctl shows neighbors and originators, the mesh is up and batman is routing. Past that, it is what you want to do with the bat0 network. Just like having eth0 connected, it can’t read your mind as to how you want to use it.
