- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
05-01-2013 08:27 AM
I'm running PANOS 4.0.13 and I've enabled NAT-T via the command line. I'm having trouble getting traffic to pass and I assume it must be my NAT policy.
1. I set a destination NAT as the vendor will be the initiator. The NAT is defined like this:
srczone: Vendor-VPN
dstzone: Untrust dstaddr: NAT IP (172.1.1.1.) dst translation addr: Real IP (10.1.1.1)
After writing this, perhaps the dstzone should be Trust, but I don't see that as the proper designation from the Doc's I'm reading.
2. I also tried making a Bi-Directional static Source NAT like so, but it doesn't appear to be working:
srczone: Trust srcaddr: real IP (10.1.1.1) src translation addr: nat IP (172.1.1.1.)
dstzone: Vendor-VPN
Please let me know your suggestions.
06-11-2013 09:17 AM
For your destination NAT: Assuming 'Vendor-VPN' is the zone the tunnel terminates on,
NAT rule should be:
srczone: Vendor-VPN
dstzone: Vendor-VPN dstaddr: NAT IP (172.1.1.1.); dst translation addr: Real IP (10.1.1.1)
Security policy:
srczone: Vendor-VPN
dstzone: Trust dstaddr: NAT IP (172.1.1.1.)
Looks like the bi-directional static NAT should have worked as well, not sure why it didn't. You can trace the NAT IP/nat rules/security rules matching the traffic from the traffic logs.
Thanks,
Aditi
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!