<?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 ASA NAT config architecture, syntax...(?) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809709#M1099312</link>
    <description>&lt;P&gt;&lt;U&gt;GOAL:&lt;/U&gt; Configure NAT in ASA (OS version 9.x) so that two LAN VPN devices can erect tunnels to one remote www VPN endpoint.&lt;/P&gt;&lt;P&gt;&lt;U&gt;GIVEN:&lt;/U&gt; ASA Outside interface= 1.1.1.1 , remote www VPN endpoint= 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;U&gt;CONFIGURATION:&lt;/U&gt;&lt;BR /&gt;object network VPN-DEVICES-LOCAL&lt;BR /&gt;ip address 172.16.2.2 255.255.255.255&lt;BR /&gt;ip address 172.16.9.2 255.255.255.255&lt;/P&gt;&lt;P&gt;nat (Inside,Outside) source static VPN-DEVICES-LOCAL 1.1.1.1 destination static 2.2.2.2 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;U&gt;QUESTIONS:&lt;/U&gt;&lt;BR /&gt;1. &lt;STRONG&gt;Is the above configuration correct? If not, may you please show the correct configuration?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2. The outside interface IP-address is used as egress IP for many LAN device translations. &lt;STRONG&gt;Does the ASA actually use a NAT overload technology here?&lt;/STRONG&gt;-- When the LAN tunneling device communication exist the ASA egress interface, does ths ASA map a unique port to this specific traffic, so that the return traffic will route to the specific LAN IP-address of the initiating device?&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Thu, 06 Apr 2023 18:54:38 GMT</pubDate>
    <dc:creator>MicJameson1</dc:creator>
    <dc:date>2023-04-06T18:54:38Z</dc:date>
    <item>
      <title>ASA NAT config architecture, syntax...(?)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809709#M1099312</link>
      <description>&lt;P&gt;&lt;U&gt;GOAL:&lt;/U&gt; Configure NAT in ASA (OS version 9.x) so that two LAN VPN devices can erect tunnels to one remote www VPN endpoint.&lt;/P&gt;&lt;P&gt;&lt;U&gt;GIVEN:&lt;/U&gt; ASA Outside interface= 1.1.1.1 , remote www VPN endpoint= 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;U&gt;CONFIGURATION:&lt;/U&gt;&lt;BR /&gt;object network VPN-DEVICES-LOCAL&lt;BR /&gt;ip address 172.16.2.2 255.255.255.255&lt;BR /&gt;ip address 172.16.9.2 255.255.255.255&lt;/P&gt;&lt;P&gt;nat (Inside,Outside) source static VPN-DEVICES-LOCAL 1.1.1.1 destination static 2.2.2.2 2.2.2.2&lt;/P&gt;&lt;P&gt;&lt;U&gt;QUESTIONS:&lt;/U&gt;&lt;BR /&gt;1. &lt;STRONG&gt;Is the above configuration correct? If not, may you please show the correct configuration?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2. The outside interface IP-address is used as egress IP for many LAN device translations. &lt;STRONG&gt;Does the ASA actually use a NAT overload technology here?&lt;/STRONG&gt;-- When the LAN tunneling device communication exist the ASA egress interface, does ths ASA map a unique port to this specific traffic, so that the return traffic will route to the specific LAN IP-address of the initiating device?&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 18:54:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809709#M1099312</guid>
      <dc:creator>MicJameson1</dc:creator>
      <dc:date>2023-04-06T18:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT config architecture, syntax...(?)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809711#M1099313</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1443661"&gt;@MicJameson1&lt;/a&gt; if 1.1.1.1 is the outside interface IP address and you want that to be the translated address you must use "interface" in the NAT configuration.&lt;/P&gt;
&lt;P&gt;nat (Inside,Outside) source dynamic VPN-DEVICES-LOCAL &lt;STRONG&gt;interface&lt;/STRONG&gt; destination static 2.2.2.2 2.2.2.2&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 19:29:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809711#M1099313</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-04-06T19:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT config architecture, syntax...(?)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809719#M1099315</link>
      <description>&lt;P&gt;Thank you Rob.&lt;/P&gt;&lt;P&gt;May you please answer...&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. The outside interface is used as egress IP for many LAN device translations.&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Does the ASA actually use a NAT overload technology here?&lt;/STRONG&gt;&lt;SPAN&gt;-- When the LAN tunneling device communication exist the ASA egress interface, does ths ASA map a unique port to this specific traffic, so that the return traffic will route to the specific LAN IP-address of the initiating device?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 19:25:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809719#M1099315</guid>
      <dc:creator>MicJameson1</dc:creator>
      <dc:date>2023-04-06T19:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT config architecture, syntax...(?)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809726#M1099317</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1443661"&gt;@MicJameson1&lt;/a&gt; yes, it uses PAT hiding the real IP address behind the outside IP address of the ASA, return traffic will route to the specific IP address of the initiating device.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 19:33:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809726#M1099317</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-04-06T19:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT config architecture, syntax...(?)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809731#M1099318</link>
      <description>&lt;P&gt;Hello Rob.&lt;/P&gt;&lt;P&gt;&lt;U&gt;GIVEN:&lt;/U&gt;&lt;SPAN&gt;&amp;nbsp;ASA Outside interface= 1.1.1.1 , remote www VPN endpoint= 2.2.2.2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I just noticed you swapped out "static" to "dynamic"...&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;"nat (Inside,Outside) source dynamic VPN-DEVICES-LOCAL&amp;nbsp;&lt;FONT color="#FF0000"&gt;interface&lt;/FONT&gt;&amp;nbsp;destination static 2.2.2.2 2.2.2.2"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For a while I have been confused with ASA logic vs Cisco IOS. I thought the ASA used the word "static" for NAT overload.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;QUESTIONS:&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;In your config, does "&lt;FONT color="#FF0000"&gt;interface&lt;/FONT&gt;" tell the ASA to use 1.1.1.1 for the outgoing source address?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Does this config make sense for the intent: 2 local devices erect a permanent VPN to a www remote VPN endpoint?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 19:46:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809731#M1099318</guid>
      <dc:creator>MicJameson1</dc:creator>
      <dc:date>2023-04-06T19:46:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT config architecture, syntax...(?)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809734#M1099319</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1443661"&gt;@MicJameson1&lt;/a&gt; "interface" tells the ASA to use the egress interface IP address.&lt;/P&gt;
&lt;P&gt;FYI, NAT logic is as follows:-&lt;/P&gt;
&lt;P&gt;nat (SRCINT,DSTINT) source dynamic|static REAL-SRC TRANSLATED-SRC destination static REAL-DST TRANSLATED-DST&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 19:47:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-config-architecture-syntax/m-p/4809734#M1099319</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-04-06T19:47:31Z</dc:date>
    </item>
  </channel>
</rss>

