<?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: Unleashed 200.18.7.1.302 issue. in Unleashed</title>
    <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/109385#M7065</link>
    <description>&lt;P&gt;@&lt;A class="" href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/88" target="_self"&gt;&lt;SPAN class=""&gt;sanjay_kumar&lt;/SPAN&gt;&lt;/A&gt;&amp;nbsp;@&lt;A class="" href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/24003" target="_self"&gt;&lt;SPAN class=""&gt;RUCSAK1&lt;/SPAN&gt;&lt;/A&gt;, Thanks for your help！&amp;nbsp;Yes, the problem has gone after only enable WPA2. Thank you! However, I can't figure out why the 200.17 version doesn't have this issue. Anyway, I'll solve it by enabling only WPA2 authentication for 200.18 new version firmware.&lt;/P&gt;</description>
    <pubDate>Tue, 09 Sep 2025 14:17:03 GMT</pubDate>
    <dc:creator>biniyi</dc:creator>
    <dc:date>2025-09-09T14:17:03Z</dc:date>
    <item>
      <title>Unleashed 200.18.7.1.302 issue.</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/106182#M6934</link>
      <description>&lt;P&gt;When R850 upgrade to Unleashed 200.18.7.1.302 from 2&lt;SPAN&gt;00.17.7.0.152. then some 2.4G smart home device will be officeline (2.4G &amp;amp; 5G is same SSID, and with 30+ smart home deivce, Most of them are 2.4G devices.) . If downgrade to version 200.17.7.0.152, no this issue.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jun 2025 11:54:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/106182#M6934</guid>
      <dc:creator>biniyi</dc:creator>
      <dc:date>2025-06-02T11:54:20Z</dc:date>
    </item>
    <item>
      <title>Re: Unleashed 200.18.7.1.302 issue.</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/106231#M6935</link>
      <description>&lt;P&gt;@biniyi,&lt;BR /&gt;&lt;BR /&gt;If the product has support warranty, could you please raise a support case on this.&lt;BR /&gt;I might need some additional data to see the issue.&lt;BR /&gt;&lt;BR /&gt;If not, let me know so that I can guide you to collect the necessary logs.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 04:35:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/106231#M6935</guid>
      <dc:creator>sanjay_kumar</dc:creator>
      <dc:date>2025-06-03T04:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: Unleashed 200.18.7.1.302 issue.</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/106482#M6945</link>
      <description>&lt;P&gt;Try Enabling WPA2 and WPA3,&amp;nbsp; I had this issue on the 5ghz, it was some devices not supporting WPA3, and needing WPA2,&amp;nbsp; but I had that turned off.&amp;nbsp; When I enabled WPA2 (made it the same password as WPA3 so I would not have to enter new passwords for everything) it all worked.&amp;nbsp; &amp;nbsp;I have no idea on why 200.16 it worked, and in 200.17 it didn't - but something for sure changed with how WPA2 and WPA3 support is designed.&amp;nbsp; In my case the manufacture (Control4) said there was never any support for WPA3 for their remotes, but I had them working perfect with ONLY WPA3 enabled on SSIDs.&amp;nbsp; Hopefully this helps you.&amp;nbsp; Wondering if this is also your issue.&amp;nbsp; They said this specific issue was fixed in 200.18 - but I have not tested to confirm, I left my config with WPA2 and WPA3 on.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 01:15:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/106482#M6945</guid>
      <dc:creator>RUCSAK1</dc:creator>
      <dc:date>2025-06-11T01:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: Unleashed 200.18.7.1.302 issue.</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/109385#M7065</link>
      <description>&lt;P&gt;@&lt;A class="" href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/88" target="_self"&gt;&lt;SPAN class=""&gt;sanjay_kumar&lt;/SPAN&gt;&lt;/A&gt;&amp;nbsp;@&lt;A class="" href="https://community.ruckuswireless.com/t5/user/viewprofilepage/user-id/24003" target="_self"&gt;&lt;SPAN class=""&gt;RUCSAK1&lt;/SPAN&gt;&lt;/A&gt;, Thanks for your help！&amp;nbsp;Yes, the problem has gone after only enable WPA2. Thank you! However, I can't figure out why the 200.17 version doesn't have this issue. Anyway, I'll solve it by enabling only WPA2 authentication for 200.18 new version firmware.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Sep 2025 14:17:03 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Unleashed-200-18-7-1-302-issue/m-p/109385#M7065</guid>
      <dc:creator>biniyi</dc:creator>
      <dc:date>2025-09-09T14:17:03Z</dc:date>
    </item>
  </channel>
</rss>

