I still think IPv6 can be safely ignored.
This articles section "here are some reasons you should start using IPv6 within your own network" seems to comfirm this. None of the 6 "reasons" speak to me.
I spent a week without IPv4 to understand IPv6 transition mechanisms
21–30 of 511 posts
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#22Great idea. Now a question for the group. What are the non-network team business benefits to IPv6 over v4? That is what drives adoption.
Increased number of available IP addresses, improved security features, simplified network management, reduced network complexity, and support for new technologies. IPv6 also provides significant performance benefits for mobile networks, IoT devices, and cloud services. The adoption of IPv6 will lead to cost savings, improved network performance, and increased scalability.
[flagged]
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#23I am quite happy that all those shady IoT devices cannot be reached from the internet directly when I am using IPv4 and NAT - what would be the best way forward to keep it that way in a IPv6-only future? The best idea I can come up with (at least right now) is: put all less trustworthy (read: Closed source) devices into a special legacy IPv4 network and only use IPv6 on my workstation and little Raspis?
You can configure your local ipv6 net without SLAAC (Stateless Address Autoconfiguration).
Or differently put, you don't need to use the net your isp provides everywhere, ipv6 can still use NAT if you want it to: https://openwrt.org/docs/guide-user/network/ipv6/ipv6.nat6
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#24I have built a couple of dual stack Kubernetes clusters already and they work much better to be honest. Most of the problems are solved and especially for node-based-ranges it works really well. Even in ipv6 only mode calico will manage amazingly and so do my OpenWRT routers. HOWEVER, My ISP regularly messes up with its ipv6 routing (deutsche Telekom (so as big as it can get for me) and if that's not the problem, the…
Yeah I found the same on Hyperoptic in London. Works fine 99.9% of the time, but occasionally ipv6 drops until I restart the router/restart the WAN connection. Which of course I barely ever notice because most stuff switches back to ipv4.
I think unless we start seeing ipv6-only stuff this will be the case, there's really no incentive for a lot of testing/debugging on at least consumer ipv6 connections until stuff actually breaks.
Would be cool if Google added a 'ipv4' warning to Chrome similar to how they do with HTTPS (maybe not as strong though). That would drive a lot of adoption.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#25Is there any risks of nodes assigning same IP if there's no central DHCP?
Not if you don't have same MAC in the network .
SLAAC reserves bottom 64 bits for autoconfiguration, and while incredibly wasteful it does ensure every MAC can have its own IP address
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#26I am quite happy that all those shady IoT devices cannot be reached from the internet directly when I am using IPv4 and NAT - what would be the best way forward to keep it that way in a IPv6-only future? The best idea I can come up with (at least right now) is: put all less trustworthy (read: Closed source) devices into a special legacy IPv4 network and only use IPv6 on my workstation and little Raspis?
> what would be the best way forward to keep it that way in a IPv6-only future?
Firewalls. You configure what traffic should be allowed from who to who. Default deny incoming traffic, and its the same behavior as when you had a NAT.
Something having a routable IP address doesn't mean it needs to receive all traffic addressed to it.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#27I am quite happy that all those shady IoT devices cannot be reached from the internet directly when I am using IPv4 and NAT - what would be the best way forward to keep it that way in a IPv6-only future? The best idea I can come up with (at least right now) is: put all less trustworthy (read: Closed source) devices into a special legacy IPv4 network and only use IPv6 on my workstation and little Raspis?
Most consumer routers will disable inbound connections for the IPv6 prefix by default from what I've seen. If not thats easy to enable.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#28Everyone always goes with the "You don't need NAT, everything is globally routable!" argument, as if that's something that anybody wants. Everything on my network is going to go through my firewall anyway. I don't want anything on my network to be globally routable.
Of course, this is not a good reason to not use IPv6, don't get me wrong. It's a problem that's easy to overcome, I just think it's not a good way to get people excited about the transition.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#29Is there any risks of nodes assigning same IP if there's no central DHCP?
Don't worry coz DAD (Duplicate Address Detection) will come to your rescue :p
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#30Everyone always goes with the "You don't need NAT, everything is globally routable!" argument, as if that's something that anybody wants. Everything on my network is going to go through my firewall anyway. I don't want anything on my network to be globally routable. Of course, this is not a good reason to not use IPv6, don't get me wrong. It's a problem that's easy to overcome, I just think it's not a good way to get…
That's what a firewall is for, NAT does nothing here.