<?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 What is the SOLO firmware for? in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/What-is-the-SOLO-firmware-for/m-p/16777#M4383</link>
    <description>Been trying to figure out what exactly the SOLO firmware is for. &amp;nbsp;I have just one R500 AP. &amp;nbsp;I've searched the forums, FAQ and Google, but there is nothing that explicitly states what the SOLO firmware is for.</description>
    <pubDate>Mon, 02 Oct 2017 15:32:03 GMT</pubDate>
    <dc:creator>donald_scott_bm</dc:creator>
    <dc:date>2017-10-02T15:32:03Z</dc:date>
    <item>
      <title>What is the SOLO firmware for?</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/What-is-the-SOLO-firmware-for/m-p/16777#M4383</link>
      <description>Been trying to figure out what exactly the SOLO firmware is for. &amp;nbsp;I have just one R500 AP. &amp;nbsp;I've searched the forums, FAQ and Google, but there is nothing that explicitly states what the SOLO firmware is for.</description>
      <pubDate>Mon, 02 Oct 2017 15:32:03 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/What-is-the-SOLO-firmware-for/m-p/16777#M4383</guid>
      <dc:creator>donald_scott_bm</dc:creator>
      <dc:date>2017-10-02T15:32:03Z</dc:date>
    </item>
    <item>
      <title>Re: What is the SOLO firmware for?</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/What-is-the-SOLO-firmware-for/m-p/16778#M4384</link>
      <description>Hi Donald,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; We ship a '901--US00' part number AP with Solo/Standalone firmware, like 104.0.0.0.1347 that&lt;BR /&gt;looks like an AP WebUI interface when you login with default 'super'/'sp-admin' credentials.&amp;nbsp; You can configure&lt;BR /&gt;individual SSIDs on both 2.4g and 5g radios (16 each) and they assume you have a DHCP server and Def-gw&lt;BR /&gt;router on the network.&amp;nbsp; This Solo AP firmware will also allow the AP to connect to a ZoneDirector or SmartZone&lt;BR /&gt;controller, via DHCP option 43, DNS, set director AP command, etc.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; The '9U1--US00' part number APs ship with our Unleashed firmware (currently 200.4.9.13.47) and&lt;BR /&gt;the code will not look at the DHCP/DNS options or join a ZD/SZ controller, they will look for an existing Unleashed&lt;BR /&gt;network or advertise their Configure SSID to allow you to connect and create one.&amp;nbsp; An Unleashed AP network can&lt;BR /&gt;exist on the same LAN as ZD/SZ (like in my office lab), though not a typical deployment.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; You *can* do a factory default on an AP running any code, access it via default IP, and install/upgrade/change&lt;BR /&gt;the code to Solo or Unleashed, as you have need or for testing.&amp;nbsp; But Support contracts (opening a case with Ruckus) &lt;BR /&gt;is different between a Controller based network (support for ZD/SZ) or Unleashed (support for up to 25 APs).&amp;nbsp; If&lt;BR /&gt;you ever need an RMA (return material authorization), you will receive a same '901' or '9U1' replacement AP, no&lt;BR /&gt;matter what code you were using on it.&amp;nbsp; Is that helpful?</description>
      <pubDate>Mon, 02 Oct 2017 17:10:21 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/What-is-the-SOLO-firmware-for/m-p/16778#M4384</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-10-02T17:10:21Z</dc:date>
    </item>
  </channel>
</rss>

