routing/naywatch/files, branch masterMirror of routing feedhttps://git.openwrt.org/feed/routing/atom?h=master2022-06-10T08:25:43Znaywatch: add log when naywatch activates2022-06-10T08:25:43ZNick Hainke2022-06-10T06:46:28Zurn:sha1:09d5ceb9230b907029a3e09858ef181ff85e3913
Naywatch now prints
naywatch: Naywatch Activated!
when becoming active.
Signed-off-by: Nick Hainke <vincent@systemli.org>
naywatch: fix reboot_now2022-04-01T08:23:56ZNick Hainke2022-04-01T08:16:56Zurn:sha1:65f747a8bcf19e0271e6bbe04c2432f9a93cc406
Naywatch should first try to reboot normally, and if that does not work
do a hard reboot. However, the hard reboot was never called.
Signed-off-by: Nick Hainke <vincent@systemli.org>
naywatch: introduce kick-count2022-01-13T09:01:09ZNick Hainke2022-01-13T08:34:44Zurn:sha1:24285ce4fcd56aa806bdbe9ac16cbfed0a81d2f8
Check multiple rounds if neighbors are available before kicking. This
should reduce unneeded reboots.
Signed-off-by: Nick Hainke <vincent@systemli.org>
naywatch: fix mode without watchdog2022-01-13T07:56:32ZNick Hainke2022-01-13T07:46:31Zurn:sha1:cf34c5a4a1ace3f8eeac2d2b9b8539e085e8fabf
The if-condition was always evaluated to be true.
Signed-off-by: Nick Hainke <vincent@systemli.org>
naywatch: warn user2021-11-15T18:37:03ZNick Hainke2021-11-15T18:22:56Zurn:sha1:ce0b8b1e553ed749e398d8122f7cc5a0692d7372
Naywatch in combination with the watchdog can be tricky and dangerous
when doing a sysupgrade. Add a warning to always stop naywatch first and
check if procd took control over the watchdog again.
Also change use_watchdog to '0'.
Signed-off-by: Nick Hainke <vincent@systemli.org>
naywatch: fix procd handling2021-10-01T09:53:10ZNick Hainke2021-10-01T08:55:36Zurn:sha1:e35255710bda08f162a185be8c460b6a80e19fb1
Sometimes, naywatch can not handover the watchdog to procd again using
ubus. We need to call the same ubus command multiple times until procd
takes over control again.
Signed-off-by: Nick Hainke <vincent@systemli.org>
naywatch: add naywatch2021-08-01T18:57:12ZNick Hainke2021-07-13T15:33:42Zurn:sha1:1088e65440b1f2f67b40e6a3073571da14f6a4b3
The network may crash on the SoCs, but the SoC itself does not. This
leads to a node no longer being accessible in a mesh network. If the
node is placed in a location that is not easily accessible, e.g. in a
high tower, it can cause a lot of problems. Therefore we check the
link-local connectivity on the configured interfaces.
Signed-off-by: Nick Hainke <vincent@systemli.org>
Tested-by: Simon Polack <spolack+git@mailbox.org>
Signed-off-by: Simon Polack <spolack+git@mailbox.org>