<?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 ASA 8.6 nat reflection in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-8-6-nat-reflection/m-p/2233965#M349905</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a scenario where i need to enable nat reflection or understand how I can make this work on a ASA 55x5-x for a specific design of telepresence equipment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a equipment that sets inside the network, and its peer (or slave) that sits on the dmz to handle outside connections. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically i have to setup up a nat reflection scenario so that the inside appliance only registers to the dmz device using its public natted address and not the dmz address. I have tried to configure this using "same-security-traffic permit intra-interface", static nat for the outside interface which in turn performs an identity nat for the public addresses...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In turn I would like to hairpin this traffic on the outside interface and have it hit the dmz when sourced from the inside and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possbile on the 8.6 code? For anyone interested here is a link to the guide that explains this behavior:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Control_with_Expressway_Deployment_Guide_X7-2.pdf" target="_blank"&gt;http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Control_with_Expressway_Deployment_Guide_X7-2.pdf&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; (page 64)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:43:27 GMT</pubDate>
    <dc:creator>Tarik Admani</dc:creator>
    <dc:date>2019-03-12T01:43:27Z</dc:date>
    <item>
      <title>ASA 8.6 nat reflection</title>
      <link>https://community.cisco.com/t5/network-security/asa-8-6-nat-reflection/m-p/2233965#M349905</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a scenario where i need to enable nat reflection or understand how I can make this work on a ASA 55x5-x for a specific design of telepresence equipment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a equipment that sets inside the network, and its peer (or slave) that sits on the dmz to handle outside connections. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically i have to setup up a nat reflection scenario so that the inside appliance only registers to the dmz device using its public natted address and not the dmz address. I have tried to configure this using "same-security-traffic permit intra-interface", static nat for the outside interface which in turn performs an identity nat for the public addresses...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In turn I would like to hairpin this traffic on the outside interface and have it hit the dmz when sourced from the inside and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possbile on the 8.6 code? For anyone interested here is a link to the guide that explains this behavior:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Control_with_Expressway_Deployment_Guide_X7-2.pdf" target="_blank"&gt;http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Control_with_Expressway_Deployment_Guide_X7-2.pdf&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; (page 64)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:43:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-8-6-nat-reflection/m-p/2233965#M349905</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2019-03-12T01:43:27Z</dc:date>
    </item>
    <item>
      <title>ASA 8.6 nat reflection</title>
      <link>https://community.cisco.com/t5/network-security/asa-8-6-nat-reflection/m-p/2233966#M349906</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;Not really exactly sure of the setup here. I mean do I understand it correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On first glance it weems to me that you are just talking about NATing DMZ server to their public IP address towards BOTH the "outside" and the "inside"? That shouldnt be a problem to my understanding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Though in the above case I mention, there is really no hairpinning of traffic involved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would there be any chance you could clarify the situation. Perhaps even with a small picture of the network setup along with somekind of example IP addresses?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 May 2013 15:54:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-8-6-nat-reflection/m-p/2233966#M349906</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-17T15:54:26Z</dc:date>
    </item>
  </channel>
</rss>

