Hi Federico, Thank you for the detailed explanation. I thought it might be useful. I am not in need of it that much. I understand that you answered so many feature requests and it is repetitive .. Sorry for that. I don't like to have my own code for Openwisp. I like to stick to the production release. 2 years ago i asked to add support for devices for firmware upgrades, and i added it locally on my server as it is already custom built openwrt for private hardware. and it would not help anyone else and you were right about that. Anyway I am using zerotier VPN for management and when i asked to add support for it, you were already drawing lines to go for it. But I had to implement a work-around for managing the Zerotier server. I chose to set up ztncui <https://github.com/key-networks/ztncui> for that back then. Thank you for the work that has been done to implement zerotier last google summer of code Looking forward to seeing it when it is production ready.
Regards, Muhammad On Fri, Mar 29, 2024 at 7:01 PM Federico Capoano <f.capo...@openwisp.io> wrote: > Hi Muhammed, > > This is one of those custom behaviours which I always recommend users to > build on their own. > Given OpenWISP openness and programmability, it's not hard at all to do > this, the application gives a lot of tools to do that. > If every time someone needs something like this we'd build it as a core > feature we'll end up with an unmaintainable pile of code. > It is possible to implement this in many ways, both on the openwrt side > with bash or lua or on the server side with python (using django signals, > the monitoring module has a signal for the health status change and > openwisp controller has the logic which can be used to send SSH commands). > I recommend picking what you like most and implement this on your own. I > honestly think building this on the router is easier. > > Regards > Federico > > On Thu, 28 Mar 2024 at 07:48, Mohammed Ismail <m.ism...@gmail.com> wrote: > >> Hi >> >> It would be useful if we can mark a device for a reboot upon next >> connection interval >> Default `option interval '120'` >> >> If the device is behind a VPN and it becomes unreachable for any reason. >> it would be useful for the admin to trigger a reboot upon the next >> connection attempt from device to the server. >> so the server side device gets marked for reboot. >> and from openwisp-config if the signal received from the server would >> execute. >> >> it could be a whole command to execute on the next connection interval or >> just a reboot. >> >> >> Best regards. >> Muhammed Al-Qadhy. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OpenWISP" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to openwisp+unsubscr...@googlegroups.com. >> To view this discussion on the web, visit >> https://groups.google.com/d/msgid/openwisp/CAKOr0YQRpWw%3DyXAqcXu30jKwPT6H-P5tb9RqYvX5pTjkArFTFw%40mail.gmail.com >> <https://groups.google.com/d/msgid/openwisp/CAKOr0YQRpWw%3DyXAqcXu30jKwPT6H-P5tb9RqYvX5pTjkArFTFw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to openwisp+unsubscr...@googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/CAAGgX6%2By_R6YPCDWt2%3D4BWrCa%2B34y0PihQr1OxJ8omDjhPnaBA%40mail.gmail.com > <https://groups.google.com/d/msgid/openwisp/CAAGgX6%2By_R6YPCDWt2%3D4BWrCa%2B34y0PihQr1OxJ8omDjhPnaBA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAKOr0YRq1w8Q64VJ%3D5%3DvUX0Pt0CdQ6fFZVX_D9ZQJ3NdGD2fBw%40mail.gmail.com.
