tailscale: fix fw_mode env by using append_param

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>
This commit is contained in:
Tung-Yi Chen
2026-03-06 02:24:22 +08:00
committed by Wesley Gimenes
parent 0f574b5f5b
commit 04dd276744
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=tailscale
PKG_VERSION:=1.94.2
PKG_RELEASE:=1
PKG_RELEASE:=2
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://codeload.github.com/tailscale/tailscale/tar.gz/v$(PKG_VERSION)?
+1 -1
View File
@@ -31,7 +31,7 @@ start_service() {
procd_set_param env TS_DEBUG_FIREWALL_MODE="$fw_mode"
# Disable logging to log.tailscale.com
procd_set_param env TS_NO_LOGS_NO_SUPPORT=true
procd_append_param env TS_NO_LOGS_NO_SUPPORT=true
# Set the port to listen on for incoming VPN packets.
# Remote nodes will automatically be informed about the new port number,