<?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: dmz in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882380#M457465</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;journiforss,&amp;nbsp; both the inside and dmz are interfaces on the ASA,&amp;nbsp; no routing is necessary right (as long as using version 8.43 or later)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Apr 2012 17:26:51 GMT</pubDate>
    <dc:creator>llamaw0rksE</dc:creator>
    <dc:date>2012-04-03T17:26:51Z</dc:date>
    <item>
      <title>dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882377#M457462</link>
      <description>&lt;P&gt;Server on dmz with private ip 10.10.10.10 mapped with ip 172.20.1.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static(dmz,inside) 172.20.1.10 10.10.10.10 mask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it inside users are going to access machine on&amp;nbsp; dmz through outside interface ?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:49:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882377#M457462</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2019-03-11T22:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882378#M457463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your INSIDE host can/will access the DMZ host with the IP address 172.20.1.10 from the INSIDE interface (provided you got the route for it OR default route points towards ASA which probably is the case)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside interface has nothing to do with the above configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDIT: Had written DMZ instead of INSIDE at the start of the sentence.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2012 08:13:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882378#M457463</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-04-03T08:13:07Z</dc:date>
    </item>
    <item>
      <title>dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882379#M457464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What interface is 172.20.1.10 on? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If 172.20.1.10 is on the INSIDE interface, then any client requesting 172.20.1.10 coming into the firewall from the INSIDE interface would be able to hit the private IP (As long as ACL's allow it).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If 10.10.10.10 send data to the INSIDE, it will get converted to 172.20.1.10, but will not if it goes out another interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scape&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2012 17:14:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882379#M457464</guid>
      <dc:creator>goatnetworking</dc:creator>
      <dc:date>2012-04-03T17:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882380#M457465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;journiforss,&amp;nbsp; both the inside and dmz are interfaces on the ASA,&amp;nbsp; no routing is necessary right (as long as using version 8.43 or later)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2012 17:26:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882380#M457465</guid>
      <dc:creator>llamaw0rksE</dc:creator>
      <dc:date>2012-04-03T17:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882381#M457466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Prashant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As your nat says (DMZ,INSIDE) those 2 interfaces are the only ones involved on the communication from an inside host to the DMZ server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That being said let me know if you need something else.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do rate all the helpful posts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Apr 2012 18:03:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882381#M457466</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-04-03T18:03:17Z</dc:date>
    </item>
    <item>
      <title>dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882382#M457467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it inside users can access the dmz server with mapped address?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 07:05:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882382#M457467</guid>
      <dc:creator>prashantrecon</dc:creator>
      <dc:date>2012-04-04T07:05:47Z</dc:date>
    </item>
    <item>
      <title>Re: dmz</title>
      <link>https://community.cisco.com/t5/network-security/dmz/m-p/1882383#M457468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the NAT command you mentioned in the original post&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static(dmz,inside) 172.20.1.10 10.10.10.10 mask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can access the DMZ server 10.10.10.10 from your INSIDE network with the mapped address of 172.20.1.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 07:09:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz/m-p/1882383#M457468</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-04-04T07:09:20Z</dc:date>
    </item>
  </channel>
</rss>

