On 3/11/26 7:18 PM, ideo.alessandro wrote:
> Hi Ilario!
>
>> Ah hem, sorry for the ignorance, can you give us an example of how the
>> end user would use such method? I never used such thing :P
>> Does this modify the configuration files? Can this be made permanent
>> over reboots?
>
> I picture this section in lime-app like a dropdown of available WAN interfaces to choose from eg eth0, eth1, usb0 etc. Maybe a line about the possibility of activating usb tethering connecting a smartphone to the router (usb0 appears only if the USB cable is connected and tethering is activated), also this feature works with the following modules included at build time: `kmod-usb-net` and `kmod-usb-net-rndis`. This feature uses uci:set, uci:save and uci:commit in the code so it is persistent across reboots.
It sounds great :D
Javier was implementing something for configuring the role of the
ethernet interfaces from lime-app.
The backend should be this one:
https://github.com/libremesh/lime-packages/tree/master/packages/lime-eth-config
I believe that this is not yet exposed in lime-app but better if Javier
confirms this.
The latest development version of lime-app should be this one (I am unsure):
https://github.com/javierbrk/lime-packages/tree/final-release/packages/lime-app
>> Would this work also on any other node? For example, currently if there
>> is more than a working WAN, Babeld is going to decide which is the best
>> to use, I believe (babeld-auto-gw-mode activates or deactivates the
>> route according to the results of watchping, that checks if the internet
>> connectivity works there).
>
> Yes, it would work on any other node, I tested the mesh with two routers with my branch deployed, one WAN connected on eth1 and the other WAN connected on usb0 (USB tethering) and I haven't encountered any problems.
>
>> Are you referring to this issue with lime-app?
>> https://github.com/libremesh/lime-packages/issues/957
>
> Yes that is the issue i'm referring to.
>
>> Your system would then share the connection with the whole mesh? Should
>> babeld-auto-gw-mode be updated to consider also this interface?
>
> I tried to connect to the WPA2 protected AP of a secondary node that is not WAN connected, but being the primary node of the mesh connected on usb0 I could ping DNS and resolve domain names, so it seems the system shares the connection with the whole mesh, I don't think that babeld-auto-gw-mode should be updated to consider the new interface.
>
> Thanks for the feedback and let me know what you think
I think this sounds great!
Thanks!
Ilario
