Context:

Over the past few months, Xfinity has just been causing me so many problems with self-hosting. Not having a static ip isn’t actually that much of a problem for me, I was able to set up a little docker container that automatically changes my dns records when my ip changes. However, pretty frequently, they’ll reset my router/gateway’s firewall configuration, which blocks basically all ipv6 traffic by default, and the other day, they even removed my port forwards while I was away, and hid my server from the port forwarding screen so I couldn’t add them back until I got physical access to the server.

So, I’ve come to the realization that I should probably set up a VPS, since that should solve basically all of my issues. All I want is something that can forward/proxy gigabit traffic to my server, probably over something like wireguard.

To be clear, I still want all of my services to run on my server, I just want the VPS to route the traffic.

And, said VPS preferably has ipv6 in addition to ipv4 access, and gigabit download, though none of those are strict requirements.

Questions:

Are there any issues or limits with this setup that I’m not considering?

Is there a better solution?

Assuming the previous Q’s are fine:

What’s a good VPS provider for this?

What software should I use to actually do the forwarding/proxying?

  • hendrik@palaver.p3x.deEnglish
    4·
    12 hours ago

    I think a few people already mentioned some good solutions. I just wanted to add: A port forwarding in the firewall of your router is the basically the same thing as a port forwarding on your Linux computer’s firewall. You could just set up any VPN, SSH tunnel or whatever and then use your firewall (nftables, iptables) and forward the VPS’ extetnal port to the internal port on the VPN. It’s the same thing you do on your router, just that you don’t get a graphical interface to configure it.

      • hendrik@palaver.p3x.deEnglish
        1·
        1 hour ago

        I’d let the home server connect to the VPN on the VPS so there’s a direct tunnel between the VPS and the home server. And the router is pretty much irrelevant. You can of course choose to terminate it on the router as well, bus as you said, that requires either a second forwarding. Or the entire home network to be bridged or routed.