<?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 You are right, the in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/static-pat-problem/m-p/2614773#M197078</link>
    <description>&lt;P&gt;You are right, the documentation is misleading.&lt;/P&gt;&lt;P&gt;When it says an acl is needed for static PAT I think it means for static policy PAT because if you then look at the examples static PAT does not use an acl.&lt;/P&gt;&lt;P&gt;Your configuration should work as I have used that many times before.&lt;/P&gt;&lt;P&gt;Can you post your full configuration removing any sensitive information.&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
    <pubDate>Sat, 14 Feb 2015 11:27:42 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2015-02-14T11:27:42Z</dc:date>
    <item>
      <title>Static PAT problem</title>
      <link>https://community.cisco.com/t5/network-security/static-pat-problem/m-p/2614772#M197077</link>
      <description>&lt;P&gt;I'm totally confused by Cisco documentation regarding Static PAT, as I can see mapping for certain hosts from outside global to the inside local.&lt;/P&gt;&lt;P&gt;All I want to Apply is using one public IP address and using Static PAT as below&lt;/P&gt;&lt;P&gt;static (DMZ,outside) tcp 195.21.40.133 smtp 192.168.50.10&amp;nbsp;smtp netmask 255.255.255.255&lt;BR /&gt;static (DMZ,outside) tcp 195.21.40.133 https 192.168.50.13 https netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;Using the above config when testing SMTP server, I found that traffic going out is not using the IP address 195.21.40.133 rather it is using the outside interface ip 195.21.40.132.&lt;/P&gt;&lt;P&gt;According to Cisco's documentation there's an ACL &amp;nbsp;prerequisite for Static PAT. I didn't understand that well.&lt;/P&gt;&lt;P&gt;I hope someone can better describe the static PAT, specially in my scenario.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:30:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-pat-problem/m-p/2614772#M197077</guid>
      <dc:creator>Rahmat Ullah</dc:creator>
      <dc:date>2019-03-12T05:30:02Z</dc:date>
    </item>
    <item>
      <title>You are right, the</title>
      <link>https://community.cisco.com/t5/network-security/static-pat-problem/m-p/2614773#M197078</link>
      <description>&lt;P&gt;You are right, the documentation is misleading.&lt;/P&gt;&lt;P&gt;When it says an acl is needed for static PAT I think it means for static policy PAT because if you then look at the examples static PAT does not use an acl.&lt;/P&gt;&lt;P&gt;Your configuration should work as I have used that many times before.&lt;/P&gt;&lt;P&gt;Can you post your full configuration removing any sensitive information.&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Sat, 14 Feb 2015 11:27:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/static-pat-problem/m-p/2614773#M197078</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2015-02-14T11:27:42Z</dc:date>
    </item>
  </channel>
</rss>

