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

luci-app-ffwizard-falter: Assistent fails with Lua stack trace when entering mesh IP without CIDR notation #319

Open
jakoblell opened this issue Jul 15, 2022 · 1 comment
Milestone

Comments

@jakoblell
Copy link

Maintainer: @pmelange
Environment: EAP225-outdoor-v3, Current Snapshot built via falter-builter

Description:

I've just set up a new Freifunk router and accidentally entered the mesh IP address as a plain address instead of a full CIDR notation with the /32 affix in the last step of the asisstent. When trying to finish the assistent, it was failing with the following Lua stack trace:

...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:264: attempt to index local 'dhcpmeshnet' (a nil value)
stack traceback:
	...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:264: in function 'write'
	...b/lua/luci/model/cbi/freifunk/assistent/wireless.lua:110: in function 'parse'
	/usr/lib/lua/luci/cbi.lua:248: in function 'parse'
	/usr/lib/lua/luci/cbi.lua:248: in function 'parse'
	/usr/lib/lua/luci/cbi.lua:713: in function 'parse'
	/usr/lib/lua/luci/dispatcher.lua:1536: in function '_form'
	/usr/lib/lua/luci/dispatcher.lua:1059: in function 'dispatch'
	/usr/lib/lua/luci/dispatcher.lua:483: in function </usr/lib/lua/luci/dispatcher.lua:482>

This is an error which can easily happen to normal users and should therefore be handled more gracefully (i.e. highlighting the text field with the incorrect input, this is already implemented for other errors such as a missing meshing IP for one of the radio interfaces).

Version info:

opkg search /usr/lib/lua/luci/model/cbi/freifunk/assistent/wireless.lua
luci-app-ffwizard-falter - git-22.120.34984-b41e05d
@Akira25 Akira25 added this to the falter-1.2.3 milestone Sep 20, 2022
@Akira25
Copy link
Member

Akira25 commented Jan 9, 2023

Just tested this on a 1.2.2-node. This error doesn't happen there. As only snapshot-images might be affected, postponing this to a later release.

@Akira25 Akira25 modified the milestones: falter-1.2.3, falter-1.3.0 Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants