On: Android’s IPv6 Is Still Broken

[joecool1029]

Since running wireguard with algo.sh seems to be popular now, this is the situation you'll end up in with most ipv6 supporting cloud hosting providers. Digital Ocean only gives 16 ipv6 addresses to the best of my knowledge, others are probably limited to only 1.

[amaccuish → joecool1029]

I moved from OWH because they only assigned a /128 to VPSes, so you're sharing a /64 with other servers. That was problematic because I run my own email server, and blacklists for IPv6 tend to be specific to a /64, meaning neighbouring servers landed my own server on blacklists (i.e. they blanket blacklist the whole /64). And obvs cloud providers sadly host a lot of spammers.

In the end, since OVH even after being asked for years offer no option for /64s on VPSes, I moved to Hetzner, where a VPS gets it's own /64, so only I am responsible for my mail server's reputation.

[Avamander → amaccuish]

I just recently had the same issue, I really don't understand why the fsck they're doing that s*. Don't they have billions of IPv6 addresses?

[ninjaguardsheep → joecool1029]

I moved from Digital Ocean to Hetzner for my personal VPSes recently.

One of the reasons was that Hetzner assigns ipv6 addresses in /64 blocks.

Rent an ipv6 enabled vps: get a /64.

Rent an additional "floating ip": get a /64.

[qalmakka → joecool1029]

yeah, I also give out ULAs to my clients in VPNs (both OpenVPN and WireGuard), but it's mostly for local, in LAN traffic. I still haven't figured out how to convince Windows to actually prefer ULAs to IPv4 like I can do on Linux.