• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: August 16th, 2023

help-circle


  • I think openvpn works completely fine for most use cases and didn’t have any trouble with it at all. I did however switch to wireguard on my gateway and I get a little better throughput compared to openvpn. That being said, I’m also using a pfsense box as my home gateway, so access to internal services has been easy as general routing gets.






  • I like proxmox, but it kinda sounds like you’d be just fine with just docker running on opensuse or debian. Or whichever the favorite container is these days (idk why podman is so great, but I seent some posts about people that love it.)

    I have tiered out my server with all my app services (jellyfin, nextcloud, etc) running in docker on a debian vm, then have lxc containers for nfs, VPN, etc. Proxmox itself handles ZFS, but I’m sure that’s bad practice and there is probably a better way - but it works for me so 🤷.

    I’ve also got a opnsense vm, but not used for any “production” atm; just checking it out to see if I should switch my pfsense box over.






  • You right. There are still IP addresses; you can’t really just yank out layer3 and call it a day.

    Here is a piece from their website about the “Secure envelopes”:

    “Each node hop only knows about the next one This is similar to onion routing, but assumes that the source is fully in control of the Safety Route and the destination is fully in control of the Private Route.”

    There’s also a packet diagram. It’s just encapsulation inception. There are also IP addresses listed as being encapsulated in the packets for additional node hops.

    I guess from the perspective of the source and destination, they don’t know each other’s IPs. So there is that v0v.