9
Need help understanding how to get around port-forwarding with tailscale
(programming.dev)
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 02 Feb 2024
9 points (84.6% liked)
Selfhosted
39677 readers
386 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
Tailscale requires each person be granted access, I.e. it's private. (Edit:I didn't know about Tailscale Funnel, which is more like Cloudflare tunnel)
Cloudflare Tunnel gives anyone on the internet access, but to my knowledge only covers HTTP traffic. If what you're trying to do requires port numbers then I don't think that will work.
In regards to media traffic, Cloudflare silently removed that section of their Ts & Cs, so hosting Jellyfin, etc should now be OK.
You might be able to use Tailscale on a cheap VPN to forward traffic to your setup, but it might be cheaper and easier to pay your ISP.
It's worth pointing out that port forwarding happens on your router, but if you don't have a public IP then it won't work. Sometimes ISPs will give you a public IP if you just ask, sometimes they tie it to a static IP add-on and charge for it. It sounds like you might be in the latter case. It can vary by ISP, so if you live somewhere where you get a choice, you may find another ISP is a better deal (e.g. where I live some charge $15 a month for a static IP, some charge a one off $40 fee, and some you can just ask and they will give you a public dynamic IP for free. Others will give everyone public dynamic IPs).
My ISP says my IP is technically dynamic, but it hasn't changed once in the 6 years I've had their service. But that's for the best, since they're the only choice for symmetrical gigabit and their only option for static IPs is for business accounts.
So I continue to trust that they won't change it. Fingers crossed.
Dynamic IPs don't change very often. Sometimes you can get a new one by restarting your router, which most people don't do very often. But in my experience they stay the same if you don't restart it.
If you do end up with a new IP occasionally, it's typically not too hard to change things to the new one.
You can also just spend $10 on a domain name with a registrar that offers dynamic DNS. Offhand, both Namecheap and Cloudflare do. I have no idea what my public IP address is because my router just updates it automatically for me. Plenty of DDNS desktop clients around if your router can't for whatever reason.
Haven't seen mine change in 5 years, lol. Even with modem reboots!
Does your ISP sell static IPs? Maybe they are all static?
For an ISP using all public IPs, in the days of dial up they could rent less IPs than customers because people were online at different times. These days the routers are all online 24/7, so it seems odd to me that some ISPs have everyone on public IPs but they aren't static. Probably some technical reason why things don't work how I think they do, but it just feels like a way to sell static IPs as an add-on when it wouldn't cost them anymore to allocate an IP to a customer for the life of the connection.