routing/naywatch, branch master

treewide: install configs with INSTALL_CONF (0600)

2025-11-10T09:38:36Z

Use INSTALL_CONF instead of INSTALL_DATA to install configuration files under /etc with correct permissions. This improves security by ensuring config files are not world-readable. INSTALL_DATA sets mode 0644, while INSTALL_CONF sets mode 0600. Signed-off-by: Josef Schlehofer

treewide: remove AUTORELEASE

2023-04-27T15:14:16Z

OpenWrt/packages removed AUTORELEASE treewide. Remove it also in the routing feed. This is just copied from [0] with modification to the sed cmd because it was not working for the routing feed: The following temporary change was made to the core: diff --git a/rules.mk b/rules.mk index 57d7995d4fa8..f16367de87a8 100644 --- a/rules.mk +++ b/rules.mk @@ -429,7 +429,7 @@ endef abi_version_str = $(subst -,,$(subst _,,$(subst .,,$(1)))) COMMITCOUNT = $(if $(DUMP),0,$(call commitcount)) -AUTORELEASE = $(if $(DUMP),0,$(call commitcount,1)) +AUTORELEASE = $(if $(DUMP),0,$(shell sed -i "s/\$$(AUTORELEASE)/$(call commitcount,1)/" $(CURDIR)/Makefile)) all: FORCE: ; And this command used to fix affected packages: for i in $(cd feeds/routing; git grep -l PKG_RELEASE:=.*AUTORELEASE | \ sed 's/\/Makefile$//';); do make package/$i/download done [0] - https://github.com/openwrt/packages/commit/0c10c224be81f9221dabfab449855ab6718d2a0c Signed-off-by: Nick Hainke

naywatch: add log when naywatch activates

2022-06-10T08:25:43Z

Naywatch now prints naywatch: Naywatch Activated! when becoming active. Signed-off-by: Nick Hainke

naywatch: fix reboot_now

2022-04-01T08:23:56Z

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

naywatch: introduce kick-count

2022-01-13T09:01:09Z

Check multiple rounds if neighbors are available before kicking. This should reduce unneeded reboots. Signed-off-by: Nick Hainke

naywatch: fix mode without watchdog

2022-01-13T07:56:32Z

The if-condition was always evaluated to be true. Signed-off-by: Nick Hainke

naywatch: warn user

2021-11-15T18:37:03Z

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

naywatch: fix procd handling

2021-10-01T09:53:10Z

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

naywatch: add naywatch

2021-08-01T18:57:12Z

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 Tested-by: Simon Polack Signed-off-by: Simon Polack