How to update to the latest Tailscale version?
-
24.11
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.82.5.pkgAll good, connected happily to headscale 0.26.0
-
Updated CE 2.7.2 to 1.84.0
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/tailscale-1.84.0.pkg -
so now that 2.8.0 CE is running Freebsd15, should we be grabbing the tailscale port from the Freebsd15: latest dir for installation?
-
@brinkmann I personally am not running 2.8.0 yet, but yes.
-
Over on https://www.freshports.org/security/tailscale. The chart that had the different version is gone, as of 2025-06-26. Also with pfSense CE moving to FreeBSD 15, I guess the repos are trying to consolidate. However, I used the chart to pick up the url to install Tailscale from. The last working url I had was https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.82.5.pkg, but simply changing 1.82.5 to 1.84.2 is no longer working. Has anyone been able to upgrade to 1.84.2 and if so what was your url. Thank you.
-
@smurph82
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.0.pkg
Latest -
@smurph82 I just upgraded to PfSense CE 2.8.0 and made sure to reupdate the Tailscale package myself. Here's the command I used to update: pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.2.pkg
It still gives the kernel version mismatch but it's still fine to ignore. -
Anyone else get the following notification from Tailscale?
And what, if anything, do we need to do?
-
@elvisimprsntr I got this mail too, an hour ago, also dont know, what we have to do right now...didnt had time yet to read full instructions and what consequences it will bring for us
-
@elvisimprsntr they're updating the backend control structure to use new IP addresses. If you use tailscale's own servers for management instead of a self-hosted Headscale instance, you just need to make sure that your pfsense firewall does not block connections to those IP ranges. By default, both ranges would be allowed so unless you've added restrictive rules, you don't need to do anything. I'd still recommend verifying that they're not blocked first though.
-
@veddy254 Thank you, got it
-
Thanks
ping 192.200.0.1 PING 192.200.0.1 (192.200.0.1): 56 data bytes 64 bytes from 192.200.0.1: icmp_seq=0 ttl=45 time=120.432 ms 64 bytes from 192.200.0.1: icmp_seq=1 ttl=45 time=129.154 ms 64 bytes from 192.200.0.1: icmp_seq=2 ttl=45 time=121.636 ms 64 bytes from 192.200.0.1: icmp_seq=3 ttl=45 time=132.175 ms -
J Jim Coogan referenced this topic
-
Updated CE 2.7.2 to 1.84.2_1
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/tailscale-1.84.2_1.pkg -
@elvisimprsntr said in How to update to the latest Tailscale version?:
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/tailscale-1.84.2_1.pkg
Thanks!
-
For 25.07 RC, this worked for me (run
shfirst)[25.07-RC][root@r1.lan]/root: sh # export IGNORE_OSVERSION=yes # pkg add https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.2.pkg # service tailscaled restart # tailscale up# tailscale version 1.84.2 go version: go1.24.4 # tailscaled -version 1.84.2 go version: go1.24.4 -
Updated CE 2.7.2 to 1.86.0, but I see there is already a 1.86.2. So you might want to hold off.
Note: Tailscale halted the rollout of version 1.86.0 for macOS on July 25, 2025, and for all other platforms on July 28, 2025, due to multiple regressions.
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/tailscale-1.86.0.pkg -
@elvisimprsntr Thanks, just updated, works fine!
-
Updated CE 2.7.2 to 1.86.2
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/tailscale-1.86.2.pkg -
Any ideas to why I get this error? Im running pfsense CE 2.8.0-RELEASE (amd64)
pkg add https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.2_1.pkg pkg: An error occured while fetching package -
@lbm_ said in How to update to the latest Tailscale version?:
https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/tailscale-1.84.2_1.pkg
pkg: An error occured while fetching packageI would recommend verifying the DNS settings in PfSense and verifying date/time is correct. Barring that, try again later and see if it still fails. I was able to successfully run the command on my 2.8.0 install (I didn't install it because I've already installed it) so it seems localized.
