16
how do you use tailscale/zerotier?
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jul 2023
16 points (90.0% liked)
Selfhosted
39677 readers
434 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
You can partially use Tailscale but yes, to use it you need to install it in all your devices.
At first I had it installed and just had a few use cases (mainly PiHole with MagicDNS which requires installing it in all your machines). But I still connected to ssh with the ip of the machine.
After I finished that initial set up then I closed all the ports and only allowed ssh from the tailnet.
I think you can get away with installing it just in your reverse proxy and in the machine you want to point to if you have solved the issue of the DNS.
One thing to have in mind with this approach is that you won't benefit from the routing of wireguard, since all your traffic needs to pass through the reverse proxy, a better approach would be to have each service with its own tailnet ip.
The only issue I've found is if you have a container in a machine with tailscale, the container doesn't know about the tailnet unless you have host network type or some other way to share a network which actually knows about tailscale.