<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic NAT Translations Related to VPN Tunnels in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/nat-translations-related-to-vpn-tunnels/m-p/1233834#M6094</link>
    <description>&lt;P&gt;Thanks for any help in advance.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have many partners that we create VPN tunnels with.&amp;nbsp; To save time and to avoid IP overlap, I would like to dedicate a private subnet like 10.10.0.0/16 and route that subnet toward our Palo firewall that terminates VPNs.&amp;nbsp; I would like to use IP addressing in that subnet to NAT the partner traffic as it comes inbound off of a VPN tunnel.&amp;nbsp; I would like to perform this NAT on the Palo that is terminating VPN tunnels.&amp;nbsp; Sometimes, we have partners that connect to the same server for the same type of resource.&amp;nbsp; Here is an example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Partner IP address as built on the tunnel:&amp;nbsp; 172.16.1.1 needs to connect to a server in our datacenter at to perform LDAP lookups:&amp;nbsp; 172.20.1.10.&amp;nbsp; In this case (since there may be multiple partners doing this), I would also want to NAT this IP address to one of our public IP addresses before dropping onto the VPN tunnel.&amp;nbsp; For this example, let's assume that we have this public IP address available to NAT to our server:&amp;nbsp; 100.112.2.49.&amp;nbsp; We can use 10.10.10.1 as a NAT for the partner IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To clarify, the "crypto map" would contain these proxy ids:&amp;nbsp; 100.112.2.49 to/from 172.16.1.1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The NAT translation would be:&lt;/P&gt;
&lt;P&gt;100.112.2.49 to 172.20.1.10 and 172.16.1.1 to 10.10.10.1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have this setup in a lab.&amp;nbsp; When I ping from the "partner" side of the VPN, the "Datacenter Server" sees the ping request and responds.&amp;nbsp; The partner side never receives the response.&amp;nbsp; Pinging from the datacenter server, there is no response and with my lab, i cannot determine if the partner side is seeing the request.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please see attached diagram.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if there is any other information needed to help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Andrew&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jul 2025 17:25:48 GMT</pubDate>
    <dc:creator>Andrew_Ours</dc:creator>
    <dc:date>2025-07-11T17:25:48Z</dc:date>
    <item>
      <title>NAT Translations Related to VPN Tunnels</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/nat-translations-related-to-vpn-tunnels/m-p/1233834#M6094</link>
      <description>&lt;P&gt;Thanks for any help in advance.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have many partners that we create VPN tunnels with.&amp;nbsp; To save time and to avoid IP overlap, I would like to dedicate a private subnet like 10.10.0.0/16 and route that subnet toward our Palo firewall that terminates VPNs.&amp;nbsp; I would like to use IP addressing in that subnet to NAT the partner traffic as it comes inbound off of a VPN tunnel.&amp;nbsp; I would like to perform this NAT on the Palo that is terminating VPN tunnels.&amp;nbsp; Sometimes, we have partners that connect to the same server for the same type of resource.&amp;nbsp; Here is an example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Partner IP address as built on the tunnel:&amp;nbsp; 172.16.1.1 needs to connect to a server in our datacenter at to perform LDAP lookups:&amp;nbsp; 172.20.1.10.&amp;nbsp; In this case (since there may be multiple partners doing this), I would also want to NAT this IP address to one of our public IP addresses before dropping onto the VPN tunnel.&amp;nbsp; For this example, let's assume that we have this public IP address available to NAT to our server:&amp;nbsp; 100.112.2.49.&amp;nbsp; We can use 10.10.10.1 as a NAT for the partner IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To clarify, the "crypto map" would contain these proxy ids:&amp;nbsp; 100.112.2.49 to/from 172.16.1.1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The NAT translation would be:&lt;/P&gt;
&lt;P&gt;100.112.2.49 to 172.20.1.10 and 172.16.1.1 to 10.10.10.1&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have this setup in a lab.&amp;nbsp; When I ping from the "partner" side of the VPN, the "Datacenter Server" sees the ping request and responds.&amp;nbsp; The partner side never receives the response.&amp;nbsp; Pinging from the datacenter server, there is no response and with my lab, i cannot determine if the partner side is seeing the request.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please see attached diagram.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if there is any other information needed to help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Andrew&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 17:25:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/nat-translations-related-to-vpn-tunnels/m-p/1233834#M6094</guid>
      <dc:creator>Andrew_Ours</dc:creator>
      <dc:date>2025-07-11T17:25:48Z</dc:date>
    </item>
  </channel>
</rss>

