<?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>DemianJacome Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>DemianJacome Tracker</description>
    <pubDate>Fri, 17 Nov 2023 23:44:19 GMT</pubDate>
    <dc:date>2023-11-17T23:44:19Z</dc:date>
    <item>
      <title>VPN DO NOT ESTABLISH BETWEEN VELOCLOUD GATEWAY AND FORTIGATE</title>
      <link>https://communities.vmware.com/t5/VeloCloud-Discussions/VPN-DO-NOT-ESTABLISH-BETWEEN-VELOCLOUD-GATEWAY-AND-FORTIGATE/m-p/2984290#M157</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I have a problem with IpSec VPN between Velocloud gateway and Fortigate (VM fortigate on OCI, fortigate 200E, 80E, and 500E appliance).&lt;/P&gt;&lt;P&gt;In both cases the VPN isn't established correctly.&amp;nbsp;Do you have the same problem or something similar?&lt;/P&gt;&lt;P&gt;In the case of VPN between Velocloud Gateway and Fortigate VM there is a mismatch with the SPI parameter&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 15:03:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VeloCloud-Discussions/VPN-DO-NOT-ESTABLISH-BETWEEN-VELOCLOUD-GATEWAY-AND-FORTIGATE/m-p/2984290#M157</guid>
      <dc:creator>DemianJacome</dc:creator>
      <dc:date>2023-08-28T15:03:04Z</dc:date>
    </item>
  </channel>
</rss>

