<?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 Vpn clarification in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352610#M306703</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI shibu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your edge is doing a one to one NAT for the ASA outside interface than there should be no issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But it the edge router is doing a PAT than you have no option but to enable the NAT-t on the remote end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because NAT-T doesn't work with PAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jeet Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Dec 2013 19:25:05 GMT</pubDate>
    <dc:creator>Jeet Kumar</dc:creator>
    <dc:date>2013-12-26T19:25:05Z</dc:date>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352608#M306701</link>
      <description>&lt;P&gt;Dears,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a query regarding Site to Site VPN setup between a Juniper SRX 3600 and Cisco asa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a Cisco ASA and the client has a Juniper SRX 3600.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scenario here is our end Cisco ASA outside interface is private ip (10.10.10.10) &amp;amp; Public ip(static one to one) mapping is being done at the perimeter router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Client side they have direct public configured on the Juniper SRX 3600 with NAT-Trasversal disabled on the corresponding tunnel towards our side.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They have a strict policy to disable NAT-T which they wont enable it.So we have too disable NAT-T here on the tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue here is Phase-1 is coming up but phase 2 i dont see any IPSEC SA.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;SPAN style="font-size: 10pt;"&gt;In this scenario where our ASA behind a NAT device (router) with NAT-T disabled will the site to site vpn works ? Will the tunnel comes up disabling NAT-T?&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Any assistance will be helpfull.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 03:21:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352608#M306701</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2019-03-12T03:21:54Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352609#M306702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any response would be highly appreciated thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Dec 2013 19:00:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352609#M306702</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2013-12-26T19:00:48Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352610#M306703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI shibu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your edge is doing a one to one NAT for the ASA outside interface than there should be no issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But it the edge router is doing a PAT than you have no option but to enable the NAT-t on the remote end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because NAT-T doesn't work with PAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jeet Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Dec 2013 19:25:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352610#M306703</guid>
      <dc:creator>Jeet Kumar</dc:creator>
      <dc:date>2013-12-26T19:25:05Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352611#M306704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jeet,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pl see my response inline.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;If your edge is doing a one to one NAT for the ASA outside interface than there should be no issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;&lt;STRONG&gt;Shibu :&amp;nbsp;&amp;nbsp;&amp;nbsp; YES we do one to one NAT.&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif; min-height: 8pt; height: 8pt;"&gt;&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;So you mean site to site vpn works fine with NAT-T disbled at both end.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;amp;&amp;nbsp; One to one NAT configured on the perimeter device for the ASA private IP.&amp;nbsp; pl clarify&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Dec 2013 19:33:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352611#M306704</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2013-12-26T19:33:00Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352612#M306707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any update on this?&amp;nbsp; really appreciated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Dec 2013 11:55:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352612#M306707</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2013-12-28T11:55:00Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352613#M306710</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;A little clarification:&lt;/P&gt;&lt;P&gt;Q. Why is NAT-T needed?&lt;/P&gt;&lt;P&gt;A. In phase 2 and the last messages of phase1, the packets being sent between peers are encrypted ESP packets (IP-proto-50). So when an encrypted packet goes through a device running PAT, it will be dropped since it doesnt use port numbers. In these cases, NAT-T is used to send UDP 4500 packets instead of ESP packets. &lt;SPAN style="font-size: 10pt;"&gt;So, if you are behind a NAT device, you need to enable NAT-T.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for the NATing on the router, you need to add 2 static NAT statements to allow UDP 500 and UDP 4500 packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre; background-color: #ffffff; color: #666666; font-family: Consolas, Monaco, 'Lucida Console', monospace; font-size: 0.857142857rem; line-height: 1.714285714;"&gt;ip nat inside source static udp X.X.X.X 500 interface FastEthernet0/0 500&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre; background-color: #ffffff; color: #666666; font-family: Consolas, Monaco, 'Lucida Console', monospace; font-size: 0.857142857rem; line-height: 1.714285714;"&gt; &lt;/SPAN&gt;&lt;SPAN style="white-space: pre; background-color: #ffffff; color: #666666; font-family: Consolas, Monaco, 'Lucida Console', monospace; font-size: 0.857142857rem; line-height: 1.714285714;"&gt;ip nat inside source static udp X.X.X.X 4500 interface FastEthernet0/0 4500&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="white-space: pre; background-color: #ffffff; color: #666666; font-family: Consolas, Monaco, 'Lucida Console', monospace; font-size: 0.857142857rem; line-height: 1.714285714;"&gt;This is called Port Forwading and will pass any VPN traffic to the ASA.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you implement static NATing without ports, all traffic going to the public ip of the router will go to the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to disable NAT-T, you can have the router become the termination point of the VPN instead of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Zaid Al-Kurdi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Dec 2013 13:57:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352613#M306710</guid>
      <dc:creator>zalkurdi</dc:creator>
      <dc:date>2013-12-28T13:57:42Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352614#M306713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Zaid,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here in the Perimeter router we have static nat configured&amp;nbsp; as below . not PAT with port numbers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip nat inside source static *.*.*.*&amp;nbsp; *.*.*.* &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="background-color: #f7fafb; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;Q. Why is NAT-T needed?&lt;/P&gt;&lt;P style="background-color: #f7fafb; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;A. In phase 2 and the last messages of phase1, the packets being sent between peers are encrypted ESP packets (IP-proto-50). So when an encrypted packet goes through a device running PAT, it will be dropped since it doesnt use port numbers. In these cases, NAT-T is used to send UDP 4500 packets instead of ESP packets. So, if you are behind a NAT device, you need to enable NAT-T.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Shibu :&amp;nbsp;&amp;nbsp; Our ASA is behind a NAT device(Router) &amp;amp; configured static NAT as above.&amp;nbsp;&amp;nbsp; I am bit confused about your statement which tells about PAT&lt;/STRONG&gt;.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;As Mr.Jeet kumar mentioned above with out NAT-T ESP should work fine with static NAT.&amp;nbsp; Could you pl clarify here?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to disable NAT-T, you can have the router become the termination point of the VPN instead of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S&lt;STRONG&gt;hibu: We cannot make Router as the temination point as this is owned by providers datacentre&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is there any way we can make the tunnel up with disabling NAT-T on both ends.&amp;nbsp;&amp;nbsp; I am very badly needed a solution for this&lt;/STRONG&gt;?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Dec 2013 15:35:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352614#M306713</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2013-12-28T15:35:55Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352615#M306718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could someone give me clear clarity on this reqeust?&amp;nbsp; any response would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Dec 2013 17:28:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352615#M306718</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2013-12-28T17:28:44Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352616#M306737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;any response on this would be appreciated. thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 29 Dec 2013 05:41:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352616#M306737</guid>
      <dc:creator>Shibu1978</dc:creator>
      <dc:date>2013-12-29T05:41:03Z</dc:date>
    </item>
    <item>
      <title>Vpn clarification</title>
      <link>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352617#M306738</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;Now if you want to statically map the public IP of the router to the IP of the ASA, that would work. &lt;/P&gt;&lt;P&gt;However, this will make all traffic to that IP, not just VPN, go to the ASA. My suggestion was to allow only VPN traffic through. &lt;/P&gt;&lt;P&gt;This is totally up to you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Dec 2013 07:33:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-clarification/m-p/2352617#M306738</guid>
      <dc:creator>zalkurdi</dc:creator>
      <dc:date>2013-12-30T07:33:51Z</dc:date>
    </item>
  </channel>
</rss>

