Does advertise-routes work on Synology?


I am trying to add a couple of subnet routes to Tailscale on a Synology DS218+. The Tailscale command executes without error. However, I am not able to ping any ip’s in the subnets that were added. A created a temporary ubuntu machine in the same subnet and issued the exact shame command and I can ping the added subnets from the clients. IP forwarding is enabled on the Synology.

Thanks for the help.

It’s possible but very tedious to set up currently and varies based on which version of DSM and which Synology kernel.

Our next release makes it automatic, though.

Some background is in Document how to enable IP forwarding · Issue #52 · tailscale/tailscale-synology · GitHub



Can you let me know how to enable subnet routing on Synology with the 1.8 release? I don’t seem to be able to find it. And, even if I use the iptables commands that I used before, routing doesn’t seem to work anymore.


Hi @bradfitz. Should this be working automatically now?

I’ve just installed the latest Tailscale 1.10.0 release on my Synology DS118 NAS (running DSM 6.2.4-25556). I SSH’d into the NAS and ran:

sudo tailscale up --reset --advertise-routes=

The idea was to expose the 10.196.0.X subnet. The response to this is Success. and the subnet shows up in the Tailscale admin interface. However, visiting IP addresses on that subnet does not work.

I’m not too sure if I should have followed any additional steps to get this working or if it is just not expected to work at the moment?

One common issue when subnet routes don’t seem to work:

  • Windows, MacOS, iOS, and Android all accept subnet routes by default
  • Linux does not accept subnet routes by default. tailscale up --accept-routes must be used.

This is partly historical, as Linux was the first client developed and the others got the benefit of more experience in operating Tailnets, and partly that Linux gets used in routing applications much more often where being explicit about routes is often an advantage.

Yep, that’s a good point which we came across that with a Linux install actually. It would be helpful to make this clearer in the installation instructions. Unfortunately, it didn’t help with getting subnets working with our synology NAS however.

I never got subnet routes to work on Synologoy after version 1.6.0. I had to revert back to that version to make it work. And then I had to follow the instructions on the link in the second message in this thread.