<?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: IPSec Tunnel from vsys1 to vsys2 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203593#M59969</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/83714"&gt;@Solomonsands&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Honestly it seems unnecessary&amp;nbsp;to include an IPSec tunnel in this situation. Palo Alto includes a number of ways to allow inter-vsys communication, and adding a tunnel into this would be rather messy. So options I would look at are the following&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Utilizing an existing switch to simply loop 2 interfaces to bridge the gap. Easy and you get the same benefits with a little less complex of a situation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) Utilize intervsys routing; which can be found in more detail in this LIVE article &lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/Tips-amp-Tricks-Inter-VSYS-routing/ta-p/69699" target="_blank"&gt;HERE&lt;/A&gt;. This is the 'best' answer in my mind, but it does get a little more complex.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Built-in option for this type of traffic would be #2 as listed above.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Mar 2018 17:05:37 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2018-03-05T17:05:37Z</dc:date>
    <item>
      <title>IPSec Tunnel from vsys1 to vsys2</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203583#M59968</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a design issue to mull over, and one of the options is to look at having ipsec tunnels between vsys isntances on the same box.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, I have vsys1 as my default vr, what I may need to do is turn up vsys2 and have certain traffic in vsys1 'hop' over to vsys2.&amp;nbsp; Sounds problmeatic so my first instinct is to encap it between vsys instances.&amp;nbsp; Is there a built-in mechanism to allow virtual systems to securely pass traffic to one-another? I assume that they are all isolated from one another by design, which again makes me think that a tunnel of some type needs to be established for them to communicate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a 5220 in active/passive.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 16:30:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203583#M59968</guid>
      <dc:creator>Solomonsands</dc:creator>
      <dc:date>2018-03-05T16:30:23Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Tunnel from vsys1 to vsys2</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203593#M59969</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/83714"&gt;@Solomonsands&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Honestly it seems unnecessary&amp;nbsp;to include an IPSec tunnel in this situation. Palo Alto includes a number of ways to allow inter-vsys communication, and adding a tunnel into this would be rather messy. So options I would look at are the following&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Utilizing an existing switch to simply loop 2 interfaces to bridge the gap. Easy and you get the same benefits with a little less complex of a situation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) Utilize intervsys routing; which can be found in more detail in this LIVE article &lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/Tips-amp-Tricks-Inter-VSYS-routing/ta-p/69699" target="_blank"&gt;HERE&lt;/A&gt;. This is the 'best' answer in my mind, but it does get a little more complex.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Built-in option for this type of traffic would be #2 as listed above.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 17:05:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203593#M59969</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-03-05T17:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Tunnel from vsys1 to vsys2</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203599#M59971</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the reply.&amp;nbsp; From what I gathered, traffic between vsys have to egress to their respective external zone before traversing the firewall in to the destination external zone.&amp;nbsp; My concern is the encryption state of each hop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the 5220 at edge with vsys1.&amp;nbsp; He takes an IPSec tunnel from a crappy remote router with less-than-optimal encryption.&amp;nbsp; Per our sec posture, only FIPS crypto can be used to get in to our environment.&amp;nbsp; Our solution thus far is to stand up an intermediate ipsec router that can speak non-FIPS, and then it routes the traffic to the 5220 with FIPS crypto in to a dmz. We believe the use of another vsys can take the place of the intermediate router, but need to be sure that the traffic passing from vsys to vsys is secure and observable.&amp;nbsp; Is this what inter-vsys routing does by default?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 17:43:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203599#M59971</guid>
      <dc:creator>Solomonsands</dc:creator>
      <dc:date>2018-03-05T17:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Tunnel from vsys1 to vsys2</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203612#M59978</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;If its only one or a few machines that need to connect to you via VPN, what about giving them the GlobalProtect client? That way you can ensure your security posture.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just a thought.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 19:34:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-tunnel-from-vsys1-to-vsys2/m-p/203612#M59978</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-03-05T19:34:08Z</dc:date>
    </item>
  </channel>
</rss>

