Comment on What us the best way to add remote access to my servers?

• neon_nova@lemmy.dbzer0.com ⁨1⁩ ⁨day⁩ ago

  When you connect to Tailscale, via cli it should give you a link to use to connect it to your account. You can get the ip address in various ways. One of which is just looking on your Tailscale dashboard. You need to have Tailscale installed on every machine you want to talk with.

  source
• MaggiWuerze@feddit.org ⁨1⁩ ⁨day⁩ ago

  Sure, you’re not behind CGNAT?

  source

  • ZeDoTelhado@lemmy.world ⁨1⁩ ⁨day⁩ ago

    I do not have Nat of any kind that I am aware

    source

    • rtxn@lemmy.world ⁨1⁩ ⁨day⁩ ago

      If you have IPv4 addresses, I guarantee you’re behind at least one NAT gateway. What you need is a Tailscale subnet router, or something equivalent from another service.

      In the most basic configuration, the Tailscale client facilitates communication between one host it is running on and another host it is running on that are both connected to the same tailnet. For this purpose, it uses addresses from the 100.64.0.0/10 “shared address space” subnet. These addresses will only be reachable from within your tailnet.

      If you want an entire subnet (e.g. your LAN) to be accessible within your tailnet, you need to set up a subnet router. This involves configuring the Tailscale client on a device within the target subnet to advertise routes (tailscale set --advertise-routes=192.168.1.0/24), allowing the host to advertise routes in the admin page (Machines -> … -> Edit routes), and configuring the Tailscale client on external hosts to accept advertised routes (tailscale set --accept-routes).

      If you want your servers to be accessible from anywhere on the internet, you’ll need Tailscale Funnel. I don’t use it personally, but it seems to work.

      source

      • ZeDoTelhado@lemmy.world ⁨1⁩ ⁨day⁩ ago

        Ah great, this sounds like what I was missing with tailscale. With try once I can, thanks!

        source