so when i dislike changes in software i’m “weird” and i should “get on with the times”, but when you don’t wanna do IPv6 because it’s new and scary (TO YOU) it’s suddenly okay?

come on…

ipv6 isn’t without flaws. but have you SEEN the general software landscape? the things that we put up with on a daily basis?

if we waited with software to be “perfect” as much as we seemingly do with networks, computers would still only be strictly experimental mainframes

(i’m still convinced that most of this is due to insufficient education on the subject, hoping to - within my lifetime - write at least one book about the general subject that would be a little bit more approachable than the current SEO-enshittified status-quo)

@domi It's *checks watch* 2026 and my ISP doesn't support IPv6 to residents, like not even a /64 (a reminder that a /48 is appropriate for a residence, I would get a /32 if I had a big network).

They assigned /127s last time I turned off bridge mode.

@makdaam @domi

Are you sure? Is this some locality thing?

Most people (here) get /56 (gives them 256 subnets), companies and stuff may get a /48 (65535), and the ISPs themselves have /32s (4 billion).

Having a /48 and especially a /32 for yourself seems excessively overkill.

@lucasmz @domi https://www.ripe.net/publications/docs/ripe-690/

/56 is the minimum, but let's be honest I'm a bit of an outlier with 12 "top level" internal subnets at home (not counting VPNs) and then even more networks inside my lab. It would be possible to fit in 256 subnets with everything but I'd prefer to just assign new /64 per test deployment without reusing them.

Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose

ripe-690: Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose

RIPE Network Coordination Center