Like what though?
The last thing I have that doesn’t support ipv4 from the hardware level is my Nintendo DS.
Everything else has the hardware capability, it’s just never used or enabled in the software by default.
A massive swathe of current gen devices don’t even support it.
It won’t be a month.
Microsoft announce changes much smaller than that 4 years out and still have to give extensions.
Like what though?
The last thing I have that doesn’t support ipv4 from the hardware level is my Nintendo DS.
Everything else has the hardware capability, it’s just never used or enabled in the software by default.
it’s just never used or enabled in the software by default
…and most people who own those devices have never heard of IPv6 and don’t know how to enable it.
this shouldnt be a.burden for users.
you can simply update a device to support it by default.
My smart TV from two years ago does not support ipv6, and it was fairly high end.
What manufacturer/operating system?
Vizio. Technically I don’t see anything saying yes or no on IPv6 but I didn’t find any relevant settings on the TV network config, nor do I see any IPv6 address on my router.
I did see an online post of someone saying similar, except the Chromecast functionality used IPv6
Wasn’t 64 but adoption largely driven by Microsoft deciding they weren’t making a 32 but version of their next Windows at one point? It seems it might take something similar.
Microsoft supports 32 bit processors still with windows 10. They died out because it was becoming clear that 4GB of memory wasn’t going to be enough for applications, and the low margins on budget chips didn’t warrant maintaining 32 bit designs when the 64 bit versions would do and could still run the 32 bit software.
No, 64 bit was widely adopted long before windows cut support. Keep in mind a 32 bit OS can only use ~4GB of ram, and most systems have been shipping with more than that for many years now.
Towards the end of 32 bit’s life, physical address extension allowed operating systems to use more memory, often up to 40 bits worth, but still could still expose a 32 bit address space to user applications.
Yes, but that would only get the total up to about 5GB, which isn’t very much more.
thats why dual stack exists. so older devices can still be used on an ipv6 network.
just give us a functioning ipv6 infrastructure, whats the damn holdup at this point??
my 3rd world country has it but big us players like amazon seemingly cant do it.
Shdwdrgn@mander.xyz 9 months ago
Seriously? How can any device call themselves current gen and not support something as basic as this? That’s just embarrassing.
Archer@lemmy.world 9 months ago
Android doesn’t support DHCPv6 lol
hddsx@lemmy.ca 9 months ago
Why not? Isn’t there a dhcpd6 in Linux?
Archer@lemmy.world 9 months ago
Initial feature request was in 2012
Shdwdrgn@mander.xyz 9 months ago
Ugh… still? I knew the mail app had shitty support for it and had to create an IPv4-only dns entry for my mail server, I didn’t realize the whole system was broken. Ah well, despite being an android user myself I would still place it in the bucket of “not modern” because there’s really no excuse for something like this.
Appoxo@lemmy.dbzer0.com 9 months ago
Getting plenty of local link and global ipv6 adresses on my pixel 7…
Archer@lemmy.world 9 months ago
Probably via SLAAC. Android doesn’t follow the specifications for getting an individual DHCPv6 address