<?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 Regular Dynamic PAT statements in ASA 8.3. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/regular-dynamic-pat-statements-in-asa-8-3/m-p/1855076#M459107</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;object network INSIDE_10.6&lt;/P&gt;&lt;P&gt;nat (inside,outside) dynamic PAT&lt;/P&gt;&lt;P&gt;object network INSIDE_192.168&lt;/P&gt;&lt;P&gt;nat (inside,outside) dynamic PAT&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use the ingress and egress interface name instead of any any or atleast define the name of the ingress interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now if you only define the name of the ingress interface any traffic that is coming from the specified source will follow this nat rule for going out all the interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best way to do it is to specifiy the ingress and egress both the interfaces in the nat rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now to your second question you can use the same public IP object group (PAT) for both inside networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also configure the routes accordingly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Feb 2012 14:53:42 GMT</pubDate>
    <dc:creator>Amit Rai</dc:creator>
    <dc:date>2012-02-20T14:53:42Z</dc:date>
    <item>
      <title>Regular Dynamic PAT statements in ASA 8.3.</title>
      <link>https://community.cisco.com/t5/network-security/regular-dynamic-pat-statements-in-asa-8-3/m-p/1855075#M459104</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please verify this configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 inside networks:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network INSIDE_10.6&lt;/P&gt;&lt;P&gt;subnet 10.6.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network INSIDE_192.168&lt;/P&gt;&lt;P&gt;subnet 192.168.0.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I grouped these 2 into 1 object-group:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object-group network INSIDE&lt;/P&gt;&lt;P&gt;network-object object INSIDE_10.6&lt;/P&gt;&lt;P&gt;network-object object INSIDE_192.168&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Public IP address used for PAT:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network PAT&lt;/P&gt;&lt;P&gt;host 152.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used the following statement to create Dynamic PAT to public IP address:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network INSIDE_10.6&lt;/P&gt;&lt;P&gt;nat (any,any) dynamic PAT&lt;/P&gt;&lt;P&gt;object network INSIDE_192.168&lt;/P&gt;&lt;P&gt;nat (any,any) dynamic PAT&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that correct?&lt;/P&gt;&lt;P&gt;Also I'm using one public address to PAT both inside networks. Is there any advantage of using 2 different ones, so each inside network would be PAT to its own address?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;forman&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:32:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/regular-dynamic-pat-statements-in-asa-8-3/m-p/1855075#M459104</guid>
      <dc:creator>forman102</dc:creator>
      <dc:date>2019-03-11T22:32:30Z</dc:date>
    </item>
    <item>
      <title>Regular Dynamic PAT statements in ASA 8.3.</title>
      <link>https://community.cisco.com/t5/network-security/regular-dynamic-pat-statements-in-asa-8-3/m-p/1855076#M459107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;object network INSIDE_10.6&lt;/P&gt;&lt;P&gt;nat (inside,outside) dynamic PAT&lt;/P&gt;&lt;P&gt;object network INSIDE_192.168&lt;/P&gt;&lt;P&gt;nat (inside,outside) dynamic PAT&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use the ingress and egress interface name instead of any any or atleast define the name of the ingress interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now if you only define the name of the ingress interface any traffic that is coming from the specified source will follow this nat rule for going out all the interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best way to do it is to specifiy the ingress and egress both the interfaces in the nat rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now to your second question you can use the same public IP object group (PAT) for both inside networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also configure the routes accordingly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Feb 2012 14:53:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/regular-dynamic-pat-statements-in-asa-8-3/m-p/1855076#M459107</guid>
      <dc:creator>Amit Rai</dc:creator>
      <dc:date>2012-02-20T14:53:42Z</dc:date>
    </item>
  </channel>
</rss>

