I’ll be honest, less ugly than NAT which is really where I draw the line (I hate NAT), especially if they’re charging you per /64, that’s borderline diabolical from a hosting provider. If I was getting charged per /64 I’d probably route /96s too. Lack of SLAAC is unfortunate though.

No, you still need a gateway, maybe what you’re referring to is the lack of NAT? But that honestly makes it less confusing, there’s still a default gateway though. It’s funny you say the subnetting thing because for me it’s the opposite. In v4 subnets are variable sized, sure /24 is the most common but I’ve found everything from /8 all the way to /29 in the wild. In v6…every subnet in a sane network is a /64, it’s practically enforced by the standard. You basically can’t go smaller and going bigger is pointless. That means the first 4 hex groups are your subnet, the last 4 are the device, basically always. Now VPNs are one of the few environments where /64 isn’t super heavily enforced and you can go smaller but it’s still good practice to use it anyway. Memorizing addresses is…you’re not wrong, but also I personally don’t find it that bad and here’s why. The first half of the address isn’t THAT much longer than a v4 address. It is a bit, and yes it’s hex so letters. Thing is, the first half is the bit you can’t control, kinda equivalent to your public v4, so once you memorize that, the second half can be whatever you want and as short as you want. Worst case you can always use DNS to avoid memorizing addresses but that does require extra configuration.

I’m not sure what you mean by that? What problems specifically?

🤔, I’m not sure what would cause it to break other than a misconfiguration, my setup isn’t stock though, my most recent endeavor was migrating to a VTless system, so I do a lot of “different” and non-conventional things. Sure I’ve had configs break but it’s because I made a mistake, that’s not the init’s fault.

Yeah, right now in order to do it without giving up a bunch of services you have to combine it with NAT64+DNS64. NAT64 maps the entire IPv4 space to a /96 of your chosing and then DNS64 will generate AAAA records based on that /96 when upstream doesn’t provide one so clients can talk pure v6 even to v4 only sites. There are some services (steam client and discord voice calls) that require v4 addressing and won’t work with this setup, but it gets you 98% of the way there.

I don’t use either 🤔

Having run both systemd and sysv, they both never really break in my experience unless it’s self inflicted. I don’t think I’ve ever just had one break randomly, the systemd recovery environment is much better when there is a breakage, and I’m not sure the boot times are really any different in my setup. Maybe if I tried something a little more parallel than sysv they’d be faster but eh.