I spent a week without IPv4 to understand IPv6 transition mechanisms
1–10 of 511 posts
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#2He also has a video for the topic https://www.youtube.com/watch?v=e-oLBOL0rDE
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#3Why should I spend the time and energy to deal with IPv6 when disabling it fix many issues ? The listed advantages are not worth the troubles in my experience.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#4Great idea. Now a question for the group.
What are the non-network team business benefits to IPv6 over v4? That is what drives adoption.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#5I recently upgraded my lab and network to support IPV6. I wish I had waited two weeks so I could have read this first.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#6[deleted]
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#7Why should I spend the time and energy to deal with IPv6 when disabling it fix many issues ? The listed advantages are not worth the troubles in my experience.
Would have been great if the post quantified the advantages.
For networks (order of preference): IPv6 only > IPv4 Only > Dual Stack.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#8I 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?
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#9Great idea. Now a question for the group. What are the non-network team business benefits to IPv6 over v4? That is what drives adoption.
IPv4 is now stretched to the point that you often end up requiring multiple layers of NAT, such as carrier-grade NAT plus endpoint NAT. That reduces the reliability of pretty much all protocols and makes any protocol doing peer to peer communication really hard or even impossible to run. The latter includes tons of games, video chat, peer to peer VPNs, decentralized social networks, and so on.
These problems will only get worse from here on out, but they're not as visible to people outside networking because this degradation of quality of service is a slow creep. The IPv4 Internet just gradually gets more and more limited in capability and less reliable for anything beyond the most basic use cases.
IPv4's address space is simply too small. There are already almost twice as many people on Earth as there are possible IPv4 addresses, and that assumes perfectly efficient utilization of IP addresses which is pretty much impossible. In reality there are probably 8-10X as many humans as viable IPv4 addresses. If every human being tends to have a computer and a phone that means there's at least 20X more devices than IPs.
Re: I spent a week without IPv4 to understand IPv6 transition mechanisms
#10I 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?
Network segmentation, i.e use of vlans is the traditional way to solve this.