It not evident if you are an admin of localhost, but working with hundreds devices make you really appreciate it.
This is the whole config what allows the device to talk to IPv6 and provide IPv6 addresses to the clients in the vlan3003. No DHCP, no ip helpers, nothing.
> in case anyone is wondering why IPv6 is where it’s at after a decade
But.. I'm tired to juggle this nonsense. We have /21, a couple of /24 and a bunch of /28. I recently decided to move out our services from /21 and /24 to some specific /28 and despite what all those /28 are pretty close (most of them sits in one /23) I can't have a few laconic network rules with aggregates for separating our own and customers traffic. I would need to have a whole let of rules, almost for each /28.
I enjoy how RA handles address assignment. I like how the address space feels huge and uncrowded (almost private), like how internet v1 once did. I like it when the lightbulbs go off the first time I get a service working.
At a previous company I worked at, this was literally the impetus for going IPv6. We were in a regional business and were growing by acquiring companies in other regions. Every new company we acquired, we had the major pain of making the networks talk. Almost everyone is using 192.168.0.0/16 or 10.0.0.0/8. IP conflicts were a given, and re-address networks was a big painful operation. NATs were an option, but came with their own permanent complications. IPv6 made it go away. If the new site already had IPv6, collisions were still a non-issue, and if they didn't, well getting them IPv6 ready was easier than re-address everything. Once they were IPv6 ready we could go ahead and establish VPNs, and with most traffic now going over IPv6 we could re-address IPv4 without causing significant outages.
IPv6 has other advantages, better multicast, better routing, flow labeling, automatic link-local addressing, but the large IP space is definitely the elephant in the room.
It not evident if you are an admin of localhost, but working with hundreds devices make you really appreciate it.
This is the whole config what allows the device to talk to IPv6 and provide IPv6 addresses to the clients in the vlan3003. No DHCP, no ip helpers, nothing.
> in case anyone is wondering why IPv6 is where it’s at after a decadeBut.. I'm tired to juggle this nonsense. We have /21, a couple of /24 and a bunch of /28. I recently decided to move out our services from /21 and /24 to some specific /28 and despite what all those /28 are pretty close (most of them sits in one /23) I can't have a few laconic network rules with aggregates for separating our own and customers traffic. I would need to have a whole let of rules, almost for each /28.