3 ms·

I dipped my toes into IPv6 a while back and found it pretty... disappointing? My prior understanding was that IPv6 would enable us all to get static IPs (due to

by zppln 4y ago

I dipped my toes into IPv6 a while back and found it pretty... disappointing? My prior understanding was that IPv6 would enable us all to get static IPs (due to there being more than enough for everyone), but it seems that turned out to be a bad idea for privacy reasons. So my IPv6 block kept changing. Then it was a mess locally as well, where addresses kept changing and having Android units forcing you to use SLAAC because they refuse to support DHCPv6. I don't remember all the details but my take in the end was basically IPv6 not being worth the hassle.

puffoflogic 4y ago
Based on your description it appears you attempted to deploy "ipv4 with longer addresses" and got frustrated that this is not at all what ipv6 is. If you were to attempt honestly to deploy the actual ipv6 stack that exists, though not perfect, it would be a better experience.
- iforgotpassword 4y ago
  > Based on your description it appears you attempted to deploy "ipv4 with longer addresses" Because I honestly think this is what we (99.9999% of people) really need. IPv6 is second system syndrome. Things can fail in a thousand different ways and it's a pita to debug. Look no further than the "easy it sucks" top comment. I've had so many random bullshit problems in both, Enterprise environments and with home setups. Buggy SLAAC, buggy DHCPv6, buggy PD, just hot garbage everywhere. Prefix changing at home during the day? -> some devices work, some devices not picking up the new prefix for a couple minutes, some do but still try to use the old address. I don't care where the bug is, which device is at fault - IPv6 has been around for ages now and we still have to deal with this kind of crap. Wouldn't have happened with "IPv4 but longer addresses" and good old NAT. Google is boycotting DHCPv6, for which reason my current workplace simply disabled IPv6 for wifi, because they insist telling the device what address it gets. It seems IPv6 was created for engineers to jack off to, being actually used was just an afterthought.

by zppln 4y ago

puffoflogic 4y ago

Based on your description it appears you attempted to deploy "ipv4 with longer addresses" and got frustrated that this is not at all what ipv6 is. If you were to attempt honestly to deploy the actual ipv6 stack that exists, though not perfect, it would be a better experience.

iforgotpassword 4y ago
> Based on your description it appears you attempted to deploy "ipv4 with longer addresses" Because I honestly think this is what we (99.9999% of people) really need. IPv6 is second system syndrome. Things can fail in a thousand different ways and it's a pita to debug. Look no further than the "easy it sucks" top comment. I've had so many random bullshit problems in both, Enterprise environments and with home setups. Buggy SLAAC, buggy DHCPv6, buggy PD, just hot garbage everywhere. Prefix changing at home during the day? -> some devices work, some devices not picking up the new prefix for a couple minutes, some do but still try to use the old address. I don't care where the bug is, which device is at fault - IPv6 has been around for ages now and we still have to deal with this kind of crap. Wouldn't have happened with "IPv4 but longer addresses" and good old NAT. Google is boycotting DHCPv6, for which reason my current workplace simply disabled IPv6 for wifi, because they insist telling the device what address it gets. It seems IPv6 was created for engineers to jack off to, being actually used was just an afterthought.