this post was submitted on 09 Apr 2024
16 points (86.4% liked)

Selfhosted

40329 readers
419 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
16
UDP Tunneling solution recommendations (lemmy.ml)
submitted 7 months ago by umami_wasbi@lemmy.ml to c/selfhosted@lemmy.world
20 comments fedilink hide all child comments
 

I want to host a small game server for friends and myself in my home but doesn't want to open up the firewall. Any tunneling solutions supports UDP? Thnaks.

you are viewing a single comment's thread
view the rest of the comments
[–] rtxn@lemmy.world 6 points 7 months ago* (last edited 7 months ago) (1 children)

At some point, you have to compromise.

  • You can open the port(s) used by the game on the firewall (assuming you have a publicly routable IP).
  • You can run OpenVPN or a proprietary solution, but you'll have to open a port on the firewall, and I know from experience that they're a bitch and a half to configure.
  • You can run Wireguard, but you'll have to open a port on your firewall and have the other clients generate and send you their public keys.
  • You can run Tailscale (my preferred solution), which uses Wireguard and works without opening the firewall and without a publicly routable IP (e.g. behind CGNAT), but you'll have to install the client, have the users sign in, and then add them to your tailnet, which IMO is much easier than setting up Wireguard peers manually.
  • You can use Tailscale Funnel, which exposes your tailnet to the public internet, but it's in beta, has high latency, and only supports TCP, so you'll have to figure out how to smash UDP datagrams through a TCP tunnel.
  • You can try Ngrok (my backup in case Tailscale can't connect), which is a similar NAT traversal solution, but it only supports TCP and gives you a different IP and port every time you create a tunnel.
  • Twingate also exists, I guess, but I've only ever used it for SSH.
[–] lemmyvore@feddit.nl 1 points 7 months ago

Tailscale [...] install the client, have the users sign in, and then add them to your tailnet

You can just have them pass you the device enrollment links and add their devices to your tailnet. That way nobody else has to make an account.