<?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 NAT example - Increased Security? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-example-increased-security/m-p/1567016#M602215</link>
    <description>&lt;P&gt;Came across an unusual example of NAT in an ASA recently, difficult to explain but it looked like it was doing a double NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E.g.&lt;/P&gt;&lt;P&gt;Outside IP 222.222.222.222&lt;BR /&gt;Mail server 192.168.1.10 (real IP)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In the config there were standard nat rules which translated the destination/outside IP to other IPs (one-many), however the IP it was translated to was for example 172.16.1.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There was then another nat rule which translated the whole subnet 172.16.1.x to 192.168.1.x, the access list obviously reflected access from the outside to the translated IP 172.16.1.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The guy which configured it seemed to make out it increased security as it masked the internal IP range, just wondered what other peoples opinions are as it seems pointless to me - the dst and source nat rules surely hide the internal ip scheme anyway??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advanced&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 18:47:52 GMT</pubDate>
    <dc:creator>ma77smith</dc:creator>
    <dc:date>2019-03-11T18:47:52Z</dc:date>
    <item>
      <title>NAT example - Increased Security?</title>
      <link>https://community.cisco.com/t5/network-security/nat-example-increased-security/m-p/1567016#M602215</link>
      <description>&lt;P&gt;Came across an unusual example of NAT in an ASA recently, difficult to explain but it looked like it was doing a double NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E.g.&lt;/P&gt;&lt;P&gt;Outside IP 222.222.222.222&lt;BR /&gt;Mail server 192.168.1.10 (real IP)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In the config there were standard nat rules which translated the destination/outside IP to other IPs (one-many), however the IP it was translated to was for example 172.16.1.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There was then another nat rule which translated the whole subnet 172.16.1.x to 192.168.1.x, the access list obviously reflected access from the outside to the translated IP 172.16.1.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The guy which configured it seemed to make out it increased security as it masked the internal IP range, just wondered what other peoples opinions are as it seems pointless to me - the dst and source nat rules surely hide the internal ip scheme anyway??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advanced&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:47:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-example-increased-security/m-p/1567016#M602215</guid>
      <dc:creator>ma77smith</dc:creator>
      <dc:date>2019-03-11T18:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: NAT example - Increased Security?</title>
      <link>https://community.cisco.com/t5/network-security/nat-example-increased-security/m-p/1567017#M602216</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's interesting. I want to reserve my comments unless i am able to have a look at the example in entirety. Please share the link for that. If it is indeed implementing double NAT, it does not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Prapanch&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Sep 2010 14:46:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-example-increased-security/m-p/1567017#M602216</guid>
      <dc:creator>praprama</dc:creator>
      <dc:date>2010-09-30T14:46:00Z</dc:date>
    </item>
  </channel>
</rss>

