71–78 of 78 posts
All we need is ONE major website to declare 24 Hour brown-out for IPv4 and put a message something like "Contact your ISP to upgrade your connection". Alas, publicly traded companies....
Think you will need more than that!! Rollout has stagnated for over 20 years.
Citation "IPv6 was designed to restore the end-to-end model of communications with all nodes on networks using globally unique addresses. But considering this, IPv6 may imply privacy concerns due to greater visibility on the Internet."
The only difference is, that you're not "protected" by nat, so packets going back to you, can go back to you (but this is solved by a simple firewall installed by default on pretty much any ipv6 enabled CPE). With ipv6 privacy extensions, your IP address changes every few minutes (withoin the same /64 network) so it's not a lot different (privacy wise) than today, wher that whole network would be hidden behind a sing…
What happens to all old software that is more or less "hard-coded" to use IPv4 addresses? Will there be an OS layer that can run an app in IPv4 compatibility mode of some sort?
Earlier quoted context omitted.
My ISP offers a plan without IPv4 at a lower price. v4 websites only are served through their NAT64/DNS64 infrastructure and it works really well except for some dumb applications that hardcode the IPv4 instead of using domain names (yeah, and also the ones that rewrite the entire stack in C and only support AF_INET...)
If possible, can you share the ISPs name?
Earlier quoted context omitted.
Why do you need that? What's wrong with SLAAC and RDNSS?
I got a local NTP server and I want to assign it to my network clients. AFAIK the only way is via DHCPv6.
In 99.99% of the cases you have to intercept or reconfigure.
Earlier quoted context omitted.
I will be calling to complain if I am not assigned an ipv4 address by default. Very first thing I do whenever I move or get a new router is disable all ipv6. All of my client devices have ipv6 disabled. ipv6 takes a very simple addressing schema and unnecessarily turns it into an entire beeping protocol for no reason. I don't care if I have to write angry letters to senators to pass laws forbidding the sunsetting of…
> ipv6 takes a very simple addressing schema and unnecessarily turns it into an entire beeping protocol for no reason. IPv6 is simpler than IPv4 in that you don't need to setup infrastructure (e.g., DHCP) to get going.
Earlier quoted context omitted.
Why do you need that? What's wrong with SLAAC and RDNSS?
I got a local NTP server and I want to assign it to my network clients. AFAIK the only way is via DHCPv6.
Also, does Android even use NTP servers that are advertised over IPv4 DHCP? I don't think so, and if not, then is this really a reason?
Oh boy.
I've been working in IT for 30 years, managed plenty of servers, host services at home, develop FOSS and whatnot but never got interested in IPv6.
And I must say that this is a scary world. Some of my devices suddenly were getting their DNS settings from something else than the DHCP, I had to learn quickly about RA and other anagrams. I was super worried about the exposition of my services - something I completely controlled in IPv4.
With this in mind, I think that IPv6 is too complicated. It does not have that sweet spot between "plug the green cable to the socket called ETH" and "I am going to try to squeeze some extra bits into the datagram".