I have been unable to make this function. DSM 7 is still blocking traffic … reported IP addresses for source does not match tailscale website for host device. I have spent a day on this and have no choice but to delete tailscale and move on … but be aware !!! first reboot after installing (screwing around as per instuctions) and then uninstalling using package manager caused an improper shutdown for the NAS and corrupted a bunch of files … thats what I get for manually installing uncertified (by synology) software. Be verry verry careful …
Installing via the Synology Package center, then installing from https://pkgs.tailscale.com/stable/, then uninstalling from the package center might have left some files leftover. It shouldn’t have resulted in filesystem corruption unless the whole device was abruptly powered off or something similar.
Why does it take Synology a large amount of time to enable the latest version on their package centre?
- The Synology package center updates monthly.
- We submit a new binary well in advance of the monthly release, to get through their test process.
- If there is some problem in a newly released version, it will be a month until we can fix it. Therefore we submit Tailscale client versions which have been thoroughly exercised on the other platforms first.
Add it all up, and the Package Center is substantially behind the leading edge of development.
https://pkgs.tailscale.com/stable/ delivers the same version of the client as the other platforms.
https://pkgs.tailscale.com/unstable/ delivers the current state of the development tree, between the stable releases.
I just completed the upgrade to Tailscale 1.22 for my Synology running DSM 7 as recommended. Then I ran this script /var/packages/Tailscale/target/bin/tailscale configure-host as root through SSH. I was trying to use my Tailnet to secure my backup connection between two Synology NAS using Hyperbackup.
Everything appeared to work to allow outbound connections, but now I cannot connect to the upgraded Synology through an inbound Tailscale connection.
Is there another step I need to do after the running the script?
None of the services appear to be working for my upgraded Synology. Thanks to anyone who posts.
All my machines show connected, I cannot directly ping the affected Synology, but I can even run ‘tailscale ping x.x.x.x’. I can also ping the Tailnet address of the computer I am working on through SSH with powershell from the Synology NAS, but I cannot ping, directly, in the opposite direction. My ping only works via DERP to my Synology.
Nevermind, I figured it out. It turned out to be a Synology internal firewall issue. Thanks for the help.
1 Like
So I’m having issues
DS920+ DSM 7.0.1-42218 Update 3 (Mine)
DS220+ DSM 7.0.1-42218 Update 3 (Setup at parents home)
eero routers for both upnp enabled
Tailscale spk installed from stable channel
1.22.1-220017 installed on both
Ran the outbound commands on both
Set the startup script on both
I can ping each via SSH with no issue
Firewall not enabled on either Synology
I cannot get hyperbackup to see one another. I don’t know what could possibly be wrong.
Sharesync seems to work/see one another