Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

admin/freifunk/assistent/wireless - Failed to execute cbi dispatcher target #799

Open
ilippert opened this issue May 12, 2020 · 1 comment

Comments

@ilippert
Copy link

Bug report

What is the problem?
I want to use the assistant to change bandwidth and location of the router.

Instead of being able to do this, I get this error

Failed to execute cbi dispatcher target for entry '/admin/freifunk/assistent/wireless'.
The called action terminated with an exception:
...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:361: bad argument #2 to 'tonumber' (integer expected, got string)
stack traceback:
 [C]: in function 'tonumber'
 ...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:361: in function 'getchannel'
 ...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:160: in function 'i'
 /usr/lib/lua/luci/model/uci.lua:203: in function 'foreach'
 ...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:122: in function 'write'
 ...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:100: in function 'parse'
 /usr/lib/lua/luci/cbi.lua:201: in function 'parse'
 /usr/lib/lua/luci/cbi.lua:201: in function 'parse'
 /usr/lib/lua/luci/cbi.lua:559: in function 'parse'
 /usr/lib/lua/luci/dispatcher.lua:871: in function </usr/lib/lua/luci/dispatcher.lua:863>

This occurs on a gl-mt300n-v2 router

What is the expected behaviour?
I should be able to use the assistant to adapt bandwidth.

Firmware Version:
git-19.249.30590-a328a50) / Freifunk Berlin Development abc3c31

Site Configuration:
I have freshly installed firmware. Then restored an old configuration from the same router that has worked successfully for years.

@SvenRoederer
Copy link
Contributor

This is a very old Development build (a branch from master from 13 Dec 2019). Can you retest with a recent build? There have been some upstream fixes, which already might fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants