<?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 VPN issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226665#M65250</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;thank you for the reply,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes I'm log the interzone, in day to day basic I don't have policy to allow DMZ accessing the VPN tunnel (the opposite direction) so when I trying to ping I see it denies on the interzone-default rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's why for testing the return routing I created new policy allowing DMZ to access VPN tunnel for PING/ICMP and then suddenly the opposite way, VPN tunnel to DMZ started to work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Aug 2018 22:34:18 GMT</pubDate>
    <dc:creator>SShnap</dc:creator>
    <dc:date>2018-08-09T22:34:18Z</dc:date>
    <item>
      <title>IPSEC VPN issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226523#M65212</link>
      <description>&lt;P&gt;I have realy weired issue,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have two sites connected with IPSEC vpn, PAVM200 to PA3020.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the sites are connected with IPSEC very stable vpn, remote site trying to access DMZ zone on the local site.&lt;/P&gt;&lt;P&gt;The routing confiured and policy rule allowing the access from VPN to DMZ.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;everything works fine and I was able to see the traffic,&lt;/P&gt;&lt;P&gt;suddenly after the VPN drop and esteblish the connection again the remote site users can only access the local site network but no DMZ zone on local site.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;on the logs for the remote site I see the traffic egress to the right tunnel without reply, on the local site I don't see the traffic is coming.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On last try I was creating new policy rule for DMZ to remote site network for checking the reply routing and suddenly everything come back to normal and working even after I disalbe the new policy rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now after 5 months that it's working the VPN dropped again and once again I needed to create that new policy for bring everything to work again, very weired.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;any suggestion what to check?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the help.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 22:09:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226523#M65212</guid>
      <dc:creator>SShnap</dc:creator>
      <dc:date>2018-08-08T22:09:09Z</dc:date>
    </item>
    <item>
      <title>Re: IPSEC VPN issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226656#M65242</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/40971"&gt;@SShnap&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Do you log the interzone default rule so that you can see if the policy is getting denied in the logs? It would be very odd to see this happen unless for some reason the security policy that was matching this traffic for some reason no longer matched the traffic as it should. (Either changes on the Local or Remote end; or the XML getting corrupt following changes or upgrades).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Aug 2018 19:58:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226656#M65242</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-08-09T19:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: IPSEC VPN issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226665#M65250</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;thank you for the reply,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes I'm log the interzone, in day to day basic I don't have policy to allow DMZ accessing the VPN tunnel (the opposite direction) so when I trying to ping I see it denies on the interzone-default rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's why for testing the return routing I created new policy allowing DMZ to access VPN tunnel for PING/ICMP and then suddenly the opposite way, VPN tunnel to DMZ started to work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Aug 2018 22:34:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-vpn-issue/m-p/226665#M65250</guid>
      <dc:creator>SShnap</dc:creator>
      <dc:date>2018-08-09T22:34:18Z</dc:date>
    </item>
  </channel>
</rss>

