<?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 PAT with Pool in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256959#M357837</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The first inside user takes 88.88.88.1, second takes 88.88.88.2 and so on and when the last ip address 88.88.88.254 is taken, no more inside hosts will be able to go outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, essentially, it will be one to one mapping and not PAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To effectively use PAT, we can do following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 10 88.88.88.1 - 88.88.88.253&lt;/P&gt;&lt;P&gt;global (outside) 10 88.88.88.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First the pool will be exhausted and then all the inside users are patted on 88.88.88.254 and 65535 such xlates on this ip would be possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AJ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 May 2013 03:17:59 GMT</pubDate>
    <dc:creator>Ajay Saini</dc:creator>
    <dc:date>2013-05-01T03:17:59Z</dc:date>
    <item>
      <title>PAT with Pool</title>
      <link>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256957#M357833</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are having an ASA running on 8.2&lt;/P&gt;&lt;P&gt;We are planning for natting three /16 subnets with one /24 public IP pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 10 88.88.88.1 - 88.88.88.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 10 172.16.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;﻿&lt;/P&gt;&lt;P&gt;﻿nat (inside) 10 172.17.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 10 172.18.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so when the traffic comes from inside the first nat will happen with public IP 88.88.88.1&lt;/P&gt;&lt;P&gt;we need to know how and when the natting will happen with next public IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can we control the threshold ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mohamed Shafeer&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:36:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256957#M357833</guid>
      <dc:creator>Mohamed Shafeer Kunhu</dc:creator>
      <dc:date>2019-03-12T01:36:41Z</dc:date>
    </item>
    <item>
      <title>PAT with Pool</title>
      <link>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256958#M357835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;depending on the code version it will not necessarily take the second IP in the pool.&lt;/P&gt;&lt;P&gt;when another host needs to be natted then it will take another IP and the translations timeout after 3 hours by default if I'm not mistaken but you can modify this with the&amp;nbsp; timeout xlate command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget to rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2013 09:58:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256958#M357835</guid>
      <dc:creator>cadet alain</dc:creator>
      <dc:date>2013-04-30T09:58:21Z</dc:date>
    </item>
    <item>
      <title>PAT with Pool</title>
      <link>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256959#M357837</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The first inside user takes 88.88.88.1, second takes 88.88.88.2 and so on and when the last ip address 88.88.88.254 is taken, no more inside hosts will be able to go outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, essentially, it will be one to one mapping and not PAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To effectively use PAT, we can do following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 10 88.88.88.1 - 88.88.88.253&lt;/P&gt;&lt;P&gt;global (outside) 10 88.88.88.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First the pool will be exhausted and then all the inside users are patted on 88.88.88.254 and 65535 such xlates on this ip would be possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AJ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 May 2013 03:17:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-with-pool/m-p/2256959#M357837</guid>
      <dc:creator>Ajay Saini</dc:creator>
      <dc:date>2013-05-01T03:17:59Z</dc:date>
    </item>
  </channel>
</rss>

