packages, branch master

ripe-atlas: add get_key and probeid to init script

2026-10-05T20:56:11Z

Previous package (atlas-sw-probe) printed the public key to register a new probe with "/etc/init.d/atlas get_key" and the probe ID with "/etc/init.d/atlas probeid", and the documentation [1] [2] tells users to run get_key. Add both back as "/etc/init.d/ripe-atlas get_key" and "/etc/init.d/ripe-atlas probeid". For a probe that has registered since boot, get_key prints the probe ID instead of asking to register it. [1] https://docs.turris.cz/basics/apps/atlas/ [2] https://github.com/openwrt/packages/blob/d2aeaf041bc0/net/atlas-sw-probe/files/atlas.readme Fixes: b77264c9226c ("ripe-atlas: add new package") Signed-off-by: Josef Schlehofer

shunt: fix rpcd status call

2026-10-05T19:19:59Z

* define tproxy_available() before render(): ucode resolves the name when render() is compiled, so the later definition left it null and every status call failed - LuCI showed "no answer from the backend" Signed-off-by: Dirk Brenken

shunt: update to 0.1.11

2026-10-05T18:35:54Z

* add the per-policy action 'tproxy': hands the selected tcp/udp traffic to a transparent proxy on the router (option tproxy_port), delivered to 127.0.0.1/::1 via a 'local default dev lo' policy table * restore rules for tproxy flows carry the tproxy statement on every packet - a mark alone loses udp flows to the proxy's reply socket * a proxied flow whose listener is gone is always dropped: its conntrack entry was never NATed and would leave with the client's own address; fallback 'main'/'block' decides about new flows only * no tproxy rules in output (the kernel rejects the statement there), no keep_local rule for tproxy (main would forward socket-assigned packets) * tproxy policies are skipped as an issue without kmod-nft-tproxy instead of failing the whole nft batch * shunt check and the rpcd status report tproxy policies * readme update Co-authored-by: Claude Signed-off-by: Dirk Brenken

zoneinfo: update to 2026e release

2026-10-05T17:40:11Z

Package version and file hashes changed. Signed-off-by: Vladimir Ulrich

duperemove: add new package

2026-10-05T14:47:02Z

duperemove is a simple tool for finding duplicated extents and submitting them for deduplication. It will de-dupe results on btrfs. Co-Authored-By: Claude Sonnet 5 Signed-off-by: Keith T. Garner

weechat: add new package

2026-10-05T13:30:14Z

WeeChat (Wee Enhanced Environment for Chat) is a fast, light and extensible chat client with a modular architecture and relay support. This package provides: - weechat-minimal (default variant): headless daemon without ncurses, suited for routers and for use through relay web or mobile clients. - weechat-full: the ncurses terminal client as well as the headless daemon. - Config.in: menuconfig options for zstd, cJSON and the scripting plugins (Python, Lua, Ruby, Perl, Tcl). - procd init script and UCI configuration. irc.conf, relay.conf and logger.conf are generated from UCI, and the values written to them are checked first. The relay refuses to start without a password and disk logging is off by default to protect flash storage. Passwords are stored as hex encoded WeeChat expressions, so characters like ';' or '${' can neither run commands nor get evaluated. - The daemon runs as the weechat user. /etc/weechat, /etc/weechat/tls and /var/run/weechat belong to root. The init script only changes paths whose parent the daemon cannot modify, except for the generated files in the sticky config directory, which it renames into place without following symlinks. Of the log directories it only creates the default /var/log/weechat. - test.sh: checks the binaries and plugins, the init script validation, the directory layout, the values WeeChat reads back from the generated files and that the relay listens. Signed-off-by: Josef Schlehofer

ripe-atlas: take over maintainership

2026-10-05T13:29:39Z

Tiago Gaspar has not been active in this repository since May 2026 and did not respond when Alexandru Ardelean offered to pick the package up in https://github.com/openwrt/packages/pull/30030. Michel Stam, who wrote RIPE's own OpenWrt packaging, has not taken part here, and since 5120 that packaging lists the RIPE Atlas Team instead of him. I run a probe and test the package on Turris OS, so take it over. Signed-off-by: Josef Schlehofer

ripe-atlas: migrate from atlas-sw-probe

2026-10-05T13:29:39Z

ripe-atlas-probe provides atlas-sw-probe, but carries nothing over, so an upgraded probe would come up with a new key, which RIPE rejects until its host enters it on atlas.ripe.net. Take over the key and the settings of atlas-sw-probe in a uci-defaults script of ripe-atlas-probe, and stop and disable atlas once the key is in place. A failed run is retried on the next boot. Until it succeeds, the init does not start the probe, so the key is never used twice and no new key is created. Until the key is in place, the init logs that it waits. Signed-off-by: Josef Schlehofer

ripe-atlas: clean up the Makefile

2026-10-05T13:29:39Z

- Build the tree once, the variants only install different files. Both provide ripe-atlas, with the probe as the default variant, so that apk, whose packages carry no CONFLICTS, cannot install both. - Select busybox tee, cmp and find with the options that the registration and the init use, and drop jsonfilter and the busybox ps, killall, tar, ntpd and bunzip2 selects, which nothing installed uses. - Do not keep /etc/ripe-atlas/mode, the init rewrites it on every start. - List all licenses: the measurement busybox is BusyBox (GPL-2.0-only) with libevent (BSD-3-Clause and ISC) linked in, and five of the shell libraries are LGPL-2.1-or-later. - Link the measurement applets in one loop. Signed-off-by: Josef Schlehofer

ripe-atlas: restart the probe on config changes

2026-10-05T13:29:39Z

Restart the probe when /etc/config/ripe-atlas changes. procd does not restart an instance when any of these options changes, and up to OpenWrt 25.12, when it stops one, it signals only the main script, so the measurement daemons, the ssh tunnel and telnetd would keep running. Stop and start the whole service instead. On stop, take the processes from the instance's cgroup, which holds exactly those of the probe, and fall back to the ripe-atlas group only when it holds none. Signed-off-by: Josef Schlehofer