[Plugin] Tailscale

[EDACerton]

Tailscale

 

Tailscale is a VPN service that makes the devices and applications you own accessible anywhere in the world, securely and effortlessly. The service handles complex network configuration on your behalf so that you don't have to. Network connections between devices pierce through firewalls and routers as if they weren't there, allowing for direct connections without the need to manually configure port forwarding.
        
After installing, open the console and use the tailscale CLI to configure: https://tailscale.com/cli

Configuration

The plugin provides an option to "Enable IP Forwarding" via the Settings page. This is useful for running exit nodes or subnet routers.

 

Most users will simply need to run tailscale up and log in via their web browser. You may also want to disable key expiration for your server (either by using an auth key when connecting, or afterwards via the Tailscale admin console).

Contributing

Issue reports and pull requests are welcome on Github: https://github.com/dkaser/unraid-tailscale

Edited May 9 by EDACerton
Update

[EDACerton]

Changelog

https://github.com/dkaser/unraid-tailscale/releases

Edited May 11 by EDACerton

[carp969]

This is great, good work.

One question is how does it handle the frequent updates from Tailscale?  Will it be via updates published for the plugin?

[EDACerton]

Yes -- fortunately, that's simple, and documented on the repository, so someone could easily fork it if someday that became necessary (not that I plan on that, but I plan for it).

[ptichalouf]

i use this cmd personaly, i hope this will help someone  

 

with this cmd before still in unraid terminal

 

echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf

 

 

tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24

Edited March 26 by ptichalouf

[ADvorsky]

just for your info.... tailscales magic dns might break your docker containers.

/etc/resolv.conf gets copied to all freshly started contaieners from the host, which points to a dns not existing inside the container...

disabling magic dns resolved this issue.

[EDACerton]

2 hours ago, ptichalouf said:

i use this cmd personaly, i hope this will help someone  

 

with this cmd before still in unraid terminal

 

echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf

 

 

tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24

 

For everyone else’s benefit — as a general rule, if you aren’t already familiar with the extra flags here (and know you need them), just run tailscale up.
 

FYI -- the first three commands won't survive reboot -- Unraid doesn't act like a traditional linux system, any changes that are made to /etc are lost when the system is rebooted.

 

Fortunately, in this case the impact would be fairly small -- Unraid already sets IPv4 forwarding, so the only thing that you should lose would be IPv6 via the exit node. If you want for that to persist, you would need to modify sysctl on boot using a technique such as https://forums.unraid.net/topic/61544-how-to-modify-etcsysctlconf-on-boot/. This is something that I might look as adding as an option in an update to the plugin.

 

 

Edited March 26 by EDACerton

[EDACerton]

9 minutes ago, ADvorsky said:

just for your info.... tailscales magic dns might break your docker containers.

/etc/resolv.conf gets copied to all freshly started contaieners from the host, which points to a dns not existing inside the container...

disabling magic dns resolved this issue.

This can be the case for Docker containers that are connected to the default "bridge" network, but that is expected behavior from Docker.

 

If you want for Docker containers to have internal DNS resolution (i.e., being able to resolve the other containers by name), you need to create a user-defined bridge (reference: Docker documentation). Docker containers connected to a user-defined bridge get an internal DNS server.

[gustyScanner]

Fantastic plugin, thank you for working on it! Exit node as a setting to persist across reboots would be fantastic.

[EDACerton]

13 minutes ago, gustyScanner said:

Fantastic plugin, thank you for working on it! Exit node as a setting to persist across reboots would be fantastic.

Just for clarity -- exit node will persist across reboots, the only thing that doesn't is enabling IPv6 forwarding.

[Nexus]

I installed this plugin then ran 

 

tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24

 

Now, my system is unresponsive and I had to do a hard reboot and it's not coming back

 

I need to go hookup a keyboard and display to try and recover. Any ideas where to start?  

[mattgob86]

FYI, https://tailscale.com/cli just returns a 404 message for me

[EDACerton]

1 minute ago, mattgob86 said:

FYI, https://tailscale.com/cli just returns a 404 message for me

Sorry about that, the forum helpfully put the period at the end of my sentence on the link. It's fixed

[aroo85]

9 minutes ago, mattgob86 said:

FYI, https://tailscale.com/cli just returns a 404 message for me

The link as a . at the end it should be https://tailscale.com/cli

[EDACerton]

17 minutes ago, Nexus said:

I installed this plugin then ran 

 

tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24

 

Now, my system is unresponsive and I had to do a hard reboot and it's not coming back

 

I need to go hookup a keyboard and display to try and recover. Any ideas where to start?  

Something about this command probably didn't mesh nicely with your network... it's enabling several extra features that affect how traffic moves.

As a general rule, start with tailscale up, only add other flags if you know you need them.

 

To fix your connection, I'd run the following from CLI:

tailscale set --accept-routes=false --advertise-exit-node=false --advertise-routes=""

 

Edited March 26 by EDACerton

[Nexus]

3 hours ago, EDACerton said:

Something about this command probably didn't mesh nicely with your network... it's enabling several extra features that affect how traffic moves.

As a general rule, start with tailscale up, only add other flags if you know you need them.

 

To fix your connection, I'd run the following from CLI:

tailscale set --accept-routes=false --advertise-exit-node=false --advertise-routes=""

 

Thanks. I opted to boot with no plugins loaded and delete the plugin and plugins directory and reboot. I'll wait a bit until wiser ones than me can play around with this  

 

Edited March 27 by Nexus

[pzg417]

Excellent! Big fan of tailscale. Many thanks!

[EDACerton]

23 hours ago, Nexus said:

Thanks. I opted to boot with no plugins loaded and delete the plugin and plugins directory and reboot. I'll wait a bit until wiser ones than me can play around with this  

 

If what you want is to be able to connect to Unraid remotely, and Docker containers running on bridge networks, then you can install the plugin and run tailscale up (no flags), that should work just fine.

 

The other features are all more advanced networking, so adding them incorrectly can cause issues.

[SomeoneOnLine]

All though I haven't tried this plugin.....yet. I definitely will be once I get back on land in a few days. Thanks for this. Now to see if and when someone can make a headscale plugin to pair up with this plugin.

 

Thanks for this!

 

~SOL

Edited March 27 by SomeoneOnLine
spell check!

[PilaScat]

Tried with advertise route 192.168.1.0/24 and exit node, all working like a charm, thanks, I hope next boot it remains

[Brandon_K]

Thank you thank you for this, as well as the update!  I've been waiting for this since the first day I installed the Tailscale container.

Up and running with exit node, zero issues.

[EDACerton]

I published an update yesterday (version 2023.03.27) that adds a setting to enable IPv6 forwarding for folks that are using their Unraid server as a subnet router or exit node. This allows the required sysctl values (per the Tailscale documentation) to survive reboots.

 

To access, go to the "Settings" page, then "Tailscale".

[rukiftw]

anyway to get access to br0 dockers?

with dsmith44's docker tailscale verison and docker host network access enabled, it can access br0 dockers. So far i have been unable to get this plugin to do the same. any ideas?

[EDACerton]

1 hour ago, rukiftw said:

anyway to get access to br0 dockers?

with dsmith44's docker tailscale verison and docker host network access enabled, it can access br0 dockers. So far i have been unable to get this plugin to do the same. any ideas?

Honestly, I'm not really certain how that worked in the first place

 

You could probably use the subnet router option to get a similar effect. The other option is to sidecar a Tailscale container to your other containers. This is possible with the existing Docker container, I'm also chatting with dsmith44 a little bit about how that could be made easier.

[EDACerton]

Update 2023.03.29 released: updates Tailscale to 1.38.3.