<?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: Enable 802.11k Neighbor-list Report Checkbox Greyed Out in Unleashed</title>
    <link>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38148#M3847</link>
    <description>&lt;P style="margin: 0;"&gt;Yes, basically you should remember, that 802.11r is still mostly supported only on&amp;nbsp; mobile phones, but is in most cases unsupported by laptops and many other devices, and potentially prevents them to have stable connection. So don't enable it, if you are not sure that all clients support it (which will be never the case, if network is public).&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Dec 2021 07:25:13 GMT</pubDate>
    <dc:creator>eizens_putnins</dc:creator>
    <dc:date>2021-12-20T07:25:13Z</dc:date>
    <item>
      <title>Enable 802.11k Neighbor-list Report Checkbox Greyed Out</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38146#M3845</link>
      <description>&lt;P style="margin: 0;"&gt;Good afternoon,&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;I recently added a second R610 access point and wanted to enable all roaming technologies.&amp;nbsp;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;I turned on "Fast BSS Transition E&lt;LABEL&gt;nable 802.11r FT Roaming" but am unable to check "Enable 802.11k Neighbor-list Report" as it is greyed out. I also SSH'd into the master AP and turned on 802.11v aka Smart Roaming with setting 3. I was wondering why Neighbor-list report is not allowing me to enable it. Thank you for your help.&lt;/LABEL&gt;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 19 Dec 2021 21:15:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38146#M3845</guid>
      <dc:creator>nathaniel_olive</dc:creator>
      <dc:date>2021-12-19T21:15:13Z</dc:date>
    </item>
    <item>
      <title>Re: Enable 802.11k Neighbor-list Report Checkbox Greyed Out</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38147#M3846</link>
      <description>&lt;P style="margin: 0;"&gt;Eventually 802.11r will be a helpful feature but in most cases today, it creates more problems than it solves.&amp;nbsp; That is why Ruckus has it disabled by default.&amp;nbsp; Same thing goes for SmartRoam.&amp;nbsp; That feature will force sticky clients to roam, but if your transmit power is properly balanced (lowered) and you don't have sticky clients, you should not use it.&amp;nbsp; It is disruptive to the well behaved clients (which most are these days).&amp;nbsp; Under normal 802.11 roaming,&amp;nbsp; the protocol defines the process for a client to initiate roaming and seamlessly migrate it's connection from the old AP to the new one.&amp;nbsp; SmartRoam does the opposite - without warning, it terminates the connection and leaves the unsuspecting client to scramble to find a new AP and establish a new connection. Again, Ruckus defaults are set for a reason and it is best to leave them alone unless you are solving a specific problem.&lt;/P&gt;</description>
      <pubDate>Sun, 19 Dec 2021 22:10:52 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38147#M3846</guid>
      <dc:creator>david_black_594</dc:creator>
      <dc:date>2021-12-19T22:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: Enable 802.11k Neighbor-list Report Checkbox Greyed Out</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38148#M3847</link>
      <description>&lt;P style="margin: 0;"&gt;Yes, basically you should remember, that 802.11r is still mostly supported only on&amp;nbsp; mobile phones, but is in most cases unsupported by laptops and many other devices, and potentially prevents them to have stable connection. So don't enable it, if you are not sure that all clients support it (which will be never the case, if network is public).&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Dec 2021 07:25:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38148#M3847</guid>
      <dc:creator>eizens_putnins</dc:creator>
      <dc:date>2021-12-20T07:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: Enable 802.11k Neighbor-list Report Checkbox Greyed Out</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38149#M3848</link>
      <description>&lt;P style="margin: 0;"&gt;Hi Nanthaniel,&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;You already got expert comments from David and Eizens so I think it will help you to decide if you want to enable 802.11r or not. However, problem you have described is more on the system configuration side and related to GUI.&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;&lt;/P&gt; 
&lt;P style="margin: 0;"&gt;Could you share a screenshot of WLAN settings? Also try creating a new SSID and see if that also behave same way.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 19:11:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/Enable-802-11k-Neighbor-list-Report-Checkbox-Greyed-Out/m-p/38149#M3848</guid>
      <dc:creator>syamantakomer</dc:creator>
      <dc:date>2021-12-21T19:11:09Z</dc:date>
    </item>
  </channel>
</rss>

