It works perfectly, but it is not what I want, 2.9 (or 2.9-dev) only contains the AP/STA wizard and I would AP/STA but more over the Mesh Wizard. Like in the 2.6.6, but I think this Wizard was deprecated after.
With 2.6.6 the same BCF is not working, not even with 2.9.3. Not with ether with OpenManet pre-built or home built. I tried few others unsuccessful BCF combinations.
So my questions are:
What is the difference between a -dev branch and none -dev branch?
Is there any documentation explaining which BCF/Firmware version to use with which OpenWRT? Or at least with the 2.6.6?
I’ll answer the BCF portions of this, I’ll leave the questions about the Mesh Wizard for folks who know our OpenWRT builds better.
The BCF major revision (and thus the format of the file) changed between versions 1.12 and 1.14 of the firmware. Our OpenWRT 2.6 build was based on the 1.12 firmware, and thus requires a BCF that would have been distributed with the 1.12 firmware.
The BCF from the 1.14 release should work for all versions from 2.7 to the present.
There’s a lookup table, but I don’t believe it’s published anywhere. I’ll see if I can fix that.
The wizard isn’t deprecated. It should still be in the feed. The wizard will only show up in the options available if the mesh11sd package is included in the build.
@Zandr Thank you very much I manage to make both 2.6 and 2.9 work with the older version of the BCF.
If you could publish that lookup, it would be great!
@ajudge After that I realized the Mesh Wizard was indeed not deprecated but it region dependent. Like for instance in selectwizard.js. It seems deactivated for EU and GB in many parts of your luci and morse feeds. It is working fine if the region is set to US but it is helping me, I am building a device for EU. morse_mesh11sd is already installed by default, mesh11sd and they are conflicting when trying to add it:
make[2] package/install
Collected errors:
* check_data_file_clashes: Package mesh11sd wants to install file /home/chrichri/blockchain-over-rf/morse-micro/openwrt2.9/openwrt/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/etc/init.d/mesh11sd
But that file is already provided by package * morse_mesh11sd
* check_data_file_clashes: Package mesh11sd wants to install file /home/chrichri/blockchain-over-rf/morse-micro/openwrt2.9/openwrt/build_dir/target-aarch64_cortex-a72_musl/root-bcm27xx/usr/sbin/mesh11sd
But that file is already provided by package * morse_mesh11sd
* opkg_install_cmd: Cannot install package mesh11sd.
make[2]: *** [package/Makefile:71: package/install] Error 255
make[1]: *** [package/Makefile:124: /home/chrichri/blockchain-over-rf/morse-micro/openwrt2.9/openwrt/staging_dir/target-aarch64_cortex-a72_musl/stamp/.package_install] Error 2
make -r world: build failed. Please re-run make with -j1 V=s or V=sc for a higher verbosity level to see what’s going on
make: *** [/home/chrichri/blockchain-over-rf/morse-micro/openwrt2.9/openwrt/include/toplevel.mk:233 : world] Erreur 1
Are you sure mesh11sdis helping? Should I get rid of morse_mesh11sd for my EU version then? Why is that 802.11s Halow not supposed for EU?
EU has a regulatory requirement in this frequency range for either a restrictive duty cycle or dynamic channel switching in response to conditions.
The 2.9 release implements the dynamic channel switching side of this, so it prevents any selection of specific channels. This means that it doesn’t work for mesh, as both our mesh implementations require a fixed channel.
To document how to make these modifications would effectively serve as documentation for how to avoid regulatory restrictions, so I’m going to defer to others here (@ajudge may have a better answer!).
