• 1 Post
  • 77 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle
  • Love that you put it in quotes as if to be sarcastic. Hilarious.

    This is basically how the entire Internet works, but you know that from your post. Surely you also know that traffic gets “routed” from place A to B all the time without SSH as well.

    So if you want to “route” a remote instance back to another place, you:

    1. Set routing rules on the intended origin
    2. Set default route on the remote client
    3. Set restricted firewall rules so both the origin and client are allowed to talk to each other
    4. Traffic is routed

    Another alternative is using Tailscale and setting an exit node on your network, which is essentially the same thing.

    But you already knew that, and that’s why you chimed in with your comment. Stupid me.

    How fucking stupid must I look, huh?





  • Don’t mix your public and private DNS records. Use your public records for public things, and a local DNS forwarder for your local network.

    A records only reference IPs and not ports.

    SRV can be used to specify where to find ports, but the client needs to support those lookups to properly use it. You can use a reverse proxy or HTTP redirects to point things to different ports.



  • It’s not that there’s anything inherently wrong with this, but it’s not the most in line with your goals. If you’re worried about data loss, you could have made a volume that spans both drives like RAID1/Z1, or you could have setup some clever data spanning with BTRFS or likewise. Then you’d be killing two birds with one stone for the Timeshift portion.

    If you want safe backups, you need a separate backup drive at a bare minimum.