Does anyone know of any alternatives to hoppy.network? I can’t seem to find any other services that do what Hoppy does. (Hoppy uses wireguard to assign publicly-accessible static IPv4 and IPv6 addresses to devices)

Host your own Wireguard endpoint on any cloud provider. They give you elastic IPs that you can create 1:1 NATs for your hosts. Maybe not quite as clean, but effectively the same thing.

@AbidanYre@lemmy.world
link
fedilink
English
26M

What’s your end goal? Some combination of ddns or cloud+headscale may accomplish what you’re looking for.

@solberg@lemmy.blahaj.zone
creator
link
fedilink
English
16M

I’m looking to maybe replace my VPS with something like Hoppy and a Raspberry Pi (I imagine the Pi 5 8GB might be stronger than anything I can get for $8/m). I have a static public IP anyway, but I’d rather not host websites and stuff using that.

@AbidanYre@lemmy.world
link
fedilink
English
2
edit-2
6M

If I’m understanding you correctly, I think the self hosted gateway thing linked here does what you want:

https://www.reddit.com/r/selfhosted/comments/y9tl6f/reverse_proxy_wireguard_tunnel_from_vps_to_home/

@solberg@lemmy.blahaj.zone
creator
link
fedilink
English
16M

Thanks. This solution looks like it might work, too.

@h3ndrik@feddit.de
link
fedilink
English
5
edit-2
6M

Hmm. It’s kind of just a VPN. It tunnels your traffic and terminates it at some server with those IPs. It’s just that NordVPN etc make you share an IP with other users and don’t offer port forwarding. But the rest of Hoppy isn’t necessarily unique, it’s just a specific configuration of a VPN.

I rented a VPS and installed wireguard myself. And created the firewall rules to forward (some) incoming traffic to my home server. That’s the same thing Hoppy does. Just that Hoppy does the setup of the firewall and Wireguard for you.

But I’m not aware of any similar services that do it automatically. Maybe something like pagekite.net comes close.

So I don’t know if that’s the correct solution to what you’re doing but I’d say one alternative would be to rent any small server, install Wireguard both there and on the RasPi, connect them and configure Wireguard on the RasPi so all outgoing traffic goes through the tunnel. And then configure the like 3 firewall rules on the VPS to make it forward incoming traffic on all ports to the RasPi.

@AbidanYre@lemmy.world
link
fedilink
English
26M

Based on your description, it kind of just sounds like tailscale.

@solberg@lemmy.blahaj.zone
creator
link
fedilink
English
26M

Thank you.

And created the firewall rules to forward (some) incoming traffic to my home server.

I guess this is the missing piece for me. I’ve already got all of my devices and VPSes setup with Tailscale, I’m just not sure which software to use that can do this forwarding.

I know Tailscale Funnels, Cloudflare Tunnels, and Caddy could be solutions for some, but in my experience they only do TCP or restrict what sort of traffic can be forwarded.

@h3ndrik@feddit.de
link
fedilink
English
26M

iptables or nftables. Or firewalld depending on the Linux distro and version you use.

Sometimes the Arch Wiki has some good info on specific configurations. I mean it’s not that easy to write firewall rules on the command line. But it’s no rocket science either.

Possibly linux
link
fedilink
English
26M

DIY it

@Decronym@lemmy.decronym.xyz
bot account
link
fedilink
English
2
edit-2
6M

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
IP Internet Protocol
NAT Network Address Translation
TCP Transmission Control Protocol, most often over IP
VPN Virtual Private Network
VPS Virtual Private Server (opposed to shared hosting)

5 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.

[Thread #715 for this sub, first seen 26th Apr 2024, 22:25] [FAQ] [Full list] [Contact] [Source code]

Create a post

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!

  • 1 user online
  • 126 users / day
  • 421 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog