<?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/overload from outside to inside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843374#M973536</link>
    <description>&lt;P&gt;I have host using a private internal IP that will only talk to machines on the same private IP.  I need to have public IPs talk to this machine.  I have a PIX that uses the same private IP subnet on its inside interface.  What I would like to do is a PAT/overload scenario in reverse where multiple outside hosts will talk to the inside host using one IP from the private subnet.  I think I have seen this mentioned somewhere but can't find it.  One caveat is that the PIX must also do PAT/overload for internal hosts going out to the Internet at the same time.  Is this possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Diego&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 11:26:13 GMT</pubDate>
    <dc:creator>tato386</dc:creator>
    <dc:date>2019-03-11T11:26:13Z</dc:date>
    <item>
      <title>PAT/overload from outside to inside</title>
      <link>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843374#M973536</link>
      <description>&lt;P&gt;I have host using a private internal IP that will only talk to machines on the same private IP.  I need to have public IPs talk to this machine.  I have a PIX that uses the same private IP subnet on its inside interface.  What I would like to do is a PAT/overload scenario in reverse where multiple outside hosts will talk to the inside host using one IP from the private subnet.  I think I have seen this mentioned somewhere but can't find it.  One caveat is that the PIX must also do PAT/overload for internal hosts going out to the Internet at the same time.  Is this possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Diego&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:26:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843374#M973536</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2019-03-11T11:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: PAT/overload from outside to inside</title>
      <link>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843375#M973537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Diego,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can do this with static, NAT and ACL to address both requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's a configuration example that you can use to build your configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside Web Host that needs to be accessed from Outside: 192.168.1.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int e0&lt;/P&gt;&lt;P&gt;nameif outside&lt;/P&gt;&lt;P&gt;security-level 0&lt;/P&gt;&lt;P&gt;ip add 172.16.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;int e1&lt;/P&gt;&lt;P&gt;nameif inside&lt;/P&gt;&lt;P&gt;security-level 100&lt;/P&gt;&lt;P&gt;ip add 192.168.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group acl_outside in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_outside permit tcp any host 172.16.1.1 eq www&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 1 192.168.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) interface 192.168.1.2 tcp 80&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;Sundar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Oct 2007 22:47:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843375#M973537</guid>
      <dc:creator>sundar.palaniappan</dc:creator>
      <dc:date>2007-10-16T22:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: PAT/overload from outside to inside</title>
      <link>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843376#M973538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Diego&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sundar has covered most of this but to PAT all outside addresses &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list PATIN permit ip any host 172.16.1.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Note, i'm using Sundar's IP addressing and you might want to tie access down to the particular tcp/udp ports)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (outside) 2 access-list PATIN outside&lt;/P&gt;&lt;P&gt;global (inside) 2 interface&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;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Oct 2007 02:41:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843376#M973538</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-10-17T02:41:36Z</dc:date>
    </item>
    <item>
      <title>Re: PAT/overload from outside to inside</title>
      <link>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843377#M973539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks guys.  I will give this a shot and let you know what happens. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Oct 2007 15:25:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pat-overload-from-outside-to-inside/m-p/843377#M973539</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2007-10-18T15:25:04Z</dc:date>
    </item>
  </channel>
</rss>

