Hi,
thanks Ufo - this was helpful. The problem is exactly in the file you
linked:
https://github.com/openwrt/luci/blob/master/contrib/package/meshwizard/files/usr/bin/meshwizard/helpers/setup_wifi.sh#L49
You need to change that "if" statement to something like:
if [ -z "${1/cfg[0-9a-fA-F]*/}" ]
as i know, meshkit (as an webinterface for using the imagebuilder) only
"ask" for the settings and generate the firmware-image with desired
packages.
the generation of settings on the device should be in meshwizard, so
f.i.
https://github.com/openwrt/luci/blob/master/contrib/package/meshwiza
Hi,
I don't think it is related to that commit since it does not change the
detection logic, I rather guess the problem is due to some race
condition somewhere.
I took a quick look at the meshkit repo but wasn't able to figure out
the exact place where the wifi config is generated.
~ Jo
signa
a sample config can be found at https://plan.leipzig.freifunk.net/issues/360
p.s.
if you want to reproduce that with a physical device, please be careful
with luci/meshwizard. there were some changes on busybox and the
required pull-request isnt accepted yet on openwrt
https://github.com/openw
Hi Ufo,
can you please provide such a broken wireless configuration here?
Usually those extra wifi sections are added if no previous config for
the phy is found in the config, so it seems something in the Freifunk
specific settings is odd.
~ Jo
___
Le
im using imagebuilder via meshkit (and luci/meshwizard) to configure
LEDE-devices.
with newest lede-trunk the behaviour changed, now there is one more
wifi-ap on each device.
its called "LEDE" and doesnt make to much sense for me:
*in config its called "default_radio0", while our other wifis a
