Mirror of packages feed https://git.openwrt.org/feed/packages/atom?h=master 2026-03-06T15:12:22Z 2026-03-06T15:12:22Z Tung-Yi Chen 2026-03-05T18:24:22Z urn:sha1:04dd27674493ec018a7cd582538f7a60e9ce7803 The previous commit 09c14817 introduced TS_NO_LOGS_NO_SUPPORT but used procd_set_param for a subsequent environment variable. This overwrote the previous env setting, causing fw_mode to be missed. Switch to procd_append_param to ensure all environment variables are properly passed to the process. Signed-off-by: Tung-Yi Chen <cmtsij@gmail.com> 2026-01-31T19:14:48Z Nate Robinson 2026-01-31T03:38:15Z urn:sha1:09c148177ac72465dcdae07cf136d6cf4402e00e Set TS_NO_LOGS_NO_SUPPORT=true as documented here: https://tailscale.com/kb/1011/log-mesh-traffic?tab=linux#opt-out-of-client-logging Signed-off-by: Nate Robinson <nrobinson2000@me.com> 2023-09-15T01:49:47Z Tyler Young 2023-09-14T15:14:43Z urn:sha1:ccde8d18a1a7abda2f0e69de02fd9268c1157c32 This changes the default firewall method used by Tailscale to nftables. The 'autodetection' mode is only supported by arm64 and amd64 for now[1]. This causes mips devices to not do proper detection and incorrectly default back to iptables. I added a fw_mode variable to the tailscale.conf file that could be set to iptables for easy conversion for someone still using iptables. I was able to test on an older mips device and my current aarch64 without issues. Also a few readme updates to bring it up to the current status. 1. https://github.com/tailscale/tailscale/blob/dc7aa98b768bf82017aa5cc82a62dd4d685f811d/util/linuxfw/linuxfw_unsupported.go#L4C58-L4C58 Signed-off-by: Tyler Young <git@yfh.addy.io> 2023-08-28T13:59:55Z Tyler Young 2023-08-28T00:58:10Z urn:sha1:40d5ba9378127a852b0b4735b02798be17e2e12c Signed-off-by: Tyler Young <git@yfh.addy.io> 2021-04-29T07:10:58Z Jan Pavlinec 2021-04-28T12:13:06Z urn:sha1:229b34286db1a42731af45a53d2129943c64e4e9 Signed-off-by: Jan Pavlinec <jan.pavlinec@nic.cz>