![]() If you're running dual-stack, that IPv4 address is connected to natively using IPv4. For example, an A record query would return an address of "::ffff:192.168.5.5" for the address of 192.168.5.5. If you're unaware of how NAT64 works, here's my rough explanation: An 'A' record that's queried over IPv6 is returned with the regular IPv4 address padded out with '::ffff:' to fit into an IPv6 address space. The one deviation from my previous setup was to use Google's NAT64 DNS servers, not their regular IPv6 DNS servers. I then went and configured a sub-interface tagged with VLAN 2 on the firewall with another IPv6 subnet as before. I just created a new SSID and tagged it to VLAN 2. My first step was to plumb this over to a new SSID that I could use as a personal testbed without screwing up my wife's work connection (and TV watching). To be honest, I put it off for longer than I should because I kind of figured it was going to be a hassle to set up and there were going to be teething issues while using it. I said in that post that I'd like to try out an IPv6 only network to get a feel for using IPv6 exclusively on a day-to-day basis. ![]() A little while ago I wrote a post about getting IPv6 to work on my Palo Alto PA220 firewall with my home internet connection.
0 Comments
Leave a Reply. |