openwrt-packages/net/tailscale/test.sh

#!/bin/sh

case "$1" in
	tailscale)
		tailscale version | grep "$2"
		;;
	tailscaled)
		tailscaled -version | grep "$2"
		;;
esac
tailscale: add version tests Signed-off-by: Michal Vasilek <michal.vasilek@nic.cz> 2022-10-12 19:30:37 +02:00			`#!/bin/sh`

tailscale: update to 1.36.0 - Update tailscale to version 1.36.0 - Patch iptables support Tailscale does not (yet) support nftables. Tailscale allows running with --netfilter=off allowing end-user to create his own firewall rules, but this affects only tailscale cli, not tailscaled daemon, so connection cannot be made without error telling that tailscaled was unable to determine execute iptables for determining it's version. There is a work-around for those who do not want nft-iptables compatibility package; they can create a script to /usr/bin/iptables which responds to --version argument and echos fake version string and on any other arguments or no arguments, just exits. After this procedure and starting tailscale cli with netfilter off- it works. Openwrt has moved on to nftables, so iptables manipulation seems unnecessary. Especially for other reasons, on Openwrt, firewall should be configured on it's own, because firewall rules made by other software, such as tailscale, loose their firewalling rules when firewall restarts. So I patched it to allow "fake" iptables pointing to executable /bin/false and ignoring version request. And I also set cli to default to netfilter off setting. If still end-user wants to use iptables, this patch does not make it impossible; just install iptables, or nft-iptables, and run tailscale with argument --netfilter=on and it works out as it did before, tailscaled daemon still matches with iptables if it is found in $PATH. Signed-off-by: Oskari Rauta <oskari.rauta@gmail.com> 2023-02-01 08:13:44 +01:00			`case "$1" in`
			`tailscale)`
			`tailscale version \| grep "$2"`
			`;;`
			`tailscaled)`
			`tailscaled -version \| grep "$2"`
			`;;`
			`esac`