Noob Tailscale questions

Submitted ⁨⁨4⁩ ⁨days⁩ ago⁩ by ⁨the_riviera_kid@lemmy.world⁩ to ⁨selfhosted@lemmy.world⁩

I’m having a hard time with tail scale, I have it setup on my windows computer and on my android phone. I want to be able to connect to the hotspot on my phone and access local resources on my computer. I have tried googling it and I just get a 1000 conflicting statements none of which are of any help. So far it works fine from my phone to my PC with no issues but when I connect a device to the phone it can’t see anything on the local network through that device. The connected device is in question and yes I attempted to install tail scale on the deck which also failed miserably. followed this video and at Sudo bash tailscale.sh I get no such file or directory but I can see the files in file manager. if I attempt to run it from the folder I get could not find /home/deck/documents/github/deck-tailscale.sh.

I’m so lost, can anyone point me in a direction? the ultimate goal here is to use jellyfin out side on my network on my steam deck and every install guide out there fails. I don’t see it in the discovery store and the official git hub desktop app cannot even see the files it just downloaded.

source

Comments

Sort:hotnew top

rtxn@lemmy.world ⁨4⁩ ⁨days⁩ ago
The problem is that your phone’s hotspot network doesn’t advertise routes through the Tailscale tunnel. I don’t know how/if it can be done.

Try this guide on the deck: github.com/tailscale-dev/deck-tailscale

source
- the_riviera_kid@lemmy.world ⁨4⁩ ⁨days⁩ ago
  That does not work, thats why I came here to ask. It fails at step 2.
  
  source
  - rtxn@lemmy.world ⁨4⁩ ⁨days⁩ ago
    Program no worky will not be enough if you want help. What is the exact output when you try to run tailscale.sh?
    
    source
    -> View More Comments
MangoPenguin@lemmy.blahaj.zone ⁨4⁩ ⁨days⁩ ago
The phones hotspot will bypass the VPN, so you’ll need to run it directly on the device.

source
gedaliyah@lemmy.world ⁨4⁩ ⁨days⁩ ago
Tailscale client definitely needs to be installed and logged in on the destination device (Steam Deck in this case). Is it possible that you are typing “Sudo” instead of “sudo” in the command after opening Konsole? Linux commands are case-sensitive.

I’m not knowledgeable about the steam deck, but it is also possible that sudo is not installed by default, in which case you will have to install it. sudo is a command that allows you to run other commands as root (basically admin).

I found this article that might help: pimylifeup.com/steam-deck-sudo-password/

source
- gedaliyah@lemmy.world ⁨4⁩ ⁨days⁩ ago
  Actually, watching the video it looks like they first enter:
  
  cd Documents/deck-tailscale/
  
  then enter:
  
  sudo bash tailscale.sh
  
  If you don’t have the directory Documents/deck-tailscale/, then you will have to go back a step and find out where GitHub Desktop is storing the local files.
  
  source
  - the_riviera_kid@lemmy.world ⁨4⁩ ⁨days⁩ ago
    I ran it from the local folder, literaly clicked on tailscale.sh and clicked run in konsole. still says it doesn’t exist when I’m fucking looking at it.
    
    source
    -> View More Comments
- the_riviera_kid@lemmy.world ⁨4⁩ ⁨days⁩ ago
  You have to setup a sudo password originally to install things in desktop mode but that has been done, sudo is not the issue. literally copy and pasted from this article. It fails on step 2 claiming the directory does not exist.
  
  source
  - gedaliyah@lemmy.world ⁨4⁩ ⁨days⁩ ago
    use ls command, as in the video, to list the contents of a directory, then use cd to change directory based on what you see. You can use cd … to navigate to the parent directory of your current location if needed.
    
    Also make note of the Local path shown when cloning the repository in the previous step to help find it. When you see “tailscale.sh” as one of the items after typing ls, then you will know you are in the right place.
    
    source
billwashere@lemmy.world ⁨4⁩ ⁨days⁩ ago
Best thing I ever did with Tailscale was install pfsense and then Tailscale on that. I use it at work that way. I have three separate data centers (with three pfsense VMs) with advertised routes for the three separate subnets. When I install the client on one machine, I can access all three networks automatically. I did the same thing at home so I can also access that easily as well.

I think what you’re ultimately looking for is the exit node capability. Not sure if the phone can act as an exit node but pfsense definitely can. I have a VPS hosted in NY that I use to get around certain geographical restrictions. I set it as my exit node and it looks like I’m coming from there. The desktop clients can as well.

Here’s what I’d do if I were you. Install Tailscale on a machine in your house. Set it up to advertise routes based on whatever IPs you’re using in your home. In my case it’s 10.0.0.0/24. Now any device you install Tailscale on will be able to connect to that network. Another thing you can do is any machine that is connected to your Tailscale will have a 100.x.x.x address that you can connect to directly.

Hope this helps.

source
TacoEvent@lemmy.zip ⁨4⁩ ⁨days⁩ ago
Your phone’s hotspot likely doesn’t create a local network. The other problem is that Tailscale works by creating a secure tunnel between your client and your PC. Local devices won’t have access to this secure tunnel. You need to setup Tailscale directly on the client device you want to connect to your PC from for it to work.

source
- the_riviera_kid@lemmy.world ⁨4⁩ ⁨days⁩ ago
  Again I have tried to set it up directly, it fails every time. Tail scale has subnet routing for this very purpose, I just can’t figure out what I am doing wrong on either one.
  
  source
  - cecilkorik@lemmy.ca ⁨4⁩ ⁨days⁩ ago
    Subnet routing is generally far more complex than simply installing the client. If you aren’t succeeding at one you’re likely not going to succeed at the other.
    
    I don’t know the exact problem based on what you’ve described and I’m not going to promise I can solve it for you but I’m going to try to give you some tools you can use to help yourself a little and hopefully be able to better understand what is going wrong and that will help you understand what you can do about it. Don’t get frustrated by this issue, this is a learning experience and this is a skill you need to invest in and develop so that you’re not just blindly copy-pasting instructions from videos (which is a bad place to be)
    
    Step 1: Figure out where your tailscale.sh actually is.
    
    Once inconsistency I noticed in your description of what’s going on is that you’re attempting to run tailscale.sh but you’re describing a path of /home/deck/documents/github/deck-tailscale.sh not sure if this is just a typo or what but that describes a file called deck-tailscale.sh which is not the same thing as tailscale.sh.
    
    I think the repository you’ve downloaded based on those instructions is called deck-tailscale however a repository is a folder full of files, and tailscale.sh is ONE of those files. That repository’s name would probably be /home/deck/documents/github/deck-tailscale/ so if you’re looking for tailscale.sh inside that repository it will be /home/deck/documents/github/deck-tailscale/tailscale.sh. (two tailscales in the full path, one for the repo and one for the file itself)
    
    You can verify all of these paths by using the ls <path> command, ls (that’s L and S, not IS) means “list” and is similar the dir command in Windows, it will show if the file you specify exists, or if it is a directory it will list all the contents of that directory. ls is a useful command to explore the directories and see which ones exist and which ones don’t. You can work your way up the path to see where things are going wrong, for example, if ls /home/deck/documents/github/deck-tailscale/ does not exist, try ls /home/deck/documents/github/ and if that doesn’t work try ls /home/deck/documents/ and so on
    
    Second note: I notice your documents path is /home/deck/documents I don’t have a steam deck in front of me to check, but my Linux system has a documents folder called /home/<me>/Documents with a capital D. Paths on Linux are always case-sensitive. That means /documents is not the same thing as /Documents, which is not the same as /DOCUMENTS/ and if you attempt to use one when it’s actually the other, the file will not be found. Make sure the capitalization is correct in the whole path.
    
    Step 2: Once you’ve located the correct path name of tailscale.sh you should be able to run it with: sudo <full-path-to-tailscale.sh>
    
    Good luck.
    
    source
    -> View More Comments