<?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: Re-direct DMZ IP Back to Outside Interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489080#M652431</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;This would require that IPSec and ISAKMP be disabled on the ASA completely and that the 3K setup for nat traversal.&lt;/P&gt;&lt;P&gt;If the tunnel requires the use of ESP, protocol 50,&amp;nbsp; then this will not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need to create a prot map for each protocol, so in this case UDP/500 and UDP/4500.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) udp interface isakmp 192.168.100.1 isakmp netmask 255.2552.255.255&lt;/P&gt;&lt;P&gt;static (inside,outside) udp interface 4500 192.168.100.1 4500 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Aug 2010 18:27:19 GMT</pubDate>
    <dc:creator>Loren Kolnes</dc:creator>
    <dc:date>2010-08-19T18:27:19Z</dc:date>
    <item>
      <title>Re-direct DMZ IP Back to Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489079#M652429</link>
      <description>&lt;P&gt;My current setup has an ASA and a VPN3k with a public IP in the DMZ.&amp;nbsp; I've successfully tested using the ASA to terminate VPN connections and am planning on how best to retire the VPN3k.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is an example using private range IPs to represent the public IPs:&lt;/P&gt;&lt;P&gt;VPN3k IP - 192.168.100.1&lt;/P&gt;&lt;P&gt;ASA outside interface IP - 192.168.0.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a temporary measure could I re-direct traffic bound for the VPN3k's public IP to to the ASA's outside interface IP so that the ASA will then terminate the VPN connections?&amp;nbsp; I realize I'll have to re-create the groups on the VPN3k to tunnel groups on the ASA.&amp;nbsp; I'm thinking something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (DMZ,outside) interface 192.168.100.1 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will this work?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:25:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489079#M652429</guid>
      <dc:creator>terrygwazdosky</dc:creator>
      <dc:date>2019-03-11T18:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Re-direct DMZ IP Back to Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489080#M652431</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;This would require that IPSec and ISAKMP be disabled on the ASA completely and that the 3K setup for nat traversal.&lt;/P&gt;&lt;P&gt;If the tunnel requires the use of ESP, protocol 50,&amp;nbsp; then this will not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need to create a prot map for each protocol, so in this case UDP/500 and UDP/4500.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) udp interface isakmp 192.168.100.1 isakmp netmask 255.2552.255.255&lt;/P&gt;&lt;P&gt;static (inside,outside) udp interface 4500 192.168.100.1 4500 netmask 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Aug 2010 18:27:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489080#M652431</guid>
      <dc:creator>Loren Kolnes</dc:creator>
      <dc:date>2010-08-19T18:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: Re-direct DMZ IP Back to Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489081#M652433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.&amp;nbsp; Unfortunately ESP is a necessity so this won't work for me.&amp;nbsp; The TAC came up with a fairly complicated scheme to accomplish this, but I fell back to using the VPN3k to push new config files to the clients.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Aug 2010 13:04:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489081#M652433</guid>
      <dc:creator>terrygwazdosky</dc:creator>
      <dc:date>2010-08-20T13:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: Re-direct DMZ IP Back to Outside Interface</title>
      <link>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489082#M652434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think you can make the connections terminate on the outside of the ASA for a different IP other than the interface IP. You have one of the two options:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Keep the 3K&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Change the IP of the ASA outside interface to that of 3K&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Aug 2010 20:24:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/re-direct-dmz-ip-back-to-outside-interface/m-p/1489082#M652434</guid>
      <dc:creator>Nagaraja Thanthry</dc:creator>
      <dc:date>2010-08-20T20:24:34Z</dc:date>
    </item>
  </channel>
</rss>

