<?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: How to configure a Cisco ASA behind PA2050 with public IP in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/748#M586</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;libr, if the external interface of the ASA must have a public IP address then configuring two interfaces on your 2050 for VWire seems to be your best option.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Nov 2011 12:33:01 GMT</pubDate>
    <dc:creator>bvandivier</dc:creator>
    <dc:date>2011-11-02T12:33:01Z</dc:date>
    <item>
      <title>How to configure a Cisco ASA behind PA2050 with public IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/743#M581</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to figure out how to configure our PA2050 to point one of our public IPs in a /25 block to a Cisco ASA 5510 behind it. We're using both the PA's SSL VPN and the ASA's SSL VPN so I'd like to plug the ASA into port 2 on the PA2050 and allow it to be accessed directly via one of those public IPs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our upstream provider's equipment is x.x.x.1/25, interface 1 on the PA2050 is x.x.x.2/25, and I want to set up the ASA as x.x.x.125/25. Our upstream link comes directly into interface 1 of the PA2050 and I'd prefer NOT to put a switch in between them or something similar. How would I accomplish this? We've got plenty of NAT mappings working properly for various public IPs to internal RFC1918 addresses, but I'm a bit lost here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any pointers are appreciated, thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Sep 2011 21:50:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/743#M581</guid>
      <dc:creator>mhoush</dc:creator>
      <dc:date>2011-09-30T21:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure a Cisco ASA behind PA2050 with public IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/744#M582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you considered running the ASA and the Paloalto in parallel? If you really want the ASA traffic inspected by the PA as well, you could put a vwire in front of the Cisco and then run the Cisco in parallel with the PA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To avoid the need for a switch you could do a "one to one" nat on the WAN side of the PA to an IP on another interface that leads to the ASA. To do this build the NAT rule from the trusted side towards the internet and select the "bi-directional" option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve Krall&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Sep 2011 23:04:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/744#M582</guid>
      <dc:creator>skrall</dc:creator>
      <dc:date>2011-09-30T23:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure a Cisco ASA behind PA2050 with public IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/745#M583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I do want the PA to do all the traffic inspection in this case, the ASA is *only* there as a Cisco VPN endpoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I were to do the 1-to-1 NAT method, I'm not understanding how to handle the interface addresses. What address would I be setting on interface 2 of the PA2050 if I plug the ASA into that one, given that the ASA should answer to x.x.x.125/25?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Oct 2011 00:02:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/745#M583</guid>
      <dc:creator>mhoush</dc:creator>
      <dc:date>2011-10-01T00:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure a Cisco ASA behind PA2050 with public IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/746#M584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@libr:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is the Cisco VPN encrypting ALL of the traffic with SSL? Or is it using IPSEC as well? You have to remember that the Palo Alto Device can decrypt the SSL traffc, but not IPSEC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Benjamin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Oct 2011 01:27:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/746#M584</guid>
      <dc:creator>bpappas</dc:creator>
      <dc:date>2011-10-01T01:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure a Cisco ASA behind PA2050 with public IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/747#M585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, I've misread/misunderstood what the responses were asking, sorry! I don't want to do traffic inspection, I just want the PA to do all the filtering for VPN users connecting to the ASA. Sorry for the confusion. For what it's worth, though, I'm only doing SSL VPN, no IPSEC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Oct 2011 04:44:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/747#M585</guid>
      <dc:creator>mhoush</dc:creator>
      <dc:date>2011-10-01T04:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure a Cisco ASA behind PA2050 with public IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/748#M586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;libr, if the external interface of the ASA must have a public IP address then configuring two interfaces on your 2050 for VWire seems to be your best option.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Nov 2011 12:33:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-configure-a-cisco-asa-behind-pa2050-with-public-ip/m-p/748#M586</guid>
      <dc:creator>bvandivier</dc:creator>
      <dc:date>2011-11-02T12:33:01Z</dc:date>
    </item>
  </channel>
</rss>

