<?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 NAT Loopback in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034164#M439135</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think I explained it very well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The device the teleworkers need access to is on the inside. But I don't want to programme the teleworks with the internal IP as that obviously won't work when they are shiped out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;209.x.x157 is static NAT'd to 10.1.11.9&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need for the teleworkers to be able to reach 209.x.x.157 from the inside rather than having to use 10.1.11.9.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully that better explains it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Aug 2012 14:35:49 GMT</pubDate>
    <dc:creator>CompuVision Admin</dc:creator>
    <dc:date>2012-08-22T14:35:49Z</dc:date>
    <item>
      <title>ASA NAT Loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034162#M439133</link>
      <description>&lt;P&gt;I have a requirement to access one of our outside interface IP addresses from inside the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The scenario is we have teleworker devices that we provision in house before sending out. These devices cannot use a hostname but must be programmed with the IP. I would like to able to confirm these devices are working before shipping them out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been attempting some kind of loopback/hair pinning NAT rules but haven't managed to get one working yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Device: ASA 5510&amp;nbsp; v8.4&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:44:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034162#M439133</guid>
      <dc:creator>CompuVision Admin</dc:creator>
      <dc:date>2019-03-11T23:44:42Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034163#M439134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bro&lt;/P&gt;&lt;P&gt;There's no provision for interface loopback in Cisco ASA. What you can do is, set an IP Address, Subnetmask and Default Gateway on those teleworker devices, place them on the &lt;STRONG&gt;INSIDE nameif &lt;/STRONG&gt;of the Cisco ASA, and try to access devices on the &lt;STRONG&gt;OUTSIDE nameif &lt;/STRONG&gt;of the Cisco ASA. You can ping the OUTSIDE IP Address from INSIDE, provided you've the &lt;STRONG&gt;management-access outside&lt;/STRONG&gt; command, but this is messy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P/S: If you think this comment is useful, please do rate them nicely &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2012 04:03:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034163#M439134</guid>
      <dc:creator>Ramraj Sivagnanam Sivajanam</dc:creator>
      <dc:date>2012-08-22T04:03:47Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034164#M439135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think I explained it very well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The device the teleworkers need access to is on the inside. But I don't want to programme the teleworks with the internal IP as that obviously won't work when they are shiped out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;209.x.x157 is static NAT'd to 10.1.11.9&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need for the teleworkers to be able to reach 209.x.x.157 from the inside rather than having to use 10.1.11.9.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully that better explains it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2012 14:35:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034164#M439135</guid>
      <dc:creator>CompuVision Admin</dc:creator>
      <dc:date>2012-08-22T14:35:49Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT Loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034165#M439136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If that's the case, you'll need to enable Cisco DNS Doctoring in your Cisco FW. You could refer to this Cisco URL as a guide &lt;A href="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml" rel="nofollow"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;P/S: If you think this comment is useful, please do rate it nicely &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2012 18:25:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034165#M439136</guid>
      <dc:creator>Ramraj Sivagnanam Sivajanam</dc:creator>
      <dc:date>2012-08-22T18:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT Loopback</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034166#M439137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I understand it, DNS doctoring simply hijacks the DNS request and replaces the external IP with the internal. I don't see how that is going to help considering there are no DNS requests taking place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I could programme the teleworker devices with a hostname I would just run split DNS and call it a day. Unfortunately I cannot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As much as I dislike SonicWALL devices, a loopback NAT rule is a 15 second task on them. In fact most are auto generated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2012 23:16:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-loopback/m-p/2034166#M439137</guid>
      <dc:creator>CompuVision Admin</dc:creator>
      <dc:date>2012-08-22T23:16:58Z</dc:date>
    </item>
  </channel>
</rss>

