Skip to content

Ruckus ZoneDirector

Compatibility

Social WiFi has been tested and is proven to work on the following configurations:

Ruckus ZoneDirector1200 Controller

  • versions above 10.5.0.0 build 190

Access point firmware

  • the same as Controller

An example of working setup consists of a Ruckus R310 Access Point running the same firmware version as Ruckus ZoneDirector1200 controller, which is 10.5.0.0, build 190.

Connecting the device

Connect the Ruckus ZD controller from port 1 on a switch, then connect the PC on which the configuration will take place in such a way that both devices are within the same network.

Accessing the device’s administration panel

Check the IP address received by the controller and log into it from the PC. If the controller has initial configuration on it, it will ask for login and password. If not, it will launch initial configuration procedure. The configuration can be conducted through any web browser.

Device configuration

After logging into the GUI, it is required to configure particular sections.

RADIUS configuration

Services & Profiles → AAA Servers → +Create

Nameswauth
TypeRADIUS
EncryptionLeave unchecked
Auth MethodPAP
Backup RADIUSLeave unchecked
IP Address35.205.62.147
Port31812
Shared SecretRadius Secret available in Access Points tab of the Social WiFi Panel
Confirm SecretCopy above

Leave “Request Timeout” and “Max Number of Retries” at default and press OK.

2023-01-30_14-30.png

Now add the Accounting server:

Configure → AAA Servers → +Create

Nameswaccount
TypeRADIUS Accounting
EncryptionLeave unchecked
Backup RadiusLeave unchecked
IP Address35.205.62.147
Port31813
Shared SecretRadius Secret available in Access Points tab of the Social WiFi Panel
Confirm SecretCopy above

Leave “Request Timeout” and “Max Number of Retries” at default and press OK.

2023-01-30_14-38.png

Configuring Hotspot / DNS Walled Garden

Services & Profiles → Hotspot Services → Create

Namesw_radius
WISPr Smart Client SupportNone
Login Pagehttps://login.socialwifi.com/
Start Pageredirect to the following URL → login.socialwifi.com/redirect/

2023-01-30_14-51.png

Now, switch to the Authentication tab and set up the Authentication/Accounting Servers section as follows:

Authentication Serverswauth
Accounting Serverswaccount

2023-01-30_14-53.png

Now, go to the “Walled Garden” tab and click Create New.

Add the following addresses:

*.socialwifi.com
sw-login.com
connect.facebook.net
www.facebook.com
www.googletagmanager.com
www.googleadservices.com
googleads.g.doubleclick.net
*.youtube.com
*.ytimg.com
*.googlevideo.com
yt3.ggpht.com
accounts.google.*
ssl.gstatic.com
fonts.gstatic.com
fonts.google.com
accounts.youtube.com
*.googleapis.com
apis.google.com
facebook.com
*.facebook.com
*.fbcdn.net
linkedin.com
*.linkedin.com
*.licdn.com
twitter.com
api.twitter.com
x.com
api.x.com
*.twimg.com

2023-01-30_16-46.png

Click OK.

Network configuration

Now, go to “Wireless LANs” and edit or create your Network.

NameType in the name of your network
TypeHotspot Services (WISPr)
Hotspot Servicessw_radius

2023-01-30_16-48.png

Then, open “Advanced Options” section and set the “WLAN Priority” on High.

2023-01-30_16-49.png

Click OK.

Adding the device to Social WiFi platform

In order to add a device to the Social WiFi platform:

  • In the Monitor → Access Points menu, click the AP that you want to add to Social WiFi platform, copy their MAC addresses from AP MAC address field and BSSID column.
  • Access your account at the Social WiFi Panel.
  • Choose the venue to which you would like to add the device.
  • In the “Access Points” tab, press “Add” (upper right corner), paste the MAC address you copied into the form (adding a name is optional) and click “Create”.
  • Restart the device.

Firewall troubleshooting

Symptom: after connecting to the WiFi network, on the last step which is clicking the “Connect to the internet button” you’re not getting connected to the internet.

Solution: it might be the case that you have a firewall that blocks traffic between the WiFi device and the controller. You might either have explicit blocking rules on the firewall, or simply have separate VLANs for the guests and the controller and the traffic between them might be blocked as well. In this case you have to unlock specific ports. For example:

  • TCP 9997