11 Jul
2019
11 Jul
'19
2:40 p.m.
Old thread, but I guess answers are always useful.
On 6/15/19 7:15 PM, Patricio Gibbs via lime-users wrote:
In my experience LuCI is very useful for editing
configuration and
monitoring the network. LuCI offers an intermediate step between the
simplicity of lime-app and the complexity of SSH command line
configuration. Given this usefulness and the alpha status of lime-app, I
will likely install LuCI on devices for the moment, and maybe uninstall
lime-app to save space and RAM until lime-app reaches release status.
Would this interfere with the functioning of LibreMesh?
Libremesh overrides LuCi configurations, so if you configure things with
LuCi and then you apply libremesh configs, then you would be loosing
configurations.
so in a way yes, it would be interfering (depending the case).
For example, with LuCI I can:
- set static routes for local services
Why you need routes for local services? How are you setting them?
In my case an entry on /etc/hosts is enough (in each of the mesh
devices), or setting the hostname of the device to whatever name I want
it to be called and use that name as url :)
- configure WWAN (internet connection via wifi)
this will be overwritten by lime if you do lime-apply
- set a static address for WAN client (this was
necessary in one of our
networks)
this will be overwritten by lime if you do lime-apply
can be done with lime (check documentation)
- change wifi SSID, hide SSID, change wifi password,
this will be overwritten by lime if you do lime-apply
can be done with lime (check documentation)
create MAC-based access control list
not sure... what do you use it for? has the community asked to filter by
mac? in which case?
The following don't harm libremesh
What do you use them for?
would be interesting to know the usecase
- see what devices are connected
- monitor network traffic quantity and connections
- look at logs
- install and remove packages
Without LuCI, I either have to:
1) give up on these things,
2) configure them at the moment of compiling firmware and reflash the
device, or
3) learn how to do these things via SSH (and forget about having pretty
charts on the command line).
I would definitely encourage to interact over ssh... it is far more
powerful. But still I understand that the learning curve can be steeper.
Regards,