<?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 Site to site VPN help :( in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228801#M65770</link>
    <description>&lt;P&gt;Unable to make VPN work. Both "IKE Info" and "Tunnel Info" are red light in IPSec Tunnel.&lt;/P&gt;&lt;P&gt;The peer is a Juniper vSRX.&lt;/P&gt;&lt;P&gt;Normal configuration with trust, untrust and VPN zone in both firewall. Each zone has its own subnet.&lt;/P&gt;&lt;P&gt;Both firewall can ping each other untrust interface.&lt;/P&gt;&lt;P&gt;Workstations behind the firewalls can ping firewall's untrust interface too (default route + source NAT)&lt;/P&gt;&lt;P&gt;Security policy for VPN zone to VPN zone set to allow any.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;debug ike gateway and tunnel were on&lt;/P&gt;&lt;P&gt;ikemgr.log show "SA dying from state INI_IKE_SA_INIT_SENT, caller ikev2_abort"&amp;nbsp; after 10 times retry.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;test and show vpn ike-sa gateway show&lt;/P&gt;&lt;P&gt;State: "INIT send &amp;lt;= Idle &amp;lt;== Idle &amp;lt;== Idle"&lt;/P&gt;&lt;P&gt;reason: ikev2_initiator_start&lt;/P&gt;&lt;P&gt;I think this is what SA keep trying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have no idea how to solve this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Aug 2018 06:21:46 GMT</pubDate>
    <dc:creator>jeremylo</dc:creator>
    <dc:date>2018-08-30T06:21:46Z</dc:date>
    <item>
      <title>Site to site VPN help :(</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228801#M65770</link>
      <description>&lt;P&gt;Unable to make VPN work. Both "IKE Info" and "Tunnel Info" are red light in IPSec Tunnel.&lt;/P&gt;&lt;P&gt;The peer is a Juniper vSRX.&lt;/P&gt;&lt;P&gt;Normal configuration with trust, untrust and VPN zone in both firewall. Each zone has its own subnet.&lt;/P&gt;&lt;P&gt;Both firewall can ping each other untrust interface.&lt;/P&gt;&lt;P&gt;Workstations behind the firewalls can ping firewall's untrust interface too (default route + source NAT)&lt;/P&gt;&lt;P&gt;Security policy for VPN zone to VPN zone set to allow any.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;debug ike gateway and tunnel were on&lt;/P&gt;&lt;P&gt;ikemgr.log show "SA dying from state INI_IKE_SA_INIT_SENT, caller ikev2_abort"&amp;nbsp; after 10 times retry.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;test and show vpn ike-sa gateway show&lt;/P&gt;&lt;P&gt;State: "INIT send &amp;lt;= Idle &amp;lt;== Idle &amp;lt;== Idle"&lt;/P&gt;&lt;P&gt;reason: ikev2_initiator_start&lt;/P&gt;&lt;P&gt;I think this is what SA keep trying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have no idea how to solve this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 06:21:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228801#M65770</guid>
      <dc:creator>jeremylo</dc:creator>
      <dc:date>2018-08-30T06:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: Site to site VPN help :(</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228856#M65771</link>
      <description>&lt;P&gt;looks like they're not playing ball&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;verify all ike settings from a fresh perspective to make sure all parameters are correct (peer ip is accurtate, negotiation settings are good etc )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the PA you can manually initiate by using &amp;gt; test vpn ike-sa gateway &amp;lt;gateway&amp;gt; (and &amp;gt; test vpn ipsec-sa gateway &amp;lt;gw&amp;gt; for phase2 )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if there's a similar command on the juniper you should try that too, being able to compare 'inbound' system logs may grant more visibility in your issue than staring at debug logs (inbound system logs wil tell you what the remote end is doing wrong, if no system logs show up, the remote end is not talking or is being blocked)&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 11:56:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228856#M65771</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2018-08-30T11:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: Site to site VPN help :(</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228883#M65785</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I found a few articles that talk about VPN's between Juniper and PAN. They might be worth checking out?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Learning-Articles/Tips-for-Configuring-a-Juniper-SRX-IPSEC-VPN-Tunnel-to-a-Palo/ta-p/61287" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Learning-Articles/Tips-for-Configuring-a-Juniper-SRX-IPSEC-VPN-Tunnel-to-a-Palo/ta-p/61287&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Configuration-Articles/PanOS-to-Juniper-SRX-Route-Based-VPN-with-OSPF/ta-p/53112" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Configuration-Articles/PanOS-to-Juniper-SRX-Route-Based-VPN-with-OSPF/ta-p/53112&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Aug 2018 13:49:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228883#M65785</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-08-30T13:49:14Z</dc:date>
    </item>
    <item>
      <title>Re: Site to site VPN help :(</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228967#M65811</link>
      <description>&lt;P&gt;Hello. I think I overlook the type of VPN - "Route-based" and "Policy-based".&lt;/P&gt;&lt;P&gt;I don't even know I'm using which type. Policy-based require setup "Proxy ID" and I don't have any of it.&lt;/P&gt;&lt;P&gt;Found some info in&amp;nbsp;&lt;A href="https://blog.webernetz.net/route-vs-policy-based-vpn-tunnels/" target="_self"&gt;https://blog.webernetz.net/route-vs-policy-based-vpn-tunnels/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Mention that PaloAlto don't support Policy-based VPN. Is that true?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Aug 2018 01:32:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228967#M65811</guid>
      <dc:creator>jeremylo</dc:creator>
      <dc:date>2018-08-31T01:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Site to site VPN help :(</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228982#M65814</link>
      <description>&lt;P&gt;hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/92212"&gt;@jeremylo&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;We are route based, which means that how the tunnel is set up and how traffic is put into it are 2 separate processes&lt;/P&gt;
&lt;P&gt;a policy based system combines those 2 functions&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This in itself is not a big issue, as ProxyIDs&amp;nbsp;fix that 'incompatibility'&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A route based VPN solution simply requires you to set up a VPN&amp;nbsp;profile (peer, crypto, ..) and then add routes on the&amp;nbsp;VirtualRouter that point to the tunnel interface for all the subnets at the other end of the tunnel&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A policy-based system combines the subnets that need to speak to each other&amp;nbsp;in the VPN&amp;nbsp;decision&amp;nbsp;process, which can be simulated by creating matching subnet pairs in ProxyID which would tell the remote (policy-based) system the routing pairs&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So the statement that we don't support policy based VPN is false (at the bottom of the article you can see they included a chart where we are marked as supporting policy based &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; ). We aren't policy based but we do provide the proxyID functionality to make us compatible&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for the Juniper SRX use the 'bind-interface' option when configuring the ipsec&amp;nbsp;vpn&amp;nbsp;to make it route based&lt;/P&gt;</description>
      <pubDate>Fri, 31 Aug 2018 06:24:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/228982#M65814</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2018-08-31T06:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Site to site VPN help :(</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/229675#M66038</link>
      <description>&lt;P&gt;Reason found. The vSRX was faulty. Setup and use the new version vSRX has no problem&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 07:53:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/site-to-site-vpn-help/m-p/229675#M66038</guid>
      <dc:creator>jeremylo</dc:creator>
      <dc:date>2018-09-06T07:53:02Z</dc:date>
    </item>
  </channel>
</rss>

