00:00
<
jow >
you should see a bunch of chatter in response to `ubus call uci apply`
00:00
<
jow >
this will emit at least one config change event for wireless
00:00
<
jow >
which in turn should trigger more actrivity
00:00
<
jow >
*ubus monitor
00:01
<
jow >
ubus monitor will also show the data back-and-forth between mac80211.sh & netifd
00:02
<
jow >
my hunch is that the timing of the luci actions triggers the bug
00:02
<
jow >
need to hit the bed now, bbl
00:02
<
\x >
ap is out and such, as for ubus monitor, i got kinda flooded by usteer mssages
00:09
<
\x >
here, seems to work, im disabling radio1
00:09
<
\x >
this is with the button on luci
00:12
<
\x >
>"radio1":{"up":false,"pending":false,"autostart":true,"disabled":true,
00:14
<
djfe >
I tested my Linksys MR8300 as well (read 01:53:54 CEST), ipq40xx is not affected by the LuCI bug. But thanks for taking a look at yours as well :)
00:46
goliath has quit [Quit: SIGSEGV]