<?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 Re: ASA phase 2 - encryption domain in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-phase-2-encryption-domain/m-p/3391168#M956872</link>
    <description>Just add the required routing info for that public IP and you ll make it.&lt;BR /&gt;Obviously you will use as next hop and outbound interface the interface that gets VPN packets out.</description>
    <pubDate>Wed, 30 May 2018 11:17:13 GMT</pubDate>
    <dc:creator>Florin Barhala</dc:creator>
    <dc:date>2018-05-30T11:17:13Z</dc:date>
    <item>
      <title>ASA phase 2 - encryption domain</title>
      <link>https://community.cisco.com/t5/network-security/asa-phase-2-encryption-domain/m-p/3389291#M956866</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a cisco ASA 5525, and I need to establish a vpn site to site.&lt;BR /&gt;It establishes phase 1 without problems, but for phase 2 they ask me to use a Public IP for the encryption domain, however that ASA does not have a direct connection to the Internet.&lt;BR /&gt;Is there any way to "cheat", with loopback or nat?&lt;BR /&gt;The internal server has an internal IP (belongs to an ASA interface -&amp;gt; dmz_3)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Interface Name Security&lt;BR /&gt;GigabitEthernet0 / 0 Outside 0&lt;BR /&gt;GigabitEthernet0 / 1 Inside 100&lt;BR /&gt;GigabitEthernet0 / 2 dmz 50&lt;BR /&gt;GigabitEthernet0 / 3 dmz_2 55&lt;BR /&gt;GigabitEthernet0 / 4 dmz_3 55&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;TNKs!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:48:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-phase-2-encryption-domain/m-p/3389291#M956866</guid>
      <dc:creator>christiancruz88</dc:creator>
      <dc:date>2020-02-21T15:48:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA phase 2 - encryption domain</title>
      <link>https://community.cisco.com/t5/network-security/asa-phase-2-encryption-domain/m-p/3391168#M956872</link>
      <description>Just add the required routing info for that public IP and you ll make it.&lt;BR /&gt;Obviously you will use as next hop and outbound interface the interface that gets VPN packets out.</description>
      <pubDate>Wed, 30 May 2018 11:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-phase-2-encryption-domain/m-p/3391168#M956872</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2018-05-30T11:17:13Z</dc:date>
    </item>
  </channel>
</rss>

