2. that’s what ipv6-only w/ nat64 is for (thank goodness)
3. i’m not sure this is the flex you think it is: https://twitter.com/noipv6/status/1575662492063174656
4. okay?
5. okay
6. that people are “used to” dotted decimal ip addresses just means ppl can learn arbitrary things. there’s nothing inherently more natural about legacy ip addresses than ipv6 addresses.
7. enterprises that need/want ipv6 are deploying ipv6. source: my job
8. okay
9. this almost sounds like 6rd fwiw
=D
3. Yeah, it shows my ipv4 only, and I have both. Do you not have a v4?
6. No, there's not, but the reality is everyone you're trying to switch over to v6 is already used to v4, and it's like herding cats.
1. why would you add the extra step of using a “v4-mapped v6 address” if you’re just going to end up using regular ones?
3. if you have ipv6 but that google link shows a legacy ip address, your ipv6 connectivity is broken somehow. you’re not behind some sort of weird nat66, are you?
6. that’s getting less true with every passing year, thankfully
2. Because a bunch of those are also stuck running v4 on the side and would probably love for v6 adoption to move forward so they can drop the technical debt.
3. https://www.google.com/search?client=firefox-b-1-d&q=what+is...
4. My v6 addr is different from my v4, is what I'm saying.
5. My bad, I mixed up "octal" and "octet." It's decimal notation, which is made of octets.
6. Yeah, idk, it's what they said. Do people memorize IPs, probably not, except for local 192. or 10. ones. Do people note them in short-term memory while debugging, yes. The colon-separated hex is more annoying to me, maybe because I'm used to decimal, but then again so are most people.
7. I would say then, common workaround for enterprises that actually need/want to use ipv6 sooner or later.
8. Gee, I'm sorry for the mixup. Seems you got which one I meant anyway.
9. It probably is too late to do this everywhere. Maybe ISPs could hand out 4-mapped v6 addresses at least, idk if that's possible.