<?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 PPTP NAT and site-to-site IPSEC VPN on same IP address in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14739#M10820</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm doing a firewall migration where i encountered a following situation:&lt;/P&gt;&lt;P&gt;- customer has site-to-site VPNs terminated on public IP address, let's say 1.1.1.1&lt;/P&gt;&lt;P&gt;- customer is using PPTP VPN solutio&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;n which is also terminated on same IP address 1.1.1.1 and DNAT-ed to PPTP server, let's say on address 10.10.10.10&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;- on current fw they have a DNAT rule for just TCP 1723 and GRE protocol which translates packets with destination 1.1.1.1 to 10.10.10.10&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as PA doesn't support use of GRE (protocol or application) in NAT rules i have to make a more general rule which translates every packet coming to 1.1.1.1 to 10.10.10.10&lt;/P&gt;&lt;P&gt;Will site-to-site VPNs terminating on PA on IP address 1.1.1.1 still work in such scenario? Or will they be forwarded to PPTP server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, &lt;/P&gt;&lt;P&gt;Simon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Dec 2014 12:53:44 GMT</pubDate>
    <dc:creator>santonic</dc:creator>
    <dc:date>2014-12-15T12:53:44Z</dc:date>
    <item>
      <title>PPTP NAT and site-to-site IPSEC VPN on same IP address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14739#M10820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm doing a firewall migration where i encountered a following situation:&lt;/P&gt;&lt;P&gt;- customer has site-to-site VPNs terminated on public IP address, let's say 1.1.1.1&lt;/P&gt;&lt;P&gt;- customer is using PPTP VPN solutio&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;n which is also terminated on same IP address 1.1.1.1 and DNAT-ed to PPTP server, let's say on address 10.10.10.10&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;- on current fw they have a DNAT rule for just TCP 1723 and GRE protocol which translates packets with destination 1.1.1.1 to 10.10.10.10&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as PA doesn't support use of GRE (protocol or application) in NAT rules i have to make a more general rule which translates every packet coming to 1.1.1.1 to 10.10.10.10&lt;/P&gt;&lt;P&gt;Will site-to-site VPNs terminating on PA on IP address 1.1.1.1 still work in such scenario? Or will they be forwarded to PPTP server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards, &lt;/P&gt;&lt;P&gt;Simon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Dec 2014 12:53:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14739#M10820</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2014-12-15T12:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: PPTP NAT and site-to-site IPSEC VPN on same IP address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14740#M10821</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A bit more complications: yes i know I can make a no-nat rule above the mentioned DNAT rule for known VPN endpoints. &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;But a couple of VPN endpoints will have dynamic IP addresses&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Dec 2014 12:57:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14740#M10821</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2014-12-15T12:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: PPTP NAT and site-to-site IPSEC VPN on same IP address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14741#M10822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can write your nat rules to be more specific on the port for forwarding in order to distinguish these two servers on the same ip address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you create the nat rule you can leave any source and make the destination port the PPTP port with the translation then to that server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the site to site will arrive on the interface as IPSEC traffic and not hit the PPTP rule at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 00:02:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14741#M10822</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-12-16T00:02:00Z</dc:date>
    </item>
    <item>
      <title>Re: PPTP NAT and site-to-site IPSEC VPN on same IP address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14742#M10823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PPTP includes TCP session on port 1723 and GRE session.&lt;/P&gt;&lt;P&gt;Yes, I can make more specific NAT rule for TCP session.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;But I can't use application or protocol in NAT rule so I can't make specific NAT rule for GRE. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;I also can't make no-NAT rule to prevent NAT for VPN tunnels as it also uses ESP which can't be used in NAT policy.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 07:28:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14742#M10823</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2014-12-16T07:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: PPTP NAT and site-to-site IPSEC VPN on same IP address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14743#M10824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had assumed that the dependent GRE session created by the PPTP session would nat with the ALG.&amp;nbsp; But this is apparently not the case as PPTP is not on this list of ALG that nat correctly.&amp;nbsp; You may want to open a case to see if there is a work around for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also want to be sure there is a feature request filed by your sales engineer to add PPTP to this list in a future release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-8371"&gt;Applications that Support NAT ALG (Application Layer Gateway) Functionality&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Dec 2014 13:27:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pptp-nat-and-site-to-site-ipsec-vpn-on-same-ip-address/m-p/14743#M10824</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-12-20T13:27:09Z</dc:date>
    </item>
  </channel>
</rss>

