CCIE and its experiments | Life after CCIE

For the past few days, I've been trying to implement a dual-stack network for my home VLAN (non-IoT), but today it fails due to no supported feature set on some devices in my network. I want to describe the details so that you too can learn from my mistakes or guide me to do better. My home network is designed like this: If you remember, I have written an article " Does NAT66 or NPTv6 need it? " These are similar requirements. My ISP modem and Dream Machines, both are designed to obtain IPv6 using the Prefix Delegation or static assignments. The ISP modem is getting PD subnet, but it is failing to supply to the Dream machine. Now, I have a single option for assigning IPv6 as Static on the Dream Machine. And I have assigned the Site Local Subnet in the LAN and configured NAT with ipv6table. Used nonstandard option as ip6tables -t nat -A POSTROUTING -o eth4 -j MASQUERADE. There is no direct option to configure NATv6.NAT66, NAT64 etc. What was the failure with this scenario:...

Does NAT66 or NPTv6 need it? Let's understand the NAT requirements with an Ipv6 address. Have you ever heard that we don't require NATing with IPv6? Is it true?  My answer will be yes if you are a CCNA student, otherwise, it is only a half-truth. How? Let's try to understand with a few examples: 1. In Theoretical or book statements, IPv6 does not require any NATing because we have enough IPv6 Addresses. Your ISP might supply a/48 prefixes, so you have more than the required networks or prefixes for your office/home. So mostly you will not have to translate from private to public or vice versa. But is it a 100% true statement? I think no and practical is also approved no. Let's check other points.  2. What if your ISP modem does not respond to the Client's RA messages? If you still need Ipv6 Enabled network, then you mostly prefer to use NPTv6.  3. In the future you might change your ISP and you don't want to be stuck in a face to reconfigure the complete network...