<?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 ChannelFly seems less hoppy in 9.12... in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37154#M2006</link>
    <description>I'd like to share an observation that I've made over the weekend, wondering if this was intentional or not.&lt;BR /&gt;&lt;BR /&gt;I love the concept of ChannelFly, but previously found it really hard to control the number of channel changes. Namely, even with a relatively high MTBC setting (300-600min) and days of uptime, I would still find multiple rapid back-and-forth transitions (e.g. 3 -&amp;gt; 6, 6-&amp;gt;3 within a minute of each other), and quite honestly the MTBC setting didn't seem to do anything.&lt;BR /&gt;&lt;BR /&gt;But this appears to have changed in ZF 9.12. With 9.12, Channelfly is still understandably aggressive at channel-hopping within the first hour or two of uptime, but then it starts noticeably slowing down. Now, with 3 days of uptime and counting, my outdoor AP switches channels every 6 to 10 hours, and my indoor AP's are doing a good job of staying put, especially in 5GHz where there's relatively few neighbors. I have my MTBC set at 300 minutes and it does seem like it's an average of 5+ hours per switch.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I noticed too that the AP syslogs now print the channelfly set MTBC and actual MTBC on each channel switch.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Is this an intentional enhancement to ChannelFly, or am I possibly imagining this behavior?&amp;nbsp;</description>
    <pubDate>Mon, 10 Aug 2015 18:17:12 GMT</pubDate>
    <dc:creator>john_d</dc:creator>
    <dc:date>2015-08-10T18:17:12Z</dc:date>
    <item>
      <title>ChannelFly seems less hoppy in 9.12...</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37154#M2006</link>
      <description>I'd like to share an observation that I've made over the weekend, wondering if this was intentional or not.&lt;BR /&gt;&lt;BR /&gt;I love the concept of ChannelFly, but previously found it really hard to control the number of channel changes. Namely, even with a relatively high MTBC setting (300-600min) and days of uptime, I would still find multiple rapid back-and-forth transitions (e.g. 3 -&amp;gt; 6, 6-&amp;gt;3 within a minute of each other), and quite honestly the MTBC setting didn't seem to do anything.&lt;BR /&gt;&lt;BR /&gt;But this appears to have changed in ZF 9.12. With 9.12, Channelfly is still understandably aggressive at channel-hopping within the first hour or two of uptime, but then it starts noticeably slowing down. Now, with 3 days of uptime and counting, my outdoor AP switches channels every 6 to 10 hours, and my indoor AP's are doing a good job of staying put, especially in 5GHz where there's relatively few neighbors. I have my MTBC set at 300 minutes and it does seem like it's an average of 5+ hours per switch.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I noticed too that the AP syslogs now print the channelfly set MTBC and actual MTBC on each channel switch.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Is this an intentional enhancement to ChannelFly, or am I possibly imagining this behavior?&amp;nbsp;</description>
      <pubDate>Mon, 10 Aug 2015 18:17:12 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37154#M2006</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2015-08-10T18:17:12Z</dc:date>
    </item>
    <item>
      <title>Re: ChannelFly seems less hoppy in 9.12...</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37155#M2007</link>
      <description>Always improving...&amp;nbsp; but I'm not aware of an MTBC problem in earlier releases.</description>
      <pubDate>Mon, 10 Aug 2015 18:21:17 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37155#M2007</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2015-08-10T18:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: ChannelFly seems less hoppy in 9.12...</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37156#M2008</link>
      <description>I previously documented my experiences on FW 9.11:&amp;nbsp;&lt;A href="https://forums.ruckuswireless.com/ruckuswireless/topics/channelfly-and-rapid-channel-changes" rel="nofollow" title="Link: https://forums.ruckuswireless.com/ruckuswireless/topics/channelfly-and-rapid-channel-changes"&gt;https://forums.ruckuswireless.com/ruckuswireless/topics/channelfly-and-rapid-channel-changes&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The outdoor AP definitely sees a lot of 2.4GHz neighbors, but the indoor R600/R700 AP's probably don't.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I'm noticing especially on the indoor AP's that after a initial 6 hour period where it rapidly hops around sampling all the channels, it seems to be a lot more willing to settle on a quiet channel rather than hopping around constantly.&lt;BR /&gt;&lt;BR /&gt;Whether or not there was a problem before, I definitely am finding ChannelFly very usable on 9.12 and don't feel an urge to switch to run-stop mode like I did before &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Mon, 10 Aug 2015 18:27:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/ChannelFly-seems-less-hoppy-in-9-12/m-p/37156#M2008</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2015-08-10T18:27:19Z</dc:date>
    </item>
  </channel>
</rss>

