- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
02-25-2022 12:30 AM
02-25-2022 02:41 PM
Thank you for the post @AhamadullahM
The purpose of NAT64 is to enable IPv6 only clients to communicate with IPv4 only resources: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClIFCA0 Based on what you have described, you have opposite scenario. You have IPv4 only client to access IPv6 only network. The NAT64 will unfortunately not work in this case.
Kind Regards
Pavel
02-28-2022 01:02 AM
Hi @AhamadullahM ,
Is this the scenario you're looking for ?:
Configure NAT64 for IPv4-Initiated Communication
I hope it helps,
-Kiwi.
02-28-2022 01:19 AM
Thanks for the reply PaveIK,
Could you please let me know, any possible workaround for my scenario? we have to do the source NAT. LAN (IPV4)---to-- ISP(IPV6).
02-28-2022 01:21 AM
No, We have to look for NAT 46
Thanks for your reply
03-01-2022 10:06 PM
Thank you for the reply @AhamadullahM
I am sorry, unfortunately I do not have any hands on experience with NAT46, but on best effort bases I would advice following. Since Palo Alto Firewall does not support NAT46, I would connect IPv6 only ISP link to a router that supports NAT46 (For example Cisco ISR router or Juniper SRX), then let this device do a routing + NAT. The Palo Alto would be connected behind this router for the rest of the functionality (Firewall Features).
If it is technically doable, I would consider dual stack to configure IPv6 between your Firewall and your hosts.
Kind Regards
Pavel
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!