packages/net/olsrd, branch master

olsrd: record why the version check logs "Terminated"

2026-08-13T21:21:19Z

olsrd leaves through olsr_exit(), which ends the process with raise(SIGTERM) rather than returning from main, so the shell reports "Terminated" right after the version banner even for a plain `olsrd -v`. The pipeline status comes from grep, so the check itself is unaffected, but the line in the CI log looks like a failure to anyone reading it. Note it in the script so the next reader does not go hunting. Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5

olsrd: report the packaged version in the binary

2026-08-13T21:21:19Z

olsrd builds its version banner from the VERS make variable, which defaults to the upstream development version "pre-0.9.9", so `olsrd -v` never mentioned the version the package was built from. The source tarball carries no git metadata either, so the git hash in that string is always zero: olsr.org - pre-0.9.9-git_0000000-hash_5fd8976... Pass PKG_VERSION as VERS, the same way alfred and batctl already pass REVISION, so the banner identifies the packaged revision. This also lets test-version.sh check the real version instead of merely confirming that the binary starts. Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5

olsrd: reject non-address input before eval in olsrd-neigh.sh

2026-08-13T21:21:19Z

olsrd-neigh.sh builds shell variable names from data announced by other nodes in the mesh and passes them through eval: eval IP_${ip//[.:]/_}="$hostname" eval re-parses the string after the quotes have been consumed by the first expansion pass, so a hostname of `x;reboot` announced by a remote node is executed as a command on every node that runs the utility. The values come from the nameservice plugin's hosts file and from the txtinfo plugin, both of which carry unauthenticated remote input. Discard entries containing anything other than the characters that can legitimately appear in an address or hostname before they reach eval, in both places. Reported-by: openwrt-ai[bot] Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5

olsrd: initialize the LQ multiplier list pointer in the ubus handler

2026-08-13T21:21:19Z

The ubus add_interface handler allocates a struct olsr_lq_mult with malloc() and assigns only ->addr and ->value, leaving ->next uninitialized before the node is published into cnf->lq_mult. olsrd walks that list with for (mult = cnf->lq_mult; mult != NULL; mult = mult->next) so the first traversal follows an indeterminate pointer. Chain the new node onto the existing list, which is what the configuration file parser does for LinkQualityMult in src/cfgparser/oparse.y. This also makes the orig_lq_mult_cnt++ on the next line consistent, since the entry really is prepended to the list instead of replacing it. Reported-by: openwrt-ai[bot] Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5

olsrd: add missing jshn dependency to olsrd-utils

2026-08-13T21:21:19Z

The only file shipped by olsrd-utils is olsrd-neigh.sh, which sources /usr/share/libubox/jshn.sh on its third line. That file belongs to the jshn package, which is not pulled in by the olsrd -> libubus -> libubox dependency chain, so on a minimal image the utility fails immediately with "not found". Reported-by: openwrt-ai[bot] Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5

olsrd: fix respawn_threshold lookup in the IPv6 init script

2026-08-13T21:21:19Z

The UCI option is spelled respawn_threshold, as documented in files/olsrd6.config and as read by files/olsrd4.init, but the IPv6 init script looks up _respawn_threshold. The lookup never matches, so a user-configured value is silently ignored and the built-in default of 3600 is always used. Reported-by: openwrt-ai[bot] Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5

olsrd: add new package

2026-08-13T21:21:19Z

olsrd is the olsr.org implementation of the Optimized Link State Routing protocol, together with its plugins packaged as olsrd-mod-* subpackages. Moved from the openwrt/routing feed, as discussed in https://github.com/openwrt/routing/issues/184. Signed-off-by: Josef Schlehofer Co-authored-by: Claude Fable 5