<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>R610 on Andrew's Memory Blog</title><link>https://andrewmemory.acornwall.net/tags/r610/</link><description>Recent content in R610 on Andrew's Memory Blog</description><generator>Hugo -- gohugo.io</generator><image><url>https://andrewmemory.acornwall.net/img/rss_image.png</url><title>R610 on Andrew's Memory Blog</title><link>https://andrewmemory.acornwall.net/</link></image><language>en</language><managingEditor>andrewmemoryblog@gmail.com (Andrew's Memory Blog)</managingEditor><webMaster>andrewmemoryblog@gmail.com (Andrew's Memory Blog)</webMaster><copyright>Copyright 2009--2025</copyright><lastBuildDate>Sat, 15 Aug 2026 22:11:15 -0700</lastBuildDate><atom:link href="https://andrewmemory.acornwall.net/tags/r610/index.xml" rel="self" type="application/rss+xml"/><item><title>Making Ruckus Unleashed faster when the network drops</title><link>https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/</link><pubDate>Sat, 15 Aug 2026 22:11:15 -0700</pubDate><author>andrewmemoryblog@gmail.com (Andrew's Memory Blog)</author><guid>https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/</guid><description>&lt;p&gt;I&amp;rsquo;ve been using Ruckus Unleashed network devices (R610 and R710) and I&amp;rsquo;ve been pretty happy with them. However, they do have a problem: when the network drops (and Cox does it pretty frequently) it takes a while to reestablish the connection. It&amp;rsquo;s bad enough that I&amp;rsquo;ve got a Unify AP running just so I can reconnect.&lt;/p&gt;
&lt;h2 class="relative group"&gt;Making the mesh static
&lt;div id="making-the-mesh-static" class="anchor"&gt;&lt;/div&gt;
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
&lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#making-the-mesh-static" aria-label="Anchor"&gt;#&lt;/a&gt;
&lt;/span&gt;
&lt;/h2&gt;
&lt;p&gt;Part of the problem is that I&amp;rsquo;m running on a mesh access point, and it&amp;rsquo;s possible that the mesh is &lt;a href="https://support.ruckuswireless.com/articles/000003602" target="_blank" rel="noreferrer"&gt;busy reconfiguring itself&lt;/a&gt; because of the lack of network. So I decided to lock things down a little — there are some access points that will never change roles unless I move them around or change the underlying hardware.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m using firmware 200.15.6.212.27 (the last one before EOL). This documents what I did.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Log into the Ruckus management screen from a hard-wired port, then click on &amp;ldquo;Access Points.&amp;rdquo; For each access point, click on it, then click the &amp;ldquo;Edit&amp;rdquo; button and then the &amp;ldquo;Mesh&amp;rdquo; tab. This is what things looked like for all the APs before I started messing around:&lt;/li&gt;
&lt;/ol&gt;
&lt;figure&gt;&lt;img
class="my-0 rounded-md"
loading="lazy"
decoding="async"
fetchpriority="auto"
alt="The Mesh tab is selected. Mesh Mode is Auto, Uplink Selection is Smart, and Max Hops is Unlimited"
width="578"
height="217"
src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/before-changes.png"
srcset="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/before-changes.png 800w, https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/before-changes.png 1280w"
sizes="(min-width: 768px) 50vw, 65vw"
data-zoom-src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/before-changes.png"&gt;&lt;/figure&gt;
&lt;ol start="2"&gt;
&lt;li&gt;My Master AP is plugged into the switch. So I configured it as a Root AP:&lt;/li&gt;
&lt;/ol&gt;
&lt;figure&gt;&lt;img
class="my-0 rounded-md"
loading="lazy"
decoding="async"
fetchpriority="auto"
alt="The Mesh tab is selected. Mesh Mode is Root AP, there is no Uplink Selection available, and Max Hops is Unlimited"
width="477"
height="143"
src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png"
srcset="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png 800w, https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png 1280w"
sizes="(min-width: 768px) 50vw, 65vw"
data-zoom-src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png"&gt;&lt;/figure&gt;
&lt;p&gt;After doing this, I got a dialog: &amp;ldquo;Warning: Changing Mesh mode will make Master AP reboot to take effect. Are you sure you want to continue?&amp;rdquo; Time to click &amp;ldquo;Yes&amp;rdquo;. Then snooze a bit until the AP is back online. Once it rebooted, I had to log into the Ruckus admin software again. At this point all my other APs were disconnected.&lt;/p&gt;
&lt;ol start="3"&gt;
&lt;li&gt;My Root AP is also plugged into the switch. It gets to be a Root AP as well:&lt;/li&gt;
&lt;/ol&gt;
&lt;figure&gt;&lt;img
class="my-0 rounded-md"
loading="lazy"
decoding="async"
fetchpriority="auto"
alt="The Mesh tab is selected. Mesh Mode is Root AP, there is no Uplink Selection available, and Max Hops is Unlimited"
width="477"
height="143"
src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png"
srcset="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png 800w, https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png 1280w"
sizes="(min-width: 768px) 50vw, 65vw"
data-zoom-src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/root-ap.png"&gt;&lt;/figure&gt;
&lt;p&gt;Important: I needed to remember the last two digits of the MAC (:60).&lt;/p&gt;
&lt;ol start="4"&gt;
&lt;li&gt;My (sole) mesh AP is on the other side of the house. For it, I tell it explicitly to run as a Mesh AP and connect to the Root AP (not the Master AP) by MAC address:&lt;/li&gt;
&lt;/ol&gt;
&lt;figure&gt;&lt;img
class="my-0 rounded-md"
loading="lazy"
decoding="async"
fetchpriority="auto"
alt="The Mesh tab is selected. Mesh Mode is Mesh AP, the Uplink Selection is Manual, and there are three MAC addresses with check boxes and signal reports. Only the third check box, the MAC that ends in :60, has its check-box checked. Max Hops is Unlimited"
width="580"
height="290"
src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/mesh-ap.png"
srcset="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/mesh-ap.png 800w, https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/mesh-ap.png 1280w"
sizes="(min-width: 768px) 50vw, 65vw"
data-zoom-src="https://andrewmemory.acornwall.net/blog/2026-08-15-making-unleashed-faster-when-network-drops/images/mesh-ap.png"&gt;&lt;/figure&gt;
&lt;p&gt;As you update each AP, it goes offline and then (eventually) comes back. Don&amp;rsquo;t panic. Eventually they will all come up and you can edit them one at a time.&lt;/p&gt;
&lt;h2 class="relative group"&gt;This is only a theory
&lt;div id="this-is-only-a-theory" class="anchor"&gt;&lt;/div&gt;
&lt;span
class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
&lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#this-is-only-a-theory" aria-label="Anchor"&gt;#&lt;/a&gt;
&lt;/span&gt;
&lt;/h2&gt;
&lt;p&gt;I haven&amp;rsquo;t tried taking the network down and testing it. (Cox will do that soon enough&amp;hellip;) However, this should prevent needless re-negotiation as devices try to figure out who they are based on connectivity.&lt;/p&gt;</description></item></channel></rss>