<?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: nat (any,outside) static interface? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873471#M6045</link>
    <description>&lt;P&gt;object network natted_Subnet&lt;/P&gt;&lt;P&gt;subnet 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (&lt;STRONG&gt;any&lt;/STRONG&gt;,outside) static interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;long ago i read in cisco documentation nat (any,outside) is not a best practice. would be better if you put tight control on the flow of traffic either from (inside,outside) or (dmz,outside) instead of any,outside.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you better do a dynamic PAT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;object network natted_Subnet&lt;/P&gt;&lt;P&gt;subnet 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (any,outside) dynamic interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 15 Jun 2019 07:16:43 GMT</pubDate>
    <dc:creator>Sheraz.Salim</dc:creator>
    <dc:date>2019-06-15T07:16:43Z</dc:date>
    <item>
      <title>nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3872812#M6026</link>
      <description>&lt;P&gt;I am trying to confirm that the following means nat the object source from any interface to OUTSIDE interface IP as I can't find this config in any docs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;object network natted_Subnet&lt;/P&gt;&lt;P&gt;subnet 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (any,outside) static interface&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:13:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3872812#M6026</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2020-02-21T17:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3872819#M6030</link>
      <description>&lt;P&gt;That would not be a recommended configuration since you need to use dynamic (PAT) rather than static NAT when mapping many-to-one.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jun 2019 02:57:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3872819#M6030</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-06-14T02:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3872834#M6031</link>
      <description>My Friend,&lt;BR /&gt;You should use the NAT overload or PAT for the ease of dynamic handling of ports in the translation, see the following examples:&lt;BR /&gt;&lt;A href="https://www.certificationkits.com/cisco-certification/ccna-articles/cisco-ccna-network-address-translation-nat/static-nat-dynamic-nat-nat-overload-pat-a-configurations/" target="_blank"&gt;https://www.certificationkits.com/cisco-certification/ccna-articles/cisco-ccna-network-address-translation-nat/static-nat-dynamic-nat-nat-overload-pat-a-configurations/&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Jun 2019 04:34:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3872834#M6031</guid>
      <dc:creator>Edwin Portillo</dc:creator>
      <dc:date>2019-06-14T04:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873422#M6036</link>
      <description>&lt;P&gt;This would be correct then on an ASA for let's say internal servers that need to be access from the Outside right?&lt;BR /&gt;&lt;BR /&gt;nat (insde,outside) dynamic (interface or mapped IP address) service tcp 3889 3889&lt;BR /&gt;access-list Outside-IN extended permit tcp any host (real IP) eq 3389&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 01:01:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873422#M6036</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2019-06-15T01:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873423#M6040</link>
      <description>&lt;P&gt;This would be correct then on an ASA for let's say internal servers that need to be access from the Outside but just NATTING them to 1 IP or the Outside interface right?&lt;BR /&gt;&lt;BR /&gt;nat (insde,outside) dynamic (interface or mapped IP address) service tcp 3889 3889&lt;BR /&gt;access-list Outside-IN extended permit tcp any host (real IP) eq 3389&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 01:02:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873423#M6040</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2019-06-15T01:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873432#M6042</link>
      <description>&lt;P&gt;Now that you've added the port 3389 (rdp) your use case changes. You want a static port forwarding NAT rule:&lt;/P&gt;
&lt;PRE&gt;nat (inside,outside) static (interface or mapped IP address) service tcp 3889 3889&lt;/PRE&gt;
&lt;P&gt;See&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/118996-config-asa-00.html#anc10" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/118996-config-asa-00.html#anc10&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 03:07:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873432#M6042</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-06-15T03:07:54Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873471#M6045</link>
      <description>&lt;P&gt;object network natted_Subnet&lt;/P&gt;&lt;P&gt;subnet 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (&lt;STRONG&gt;any&lt;/STRONG&gt;,outside) static interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;long ago i read in cisco documentation nat (any,outside) is not a best practice. would be better if you put tight control on the flow of traffic either from (inside,outside) or (dmz,outside) instead of any,outside.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you better do a dynamic PAT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;object network natted_Subnet&lt;/P&gt;&lt;P&gt;subnet 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (any,outside) dynamic interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 07:16:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873471#M6045</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-06-15T07:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873553#M6047</link>
      <description>&lt;P&gt;Having trouble knowing when would I really know to use "Static" vs "Dynamic"?&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 16:44:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873553#M6047</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2019-06-15T16:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873554#M6049</link>
      <description>&lt;P&gt;When would I really know to use "Static" vs "Dynamic"?&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 16:43:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873554#M6049</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2019-06-15T16:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873586#M6051</link>
      <description>&lt;P&gt;have a read on this doc &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa90/configuration/guide/asa_90_cli_config/nat_objects.html&amp;nbsp;&amp;nbsp;" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa90/configuration/guide/asa_90_cli_config/nat_objects.html&amp;nbsp;&amp;nbsp;&lt;/A&gt; will clear all your concepts&lt;/P&gt;</description>
      <pubDate>Sat, 15 Jun 2019 18:28:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3873586#M6051</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-06-15T18:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: nat (any,outside) static interface?</title>
      <link>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3878016#M6052</link>
      <description>Friend,&lt;BR /&gt;&lt;BR /&gt;Static NAT is used to do a one-to-one mapping between an inside address and an outside address. Static NAT also allows connections from an outside host to an inside host. Usually, static NAT is used for servers inside your network. For example, you may have a web server with the inside IP address 192.168.0.10 and you want it to be accessible when a remote host makes a request to 209.165.200.10. For this to work, you must do a static NAT mapping between those to IPs. In this example, we will use the FastEthernet 0/1 as the inside NAT interface, the interface connecting to our network, and the Serial 0/0/0 interface as the outside NAT interface, the one connecting to our service provide.&lt;BR /&gt;Example:&lt;BR /&gt;Ip nat inside source static 192.168.0.10 209.165.200.10&lt;BR /&gt;&lt;BR /&gt;Interface FastEthernet 0/1&lt;BR /&gt;ip nat inside&lt;BR /&gt;Interface Serial 0/0/0&lt;BR /&gt;ip nat outside&lt;BR /&gt;&lt;BR /&gt;Dynamic NAT is used when you have a “pool” of public IP addresses that you want to assign to your internal hosts dynamically. Don’t use dynamic NAT for servers or other devices that need to be accessible from the Internet.&lt;BR /&gt;Example:&lt;BR /&gt;ip nat pool NAT-POOL 209.165.200.226 209.165.200.240 netmask 255.255.255.224&lt;BR /&gt;&lt;BR /&gt;Access-list 1 permit 192.168.0.0 0.255.255.255&lt;BR /&gt;&lt;BR /&gt;Ip nat inside source list 1 pool NAT-POOL&lt;BR /&gt;&lt;BR /&gt;Interface FastEthernet 0/1&lt;BR /&gt;Ip nat inside&lt;BR /&gt;Interface Serial 0/0/0&lt;BR /&gt;ip nat outside&lt;BR /&gt;</description>
      <pubDate>Sun, 23 Jun 2019 03:55:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-any-outside-static-interface/m-p/3878016#M6052</guid>
      <dc:creator>Edwin Portillo</dc:creator>
      <dc:date>2019-06-23T03:55:51Z</dc:date>
    </item>
  </channel>
</rss>

