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.
> 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
Alessandro
mercoledì 11 marzo 2026 15:40, Ilario via LibreMesh libremesh@??? ha scritto:
> Hi Alessandro!
> To me, it seems very useful :D
> More comments in-line:
>
> On 3/9/26 1:14 PM, ideo.alessandro via LibreMesh wrote:
>
> > Hi all, before opening a PR on this subject I want to discuss this
> > change with you, I implemented ubus APIs methods that can switch WAN
> > interface from ethernet to usb and vice versa,
>
> 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?
> If not, it would be useful if you could expand the documentation in the
> lime-packages/lime-docs/www/docs/lime-example.txt file explaining how to
> setup this in a permanent fashion.
>
> > giving the primary node
>
> 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).
>
> > of the mesh network WAN connectivity through usb tethering or 4G USB
> > dongle, might be useful if there is no wired network where the routers
> > are deployed
>
> Yes, 100% useful.
>
> > or if the router model has only one wireless chip radio0 so
> > the hotspot feature in LiMe cannot be used.
>
> Are you referring to this issue with lime-app?
> https://github.com/libremesh/lime-packages/issues/957
> We should also check of the lime-app client-of-hotspot feature then
> shares that connection with the rest of the mesh...
>
> Your system would then share the connection with the whole mesh? Should
> babeld-auto-gw-mode be updated to consider also this interface?
>
> > Let me know what you think and if it makes sense to open this PR.
>
> It sounds great to me :D
> Thanks!
> Ilario
>
> --
> Ilario
> iochesonome@???
> ilario@???
> --
> LibreMesh mailing list
> LibreMesh@???
> https://www.autistici.org/mailman/listinfo/libremesh
