<?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 Hello.I tried several in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577687#M205227</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I tried several solutions that I found on internet and foruns but none worked.&lt;/P&gt;&lt;P&gt;I then tried this one and it worked:&lt;/P&gt;&lt;P&gt;nat (Inside,Inside) 2 source dynamic&amp;nbsp;LAN NAT-for-hairpinning destination static Interface-Outside ORION service HTTP HTTP&lt;/P&gt;&lt;P&gt;LAN - Is my inside Network (lets say 192.168.10.1)&lt;/P&gt;&lt;P&gt;NAT-for- hairpinning - IP address not used in organization and used exclusively to source nat my inside network (I used 172.16.0.1)&lt;/P&gt;&lt;P&gt;Interface-Outside - is a network object with IP address of outsider interface&lt;/P&gt;&lt;P&gt;ORION - is internal server (192.168.10.1) in same network na LAN&lt;/P&gt;&lt;P&gt;For me, using the NAT-for-hairpinning object was the only way to put it to work.&lt;/P&gt;&lt;P&gt;Hope this post can be helpfull.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;João.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S. - ASA has version 9.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Nov 2014 15:49:39 GMT</pubDate>
    <dc:creator>jcarvalh</dc:creator>
    <dc:date>2014-11-20T15:49:39Z</dc:date>
    <item>
      <title>hairpinning (cisco asa) to the same IP address</title>
      <link>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577685#M205225</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I have a client migrating to a Cisco ASA.&lt;/P&gt;&lt;P&gt;I have two interfaces (inside and outside); lets say that outside interface has&amp;nbsp;IP address 172.16.1.1 and inside users are in network 192.168.10.0/24.&lt;/P&gt;&lt;P&gt;I have a static NAT mapping 172.16.1.1 to 192.168.10.1 on port 80 (for outsider acess to a vital application); also, I have PAT (to outside interface)configured for inside users to access to internet.&lt;/P&gt;&lt;P&gt;My problem&amp;nbsp;starts when inside users use public IP address (172.16.1.1) to access the vital application; this means that the firewall sees traffic from 172.16.1.1 (users) to 172.16.1.1 (aplicattion) and it drops the traffic.&lt;/P&gt;&lt;P&gt;Is there anyway to bypass this? I think that with&amp;nbsp;another public ip address I would have no problem, with one IP used for PAT and the other for the application but my client does not want to purchase another IP.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;João.&lt;/P&gt;&lt;P&gt;P.S. - I try to tell then to change DNS records but they say that application uses embedded ip addresses.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:06:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577685#M205225</guid>
      <dc:creator>jcarvalh</dc:creator>
      <dc:date>2019-03-12T05:06:30Z</dc:date>
    </item>
    <item>
      <title>Dear Joa0, Try to map the</title>
      <link>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577686#M205226</link>
      <description>&lt;P&gt;Dear Joa0,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try to map the port with 8080 not only 80.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Nov 2014 05:28:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577686#M205226</guid>
      <dc:creator>shahul hamid zehabar sathik aly haja meidine</dc:creator>
      <dc:date>2014-11-20T05:28:21Z</dc:date>
    </item>
    <item>
      <title>Hello.I tried several</title>
      <link>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577687#M205227</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I tried several solutions that I found on internet and foruns but none worked.&lt;/P&gt;&lt;P&gt;I then tried this one and it worked:&lt;/P&gt;&lt;P&gt;nat (Inside,Inside) 2 source dynamic&amp;nbsp;LAN NAT-for-hairpinning destination static Interface-Outside ORION service HTTP HTTP&lt;/P&gt;&lt;P&gt;LAN - Is my inside Network (lets say 192.168.10.1)&lt;/P&gt;&lt;P&gt;NAT-for- hairpinning - IP address not used in organization and used exclusively to source nat my inside network (I used 172.16.0.1)&lt;/P&gt;&lt;P&gt;Interface-Outside - is a network object with IP address of outsider interface&lt;/P&gt;&lt;P&gt;ORION - is internal server (192.168.10.1) in same network na LAN&lt;/P&gt;&lt;P&gt;For me, using the NAT-for-hairpinning object was the only way to put it to work.&lt;/P&gt;&lt;P&gt;Hope this post can be helpfull.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;João.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S. - ASA has version 9.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Nov 2014 15:49:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/hairpinning-cisco-asa-to-the-same-ip-address/m-p/2577687#M205227</guid>
      <dc:creator>jcarvalh</dc:creator>
      <dc:date>2014-11-20T15:49:39Z</dc:date>
    </item>
  </channel>
</rss>

