<?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 Re: outside NAT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445166#M698221</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Don,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;I'm not sure if this approach is supported but I've used something like this in the past when migrating external addresses; proceed at your own risk.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;access-list tango permit ip any host 192.168.10.1 any&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;static (dmz,outside) 203.x.x.10 192.168.10.1&lt;BR /&gt;static (dmz,outside) 203.x.x.11 access-list tango&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Chris&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 20 Jun 2010 15:40:04 GMT</pubDate>
    <dc:creator>gatlin007</dc:creator>
    <dc:date>2010-06-20T15:40:04Z</dc:date>
    <item>
      <title>outside NAT</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445163#M698214</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do i configure outside NAT such that my external public ip is map to one of my&amp;nbsp; dmz private ip.&lt;/P&gt;&lt;P&gt;What i want is when any address on the internet connects to my public ip on a certain port it will translate to my dmz ip which my server is using.&lt;/P&gt;&lt;P&gt;I am using asdm to configure my cisco asa 5510 firewall. I did a NAT for my source public ip to be translated to my dmz ip. I then set an accesslist to allow any incoming ip on a specific port to access the public ip i configure for outside NAT. But it didnt work. Pls advise. Thks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:01:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445163#M698214</guid>
      <dc:creator>donnie</dc:creator>
      <dc:date>2019-03-11T18:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: outside NAT</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445164#M698215</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;With CLI&lt;/STRONG&gt;&lt;/SPAN&gt;:&lt;/P&gt;&lt;P&gt;static (DMZ,outside) &lt;EXTERNAL-PUBLIC-IP&gt; &lt;DMZ-PRIVATE-IP&gt; netmask 255.255.255.255&lt;/DMZ-PRIVATE-IP&gt;&lt;/EXTERNAL-PUBLIC-IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;With ASDM&lt;/STRONG&gt;&lt;/SPAN&gt;:&lt;/P&gt;&lt;P&gt;Configuration --&amp;gt; Firewall --&amp;gt; NAT Rules --&amp;gt; Add Static NAT rule --&amp;gt;&lt;/P&gt;&lt;P&gt;Original interface: DMZ&lt;/P&gt;&lt;P&gt;Source: dmz-private-ip&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Translated interface: outside&lt;/P&gt;&lt;P&gt;Use IP Address: external-public-ip&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then click: OK, and apply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-list applied on the outside interface should allow traffic from "any" towards the external public ip on certain tcp/udp ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jun 2010 12:31:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445164#M698215</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-06-18T12:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: outside NAT</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445165#M698218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Halijenn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thk you for your prompt response. I know of the steps required for NAT stated in your reply. What i am looking for is when any internet ip access my public ip eg 203.x.x.10 and 203.x.x.11 it will automatically translate to my 1 private ip eg 192.168.10.1. We use to have 2 private ip(192.168.10.1, 192.168.10.2) translate to the 2 public ip stated above, but we have merge the 2 servers into 1.&lt;/P&gt;&lt;P&gt;We would like to continue to use the 2 public ip so that it is a transparent transition for our external customers. Thks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Jun 2010 05:13:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445165#M698218</guid>
      <dc:creator>donnie</dc:creator>
      <dc:date>2010-06-20T05:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: outside NAT</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445166#M698221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Don,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;I'm not sure if this approach is supported but I've used something like this in the past when migrating external addresses; proceed at your own risk.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;access-list tango permit ip any host 192.168.10.1 any&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;static (dmz,outside) 203.x.x.10 192.168.10.1&lt;BR /&gt;static (dmz,outside) 203.x.x.11 access-list tango&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Chris&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Jun 2010 15:40:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445166#M698221</guid>
      <dc:creator>gatlin007</dc:creator>
      <dc:date>2010-06-20T15:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: outside NAT</title>
      <link>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445167#M698223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately you can't translate 2 public ip addresses to just 1 private ip address as it is not supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jun 2010 01:42:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outside-nat/m-p/1445167#M698223</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-06-21T01:42:17Z</dc:date>
    </item>
  </channel>
</rss>

