@espen I don't mind a /64 subnet. It's more than I'll use in tens of lifetimes.
But coming in "comiserating and offering a solution" to a problem they're causing themselves is a very dick move.
Top-level
@espen I don't mind a /64 subnet. It's more than I'll use in tens of lifetimes. But coming in "comiserating and offering a solution" to a problem they're causing themselves is a very dick move. 4 comments
@espen And, IPv6 is still dependent on centralized infrastructure. I think we need Yggdrasil-style addressing, where addresses are generated independently. @espen @drq True, the space is so vast we might need spice to navigate it. But one of the key points is the hierarchical nature. Routers just look at the address prefix and forwards the packet to the connection with the largest matching prefix, so instead of the crisscrossing mess that is ipv4, you get a nice simple tree structure. |
@drq Yeah, its a lot of addresses. But it's not about the amount of addresses but the routing of them thats also an issue. To make things work for me I had to split it into two /65 nets, which works but also means that all the nice automatic features like SLAAC are broken because the required address-space to make these features work is now too small.
I don't have a particular complicated home network but I required 3 subnets to get everything to play well together. 😀