SensibleSalmon

Setting "Enable NetBIOS" to "No" also fixed my issue, coming from a Linux client to an Unraid 6.12.3 server over the Tailscale plugin.

On the internal network, I think Tailscale will always assign both an ipv4 and ipv6 address. I haven't found a configuration option to only issue one or the other yet, anyway. You can request a specific one for a given host via the command line though: https://tailscale.com/kb/1080/cli/#ip Note also ip allocations are static per device enrollment, so they'll be stable so long as you don't remove and re-add the device to your network.

That isn't how Tailscale specifically works. Tailscale is designed as a point-to-point overlay network VPN. To access shares on Unraid via Tailscale, you have to use the IP address Unraid has on the Tailscale network. There's a couple ways to find that IP: first is in the Tailscale settings page on Unraid, it'll show you the IP address there, like this: Or, in a console on any other machine connected to the tailnet, you can ask Tailscale what IPs it knows about with `tailscale status`: Then on the machine you want to connect to the share from (e.g., laptop), you'd point it at the tailscale address of (in my case) fd7a:115c:a1e0::8 You may have ipv4 addresses--Tailscale uses both ipv6 and ipv4 interchangeably.

For anyone else trying to figure out how to set up Tailscale using this plugin: turns out, you can just invoke "tailscale up" from the command line directly and pass all the usual arguments. Thanks @EDACerton for pointing that out to me!

Reaching out now!

Is there any way to pass a login_server param to the underlying tailscale daemon? I'm trying to link my unraid host to my headscale instance. (Docs here). I didn't see anything in the plugin settings.