71–80 of 353 posts
Why can't we paste aan ipv6 address into the browser address bar and have it go to that address? I'm forced to open [long brackets ] and the it works. Why!???? Ipv4 address just works without the hitch
Earlier quoted context omitted.
I just hope ipv6 doesn't have privacy nightmare that 1 device will always get 1 IP. Currently, the isp I use provides dynamic ip, so on every router restart my ip gets changed. If they starts to provide ipv6, I hope they give options to rotate it frequently, so toxic companies like meta, facebook, microsoft can't connect my device & ip.
It rotates about once a day in most operating systems. Called ipv6 privacy extensions. This is of course defeatable, but it provides a nice black hole for a device. It moves on and you can't connect to it anymore.
Earlier quoted context omitted.
Firewalls are more complex on IPv6 (you need to pass a bunch of ICMPv6 through, to make it work), and some residential routers have very bad or even zero firewall support for ipv6, so your devices, that would otherwise be "protected" (not really) by NAT are now directly visible to everyone on the internet. This usually isn't a problem for power users (who know how to set up and (re)confgure a firewall) nor for most b…
> Firewalls are more complex on IPv6 This is not true. Firewall rules work exactly the same in IPv6 land as they do in IPv4 land. > you need to pass a bunch of ICMPv6 through, to make it work Indeed you shouldn't block ICMPv6, but that is not really making anything "more complex". > some residential routers have very bad or even zero firewall support for ipv6 Is there a proven set of routers that go through the troub…
Yes, rules do work exactly the same, but with IPv4, you just let all the connections out through, and let just the established and connected ones back.
> Indeed you shouldn't block ICMPv6, but that is not really making anything "more complex".
But it is... you need a bunch of new rules to pass through, limit or block a bunch of ICMPv6 messages.. there's a whole RFC just for that - https://datatracker.ietf.org/doc/html/rfc4890
> Is there a proven set of routers that go through the trouble of supporting IPv6 routing but not include a firewall?
Yeah, a bunch of ISP CPEs have just a single checkmark "IPv6 firewall" on/off, and some older ones not even that (i'm talking about old sagem and innbox equipment i came in contact with, not sure about other telcos and the shity cpes they give out to the customers).
Anyone go out of their way to disable IPV6 on all their systems, even at the hardware level, like on routers etc? What's a good reason to avoid IPV6?
I recently disabled IPv6 on my home network to make firewall rules more manageable, and I was always under the impression IPv6 adoption was slow. So I was pretty surprised to check and see Google user's adoption has reached 40%. I feel like ISPs are a big push for that.
My website has a few hundred thousand users. My development is completely user driven. I get hundreds of feature requests and other emails regarding my site per month. So far, not a single user mentioned IPv6. So I never added an AAAA record. The codebase has grown for over 10 years now. God knows what subtle breakages would happen when IPv6 requests come in. I wonder if I ever will add IPv6 or just leave the site ru…
> So I never added an AAAA record. IPv4 servers are reachable by IPv6-only clients. ipv6test.google.com famously has only an A (IPv4) record for a reason. > God knows what subtle breakages would happen when IPv6 requests come in. Unless your product deals with the nitty gritty of the networking stack itself, pretty sure everything continues to hum along just fine, if the basics are covered.
Earlier quoted context omitted.
A local ISP told me that they want to get into IPv6 as soon as possible. NATs are getting costly and moving just YouTube traffic to IPv6 would actually help a lot. The problem is with end user devices that do not use a stable DUID and when the client hits the reset button, it changes. We are probably going to work around this by responding from the closest hop and taking the MAC into account.
Why should an unstable DUID matter? The prefix won't change.
“In December 1998, IPv6 became a Draft Standard for the IETF,[2] which subsequently ratified it as an Internet Standard on 14 July 2017.” 40% adoption after 25 years? Really highlights how terrible IPv6 is in terms of backwards compatibility. What we needed was an internet protocol with the benefits of IPv6 that runs as an extension to the IPv4 stack. The current approach to duplicate everything into IPv6 is wasteful…
Despite the downvotes you are right. IPv6 replaces IPv4 rather than building on top of it and this really harmed adoption.