3 ms·

Upgrading to 64-bit address space would also require a rip and replace of all carrier routers, customer CPEs, and re-writing of software. We might as well take

Upgrading to 64-bit address space would also require a rip and replace of all carrier routers, customer CPEs, and re-writing of software. We might as well take advantage of a compatibility breaking upgrade to fit in all of the other upgrades.

bronson 8y ago
> We might as well take advantage of a compatibility breaking upgrade to fit in all of the other upgrades. These are the shoals that so many projects have foundered upon.
deleted 8y ago
[deleted]
theamk 8y ago
... and that's how you end up with current situation Replacing inaddr_t with inaddr6_t is trivial, and does not require any significant effort at all. Replacing everything else is hard. My house is on IPv4 and will be on IPv4 for foreseeable future, because all of my setup (filtering, metering, monitoring, fixed IP assignment) is completely unusable in the new IPv6 world with privacy extensions where addresses are not only random, but change constantly.
- slrz 8y ago
  You do know of RFC 7217 address assignment resulting in stable addresses as long as you don't move into another network? It's even the default on some Linux distributions. If you want predicatable addressing, you can always forego privacy extensions and use EUI64-style interface identifiers.
  - theamk 8y ago
    Yes, I know about RFC 7217. But I also know that default network setup in recent Linuxes, Android and iOS all uses privacy extensions. And even if they can be disabled, I want to keep them -- they are there for a reason, I don't want to give every single internet website a permanent, unique identifier. This is not an insolvable problem. I can write another daemon to keep the history of IP<->Mac associations, change my accounting scripts to look the matching MAC, change the firewall to filter based on mac address, and so on -- but it is a lot of work, and no benefits. The NAT is not a problem at my home network, generic openwrt router has enough CPU power for my bandwidth. Direct addressing for each device is useless, as I would still have to list every port and every device I want to expose -- even if NAT goes away, the firewall with default-deny incoming policy stays. This, IMHO, is the biggest problem with IPv6 adoption. If this was only "recompile the problem and change IP address regex", then we would be done ages ago. Instead, it just got strictly worse for most small network owners.

bronson 8y ago

> We might as well take advantage of a compatibility breaking upgrade to fit in all of the other upgrades. These are the shoals that so many projects have foundered upon.

deleted 8y ago

[deleted]

theamk 8y ago

... and that's how you end up with current situation Replacing inaddr_t with inaddr6_t is trivial, and does not require any significant effort at all. Replacing everything else is hard. My house is on IPv4 and will be on IPv4 for foreseeable future, because all of my setup (filtering, metering, monitoring, fixed IP assignment) is completely unusable in the new IPv6 world with privacy extensions where addresses are not only random, but change constantly.

slrz 8y ago
You do know of RFC 7217 address assignment resulting in stable addresses as long as you don't move into another network? It's even the default on some Linux distributions. If you want predicatable addressing, you can always forego privacy extensions and use EUI64-style interface identifiers.
- theamk 8y ago
  Yes, I know about RFC 7217. But I also know that default network setup in recent Linuxes, Android and iOS all uses privacy extensions. And even if they can be disabled, I want to keep them -- they are there for a reason, I don't want to give every single internet website a permanent, unique identifier. This is not an insolvable problem. I can write another daemon to keep the history of IP<->Mac associations, change my accounting scripts to look the matching MAC, change the firewall to filter based on mac address, and so on -- but it is a lot of work, and no benefits. The NAT is not a problem at my home network, generic openwrt router has enough CPU power for my bandwidth. Direct addressing for each device is useless, as I would still have to list every port and every device I want to expose -- even if NAT goes away, the firewall with default-deny incoming policy stays. This, IMHO, is the biggest problem with IPv6 adoption. If this was only "recompile the problem and change IP address regex", then we would be done ages ago. Instead, it just got strictly worse for most small network owners.