Showing results for 
Search instead for 
Did you mean: 

SSID goes Off if internet down - Unleashed



If the unleashed master detects that the internet is down,  it disables all SSIDs.  (ive noticed this functionality across all Unleashed FW Versions , and over past several years of unleashed)

(this function being forced ON is unique to ruckus + unleashed only, and not other manufactures in my experience- on ruckus ZD and vSZ line you can disable this.  on standalone FW it does not exist in the first place (good!) ).

Is there anyway to disable this on Unleashed FW?  (even if via cli?)

I dont understand how this is a feature being enabled is helpful,  in fact it causes many problems, such as:

If ISP internet is out, almost always the local DHCP-server is still live (the defGW / main router) , thus devices are still getting IPs and communicate intranet with each other.

as a result of ruk/unleashed turning off SSIDs:

  • Customers/support cant access the main router / default gateway without physically plugging in ethernet (many modern client devices require USB-> ethernet adaptors, if they even support PHY ethernet at all)
  • Customers/support also cant access the actual ruk APs / unleashed master without physically plugging in ethernet.
  • Local users can now not even PRINT, as most modern printers are accessed over the network.  (so even if a user has a LTE or hotspot connection to get the internet, they now have no way at all to access their printer)
  • Sonos / Speaker systems (to play local sources) now dont work.

I simply dont see any rational/upside to this function being forced upon users. 

If Ruckus wants to make it a feature that can enabled/disabled - fine  (actually that would be the best case, as some may have a usecase for this, but most would not want it).

Perhaps i am missing something?   if so, please let me know.

Thank you!


thanks vesalius,  i also generally try to use Static-IPs on all APs as well.

I did want to link to this thread, as a possible solution for others with this issue.  (possible fix is to DISABLE the internet-check via a CLI command)  see here:

other, more recent post: