<?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 IP which only allowed for PAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ip-which-only-allowed-for-pat/m-p/2650339#M201571</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking for example which allow some of the IP's belongs to INSIDE which can allow to using PAT method to access Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With reference to URL&lt;BR /&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa90/configuration/guide/asa_90_cli_config/nat_objects.html#pgfId-1455942" target="_blank"&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa90/configuration/guide/asa_90_cli_config/nat_objects.html#pgfId-1455942&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is talking about the whole 192.168.2.0/24 subnet.&lt;/P&gt;&lt;P&gt;-------&lt;/P&gt;&lt;P&gt;The following example configures dynamic PAT that hides the 192.168.2.0 network behind the outside interface address:&lt;/P&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;SPAN&gt;hostname(config)# &lt;B class="cBold"&gt;object network my-inside-net&lt;/B&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;SPAN&gt;hostname(config-network-object)# &lt;B class="cBold"&gt;subnet 192.168.2.0 255.255.255.0&lt;/B&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;SPAN&gt;hostname(config-network-object)# &lt;B class="cBold"&gt;nat (inside,outside) dynamic interface&lt;/B&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;-------&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;I would like to check how should config if only allow parts of IP belongs to 192.168.2.0/24 can be PAT to internet and others will deny.&amp;nbsp; Should be need create additional ACL?&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;Thanks!&lt;/DIV&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:34:11 GMT</pubDate>
    <dc:creator>Machi Ma</dc:creator>
    <dc:date>2019-03-12T05:34:11Z</dc:date>
    <item>
      <title>IP which only allowed for PAT</title>
      <link>https://community.cisco.com/t5/network-security/ip-which-only-allowed-for-pat/m-p/2650339#M201571</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am looking for example which allow some of the IP's belongs to INSIDE which can allow to using PAT method to access Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With reference to URL&lt;BR /&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa90/configuration/guide/asa_90_cli_config/nat_objects.html#pgfId-1455942" target="_blank"&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa90/configuration/guide/asa_90_cli_config/nat_objects.html#pgfId-1455942&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is talking about the whole 192.168.2.0/24 subnet.&lt;/P&gt;&lt;P&gt;-------&lt;/P&gt;&lt;P&gt;The following example configures dynamic PAT that hides the 192.168.2.0 network behind the outside interface address:&lt;/P&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;SPAN&gt;hostname(config)# &lt;B class="cBold"&gt;object network my-inside-net&lt;/B&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;SPAN&gt;hostname(config-network-object)# &lt;B class="cBold"&gt;subnet 192.168.2.0 255.255.255.0&lt;/B&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&lt;SPAN&gt;hostname(config-network-object)# &lt;B class="cBold"&gt;nat (inside,outside) dynamic interface&lt;/B&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;-------&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;I would like to check how should config if only allow parts of IP belongs to 192.168.2.0/24 can be PAT to internet and others will deny.&amp;nbsp; Should be need create additional ACL?&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="pEx1_Example1"&gt;Thanks!&lt;/DIV&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:34:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-which-only-allowed-for-pat/m-p/2650339#M201571</guid>
      <dc:creator>Machi Ma</dc:creator>
      <dc:date>2019-03-12T05:34:11Z</dc:date>
    </item>
    <item>
      <title>Hi, You might be better of</title>
      <link>https://community.cisco.com/t5/network-security/ip-which-only-allowed-for-pat/m-p/2650340#M201572</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You might be better of limitin the mentioned hosts from connecting to the Internet in the interface ACL rather than making a special NAT configuration that determines if a host can connect to the Internet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want to control which host gets NATed then you could use the Manual NAT / Twice NAT configuration instead of the above Auto NAT / Network Object NAT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example could look something like this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object-group network PAT-SOURCE-HOSTS&lt;BR /&gt;&amp;nbsp;network-object host &amp;lt;host1 ip&amp;gt;&lt;BR /&gt;&amp;nbsp;network-object host &amp;lt;host2 ip&amp;gt;&lt;BR /&gt;&amp;nbsp;network-object host &amp;lt;host3 ip&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (inside,outside) after-auto source dynamic PAT-SOURCE-HOSTS interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can then add the addresses directly under the &lt;STRONG&gt;"object-group" &lt;/STRONG&gt;or remove them when needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could naturally use small subnets instead of the host addresses in the above example if all the users are from a certain range of the subnet you mentioned. You will also have to make sure that there is no other NAT configuration on your ASA that would apply to the users.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above Manual NAT / Twice NAT is at the lowest Section 3 (priority of NAT configuration) because it has &lt;STRONG&gt;"after-auto" &lt;/STRONG&gt;as a part of the &lt;STRONG&gt;"nat"&lt;/STRONG&gt; command.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;</description>
      <pubDate>Fri, 27 Feb 2015 08:13:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-which-only-allowed-for-pat/m-p/2650340#M201572</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2015-02-27T08:13:57Z</dc:date>
    </item>
  </channel>
</rss>

