<?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 Site to Site tunnel With Watchguard Firewalls as peers in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-with-watchguard-firewalls-as-peers/m-p/43819#M32169</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the PA firewall is the responder, take a look at your ikemgr.log file. You can use this command to navigate using standard linux 'less' navigation:&lt;/P&gt;&lt;P&gt;&amp;gt; less mp-log ikemgr.log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Find the time of the most recent failure and see what the reason for the failure is, the log should give you pretty good details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the PA firewall is the initiator, you'll need to look at the logs on the Watchguard. It sounds like you're establishing correctly, but a re-key is likely failing. The log is your best bet for seeing the issue.&lt;/P&gt;&lt;P&gt;Does it re-establish by itself? How about if you use the test command:&lt;/P&gt;&lt;P&gt;&amp;gt; test vpn ipsec-sa tunnel &amp;lt;tunnel-name&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also try enabling tunnel monitoring on the PA firewall in the IPSec config (Network &amp;gt; IPSec Tunnels &amp;gt; (tunnel name) &amp;gt; General tab &amp;gt; Advanced &amp;gt; Tunnel Monitor. Configure an address on the other side of the tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;&lt;P&gt;Greg &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Dec 2012 23:56:20 GMT</pubDate>
    <dc:creator>gwesson</dc:creator>
    <dc:date>2012-12-07T23:56:20Z</dc:date>
    <item>
      <title>IPSEC Site to Site tunnel With Watchguard Firewalls as peers</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-with-watchguard-firewalls-as-peers/m-p/43818#M32168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;I have a problem with the PAN keeping a tunnel connected to Watchguard firewalls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase1&lt;/P&gt;&lt;P&gt;Main Mode&lt;/P&gt;&lt;P&gt;IKE Crypto: MD5-3DES-GP1&lt;/P&gt;&lt;P&gt;Lifetime: 8 Hours&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DPD 5-5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase2&lt;/P&gt;&lt;P&gt;IPSec Crypto: MD5-3DES-NoPFS&lt;/P&gt;&lt;P&gt;Lifetime 8 Hours&lt;/P&gt;&lt;P&gt;LifeSize 128 MB&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Proxy: Local 10.0.0.0/8&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remote: 192.168.4.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tried just about every type of Authentication and Encryption possible but still cant get a stable tunnel. They will work for a day or 2 and then fail. I have to delete and rebuild the tunnels on the Watchguards to bring the connection back up.&lt;/P&gt;&lt;P&gt;I have not tried to play with the lifetime or size settings yet. I also have not tried Agressive mode yet. Anyone out there been able to make a stable tunnel with a Watchguard Firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2012 22:20:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-with-watchguard-firewalls-as-peers/m-p/43818#M32168</guid>
      <dc:creator>nationalhme</dc:creator>
      <dc:date>2012-12-07T22:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: IPSEC Site to Site tunnel With Watchguard Firewalls as peers</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-with-watchguard-firewalls-as-peers/m-p/43819#M32169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the PA firewall is the responder, take a look at your ikemgr.log file. You can use this command to navigate using standard linux 'less' navigation:&lt;/P&gt;&lt;P&gt;&amp;gt; less mp-log ikemgr.log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Find the time of the most recent failure and see what the reason for the failure is, the log should give you pretty good details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the PA firewall is the initiator, you'll need to look at the logs on the Watchguard. It sounds like you're establishing correctly, but a re-key is likely failing. The log is your best bet for seeing the issue.&lt;/P&gt;&lt;P&gt;Does it re-establish by itself? How about if you use the test command:&lt;/P&gt;&lt;P&gt;&amp;gt; test vpn ipsec-sa tunnel &amp;lt;tunnel-name&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also try enabling tunnel monitoring on the PA firewall in the IPSec config (Network &amp;gt; IPSec Tunnels &amp;gt; (tunnel name) &amp;gt; General tab &amp;gt; Advanced &amp;gt; Tunnel Monitor. Configure an address on the other side of the tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;&lt;P&gt;Greg &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2012 23:56:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-with-watchguard-firewalls-as-peers/m-p/43819#M32169</guid>
      <dc:creator>gwesson</dc:creator>
      <dc:date>2012-12-07T23:56:20Z</dc:date>
    </item>
  </channel>
</rss>

