<?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 In that case the ISP is doing in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855548#M153406</link>
    <description>&lt;P&gt;In that case the ISP is doing the NAT for you and forwards all traffic for 2.2.3.4 to your ASA.&lt;/P&gt;
&lt;P&gt;Just configure it with the public IPs as mentioned above. The packets from ASA1 will arrive with a destination of 192.168.1.1 on you ASA2, but ASA1 "sees" ASA2 as 2.2.3.4.&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jun 2016 08:23:04 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2016-06-01T08:23:04Z</dc:date>
    <item>
      <title>ASA with twice NAT on outside interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855545#M153403</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have question.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Situation:&lt;/P&gt;
&lt;P&gt;ASA1 - ip address 1.2.3.4 (internet routable)&lt;/P&gt;
&lt;P&gt;ASA2 - ip address 192.168.1.1 (RFC1918) and NATed 2.2.3.4&lt;/P&gt;
&lt;P&gt;Address 2.2.3.4 is routed from internet to address 192.168.1.1.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I want to make ipsec tunnel between those two ASA.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;But because ASA2 has RFC1918 address I need to make a NAT for routable address.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What I would like to achieve is: when comes packet from ASA1 (1.2.3.4) to 2.2.3.4, ASA2 makes NAT that : 2.2.3.4 = 192.168.1.1. Is it possible? Because this all is on outside interface.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;So making some of static or twice NAT?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:49:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855545#M153403</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2019-03-12T07:49:38Z</dc:date>
    </item>
    <item>
      <title>If I understand you correctly</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855546#M153404</link>
      <description>&lt;P&gt;If I understand you correctly, there is a NAT device in front of ASA2 that NATs the public IP 2.2.3.4 to the internal ASA-IP 192.168.1.1?&lt;/P&gt;
&lt;P&gt;Then there is no NAT to be configured on ASA2. You have to:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Configure the VPN on ASA1 with a peer address of 2.2.3.4&lt;/LI&gt;
&lt;LI&gt;Configure the VPN on ASA2 with a peer address of 1.2.3.4&lt;/LI&gt;
&lt;LI&gt;Make sure that the NAT-device allows UDP/500 and UDP/4500 to ASA2&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Wed, 01 Jun 2016 08:02:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855546#M153404</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2016-06-01T08:02:04Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855547#M153405</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for responding.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;No, there is no device in front of ASA2 making NAT (this would be also solution). There is just pure routing (point to point link between ASA2 and ISP is 192.168.1.0/28 - ie).&lt;/P&gt;
&lt;P&gt;So, by routing on ASA2 I got packet with source 1.2.3.4 and destination 2.2.3.4, but ASA2 doesn't know what to do with packet destined to address 2.2.3.4.&lt;/P&gt;
&lt;P&gt;I know, that this is not problem when mapped and real address are on diferent interfaces.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Does it make sense?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2016 08:13:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855547#M153405</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2016-06-01T08:13:43Z</dc:date>
    </item>
    <item>
      <title>In that case the ISP is doing</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855548#M153406</link>
      <description>&lt;P&gt;In that case the ISP is doing the NAT for you and forwards all traffic for 2.2.3.4 to your ASA.&lt;/P&gt;
&lt;P&gt;Just configure it with the public IPs as mentioned above. The packets from ASA1 will arrive with a destination of 192.168.1.1 on you ASA2, but ASA1 "sees" ASA2 as 2.2.3.4.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2016 08:23:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855548#M153406</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2016-06-01T08:23:04Z</dc:date>
    </item>
    <item>
      <title>As I said, ISP is not doing</title>
      <link>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855549#M153407</link>
      <description>&lt;P&gt;As I said, ISP is not doing NAT.&lt;/P&gt;
&lt;P&gt;I need to make NAT myself.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2016 08:28:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-with-twice-nat-on-outside-interface/m-p/2855549#M153407</guid>
      <dc:creator>Pavel Pokorny</dc:creator>
      <dc:date>2016-06-01T08:28:42Z</dc:date>
    </item>
  </channel>
</rss>

