News for hackers. Stuff that matters.
Re:Duck DNS by ecliptik on Saturday August 05, 2023 @02:32PM (#37015027)
Fond memories of using DDNS on old Netgear routers at home in the aughts and port forwarding services with some rudimentary firewall rules and tcpwrappers to try and lock down access.

Now I use a combination of Tailscale[1] for private services only to me and Tailscale Funnels[2], and Cloudflare Tunnels[3] for public service exposure.

This accomplishes the same thing I was doing with DDNS and my ISP IP, but in a much more secure and stable manner.

1. https://tailscale.com/

2. https://tailscale.com/kb/1223/tailscale-funnel/

3. https://developers.cloudflare.com/cloudflare-one/connections...

Re:Duck DNS by pheeney on Saturday August 05, 2023 @04:18PM (#37015924)
Do you have any recommendations for tutorials on setting this all up with docker?

How do you connect outside the network?

I am running DDNS to access my home services and it has been very error prone and frustrating. I moved some services back to the cloud because the bots were using all my DSL upload that we didn’t have enough bandwidth to work even with cloudflare firewalls.

Re:Duck DNS by ecliptik on Saturday August 05, 2023 @05:40PM (#37016547)
I have an artisanal handcrafted docker-compose stack for them, so everything is containerized. It's on my todo to write a blog post about the setup.

There's an nginx reverse-proxy container in the stack that routes traffic to the individual service containers via the servername; eg nitter.tail.net goes to the nitter container, teddit.tail.net goes to the teddit container, etc.

The nginx proxy only listens on the Tailnet interface and only accepts connections from the Tailnet CIDR, therefore any device I have on my tailnet can access them. Letsencrypt is also setup so everything is over https.

This allows me to access them from my phone, laptop, whatever when connected using Tailscale.

Tailscale essentially let me completely remove any need for port forwarding on my router and still have global access. It's truly amazing.

Re:Duck DNS by chrisweekly on Saturday August 05, 2023 @05:48PM (#37016590)
+1 for the blog post howto idea
Re:Duck DNS by metadat on Saturday August 05, 2023 @06:15PM (#37016785)
If you wouldn't mind, any chance you can ping me once you publish this? You can reach me at collect.metadat attt gmail.
Re:Duck DNS by heybrendan on Saturday August 05, 2023 @06:39PM (#37016937)
+1 Would very much welcome you authoring something on this topic.
Re:Duck DNS by xav0989 on Saturday August 05, 2023 @08:04PM (#37017527)
I have a similar-ish setup, but using nomad as my executor, and traefik running on a public machine doing the routing.

Basically all the services on nomad listen on the tailnet, and traefik straddles the tailnet and the public internet. It then loads the service configurations from nomad and exposes them using let’s encrypt certificates.

Re:Duck DNS by hypercube33 on Saturday August 05, 2023 @11:04PM (#37018605)
+1 as well. right now I'm using route 53 and some funky scripts to pull ip from DNS and update it for site to site links
Re:Duck DNS by ecliptik on Sunday August 13, 2023 @03:33AM (#37107543)
While not a blog post, I created a Privacy Frontends with Tailscale repo on Github with this this setup using Tailscale MagicDNS and Caddy.

https://github.com/ecliptik/tailscale-privacy-frontends

I've tested it out on a new Tailnet on a t3.medium EC2 instance and it works relatively well. Adding new services should be relatively easy.

I'm planning to write up a post about the more technical details on the stack still.

Re:Duck DNS by trallnag on Saturday August 05, 2023 @05:06PM (#37016300)
Do you still secure your personal services with passwords?
Re:Duck DNS by ecliptik on Saturday August 05, 2023 @05:33PM (#37016510)
Not the internal services. I have Letsencrypt setup for services on my tailnet using the Cloudflare DNS plugin for certbot so they're all over https.

Combined with only allowing connections to hosts from the Tailnet and https, forgoing passwords makes them easier to manage and use.

Granted most these personal services are things like Audiobookshelf, Nitter, Plex, and Newsblur. While important to me, they're not exactly high value targets.

My internal Gitea is locked down more and has MFA enabled since I always see git as something to secure.

Re:Duck DNS by trillic on Saturday August 05, 2023 @05:08PM (#37016304)
Yes.
Re:Duck DNS by dan_wood on Saturday August 05, 2023 @05:09PM (#37016314)
Since you’re already using Cloudflare why did you choose tailscale over Cloudflares WARP?
Re:Duck DNS by ecliptik on Saturday August 05, 2023 @05:24PM (#37016435)
I don't use Tailscale Funnel as much, mostly on an adhoc basis since tailscale serve is relatively lightweight if a host is already connected to a Tailnet.

WARP is primarily used for long running services I have, like GotoSocial or Lemmy that need public ingress over https for federation.

Re:Duck DNS by FloatArtifact on Sunday August 06, 2023 @12:33AM (#37018998)
This doesn't work for game of hosting services does it? Http only?
Re:Duck DNS by rovr138 on Sunday August 06, 2023 @01:17PM (#37024280)
Tailscale does, https://tailscale.com/