<?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: NAT RESERVATION in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303471#M828270</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jon.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Aug 2009 06:18:09 GMT</pubDate>
    <dc:creator>kolawole1</dc:creator>
    <dc:date>2009-08-14T06:18:09Z</dc:date>
    <item>
      <title>NAT RESERVATION</title>
      <link>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303469#M828197</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;A windows server is connected to a modem and has a public ip address. 2 others public ip addresses are reserved on the server (but not assigned to physical interfaces)such that these addresses are translated into private addresses on other servers on the lan.  &lt;/P&gt;&lt;P&gt;Is there a feature on ASA5520 that could make a nat translation on public ip addresses not assigned to the asa physical interfaces but dynamicaly kept in the config file and be able to do nat?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:05:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303469#M828197</guid>
      <dc:creator>kolawole1</dc:creator>
      <dc:date>2019-03-11T16:05:56Z</dc:date>
    </item>
    <item>
      <title>Re: NAT RESERVATION</title>
      <link>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303470#M828249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, absolutely an ASA can do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 195.177.10.1 192.168.5.1 netmask 2555.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;would present a server with a real address of 192.168.5.1 on the inside to the outside with an address of 195.177.10.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 195.177.10.1 address does not need to be assigned to any of the ASA physical interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Aug 2009 18:48:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303470#M828249</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2009-08-13T18:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: NAT RESERVATION</title>
      <link>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303471#M828270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jon.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2009 06:18:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-reservation/m-p/1303471#M828270</guid>
      <dc:creator>kolawole1</dc:creator>
      <dc:date>2009-08-14T06:18:09Z</dc:date>
    </item>
  </channel>
</rss>

