It does take more work to run dual stack. I wanted to avoid duplicating efforts when I set out to learn ipv6, so I disabled ipv4 routing on my network and just ran ipv6 with DNS64/NAT64 to provide my clients access to legacy services. In this configuration, most of my traffic was end-to-end ipv6. I tested iOS, Android, Windows, and Ubuntu clients with no issues, even my aging printers support it!
The only issue I have is the same issue found in the article, but in reverse: now that I have a securely configured ipv6 network, how can I ensure that my hosts are fully prevented from communicating over a rogue ipv4 net?
The only issue I have is the same issue found in the article, but in reverse: now that I have a securely configured ipv6 network, how can I ensure that my hosts are fully prevented from communicating over a rogue ipv4 net?