tailscale / tailscale-qpkg

Package Tailscale client in QPKG
MIT License
457 stars 38 forks source link

use tailscale command options #58

Open Deivonex opened 1 year ago

Deivonex commented 1 year ago

first thank you for the possibility to have this software on qnap!!!! there is the possibility to use the tailscale command options... for example, sudo tailscale up --advertise-exit-node? thanks

DentonGentry commented 1 year ago

I would expect --advertise-exit-node to work. Did you try it, and it did not?

Deivonex commented 1 year ago

[/share/CACHEDEV1_DATA/.qpkg/Tailscale] # sudo ./tailscale down error fetching current status: Failed to connect to local Tailscale daemon for /localapi/v0/status; not running? Error: dial unix /var/run/tailscale/tailscaled.sock: connect: no such file or directory <g/Tailscale] # sudo ./tailscale up --accept-routes --advertise-exit-node
failed to connect to local tailscaled (which appears to be running as tailscaled, pid 10955). Got error: Failed to connect to local Tailscale daemon for /localapi/v0/status; not running? Error: dial unix /var/run/tailscale/tailscaled.sock: connect: no such file or directory

DentonGentry commented 1 year ago

Could you use: ps auxw | grep tailscaled and look for a --socket argument? Depending on the version you are running it might be at several different paths.

Then you'd invoke the tailscale command with the same argument, for example: sudo ./tailscale --socket=/tmp/tailscale.sock up --accept-routes --advertise-exit-node

Deivonex commented 1 year ago

ohhhh great!!!! works fine!!!!! thanks !!!!

johntait commented 1 year ago

First, thank you very much for making installing tailscale under QTS possible.

I've been following the problems installing your tailscale package under QTS 5.0.1.xxx and received email saying it is no longer a problem (issue #46). I've been using QNap Club's package since it didn't have the same problems, but they are very slow to update (still on tailscale 1.30.2). I uninstalled the QNap Club package then installed your package manually. The installation went smoothly but when I tried to run ./tailscale up I received the same error message Deivonex reported. After reading your responses I knew I had to add the path to the socket and following your instructions now know how to run tailscale cli commands with your package installed.

I'm writing this because nobody would know how to fix the problem without reading issue 58. In fact, based on what's included in README.md, I would think I was done after installing the package and wouldn't know I need to ssh into a terminal session to at least run tailscale up (including the path to the socket) then connect and authenticate using the returned URL. Would it be possible to include instructions in README.md that point to tailscale.com's "Start Using Tailscale" documentation then add that for a QNap NAS it's necessary to ssh into a terminal session along with the commands that need to be run?

Edit: After successfully using the information you provided I found a set of instructions on Reddit and used them successfully by uninstalling your package then re-installing it. The package install and running the necessary cli commands went without a hitch. Perhaps you could point to these instructions on Reddit in README.md

https://www.reddit.com/r/Tailscale/comments/p1lawn/qnap_how_to_set_up_a_static_route_and_set_your/

Thanks for listening!

DentonGentry commented 1 year ago

The main branch of development in this repo is aimed to get into the App Center, where there is a UI to log in and not SSH.

I understand this is awkward while we're in the period between when the development has been done but it hasn't appeared in the App Center yet. I have to ask your patience until it does.

johntait commented 1 year ago

Thanks for your quick reply! I've figured out what I need to do so it isn't a problem for me. I've been concerned about people attempting to install tailscale for the first time not knowing what to do or how to find out. Having tailscale in QNap's app center with a GUI interface to log in is clearly the best long term solution. Good luck and thanks again.