<?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: WPA3 in a mixed environment in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/wpa3-in-a-mixed-environment/m-p/72592#M5514</link>
    <description>&lt;P&gt;The AP390s are not compatible with the 8.X HiveOS releases. This would include features such as WPA3 compatibility. I would recommend that you only utilize WPA2 in your configuration. If you created another policy so one had a WPA2 SSID and the other had WPA3, even if the SSIDs shared identical broadcast names, the clients still wouldn't roam seamlessly. &lt;/P&gt;</description>
    <pubDate>Thu, 28 Feb 2019 03:44:49 GMT</pubDate>
    <dc:creator>AnonymousM</dc:creator>
    <dc:date>2019-02-28T03:44:49Z</dc:date>
    <item>
      <title>WPA3 in a mixed environment</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/wpa3-in-a-mixed-environment/m-p/72591#M5513</link>
      <description>&lt;P&gt;In one location, we have a mix of AP230s, 1130s, and 390s. The auth on one of our SSIDs appears to have updated to WPA3. Unfortunately, when I attempt a push (complete or delta) to the 390s, it fails with the following error...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could not generate the CLI configuration. You have configured WPA3 (SAE) Personal Authentication in SSID (&lt;I&gt;ssid_name&lt;/I&gt;), but only the device (not 11ax) with version 8.4.r7(+) supports this.&amp;nbsp;   &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do we need to downgrade the auth to WPA2 in this environment, or is this a known issue with a fix to follow?   &lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 00:01:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/wpa3-in-a-mixed-environment/m-p/72591#M5513</guid>
      <dc:creator>bruce_stahlin</dc:creator>
      <dc:date>2019-02-28T00:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: WPA3 in a mixed environment</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/wpa3-in-a-mixed-environment/m-p/72592#M5514</link>
      <description>&lt;P&gt;The AP390s are not compatible with the 8.X HiveOS releases. This would include features such as WPA3 compatibility. I would recommend that you only utilize WPA2 in your configuration. If you created another policy so one had a WPA2 SSID and the other had WPA3, even if the SSIDs shared identical broadcast names, the clients still wouldn't roam seamlessly. &lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 03:44:49 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/wpa3-in-a-mixed-environment/m-p/72592#M5514</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2019-02-28T03:44:49Z</dc:date>
    </item>
  </channel>
</rss>

