Ruckus SmartZone, RUCKUS One and ICX
This page configures Ruckus wireless (SmartZone, RUCKUS One, Unleashed, ZoneDirector) to authenticate against Airgate, accept CoA, and send guests to the Airgate portal through a WISPr hotspot. It also covers Ruckus ICX switches.
Before you begin
Section titled “Before you begin”- SmartZone: the control-plane address that sends RADIUS and receives CoA, for example
10.0.0.2. With Use controller as proxy off, the APs send RADIUS from their own addresses. - The Airgate RADIUS address (
203.0.113.10in the examples) and a shared secret. - For guests: the Airgate portal host (for example
airgate.contoso.com) and a guest portal on Guests › Guest portal.
Step 1: Add the controller in Airgate
Section titled “Step 1: Add the controller in Airgate”- Go to Network › Switches and APs › Add device.
- Name
sz1, IP address or subnet10.0.0.2. - Vendor profile: Ruckus SmartZone / RUCKUS One / Unleashed / ZoneDirector. The dictionary becomes
Ruckus, the CoA port3799. - On RADIUS, CoA & RadSec: enter the RADIUS shared secret, keep Require Message-Authenticator in Access-Requests on, turn on RADIUS CoA / Disconnect (RFC 5176).
- Select Save.
Airgate sends CoA to the SmartZone controller address. Its CoA actions for this profile are Disconnect and changing attributes (for example a new Filter-Id mapped to a SmartZone user role).
Step 2: Authentication and accounting services (SmartZone)
Section titled “Step 2: Authentication and accounting services (SmartZone)”- Go to Network › Network Control › Services › AAA (zone or system level) and create an Authentication service:
- Name
Airgate, Protocol RADIUS, Primary server203.0.113.10, port1812, shared secret.
- Name
- Create an Accounting service
Airgate-Acct:203.0.113.10, port1813, same secret. - On the WLAN
Corp-WiFi: Authentication type Standard usage, Method 802.1X EAP, Authentication serviceAirgate, Use controller as proxy on, Accounting serviceAirgate-Acctwith an interim update interval of 10 minutes. - Under Advanced options, turn on Dynamic VLAN when Airgate assigns VLANs.
With Use controller as proxy on, RADIUS comes from the controller, and CoA reaches the controller. Airgate returns VLANs with the RFC 3580 attributes and user roles with Filter-Id or Ruckus-User-Groups; map them to roles under Clients › User roles (or the zone’s user role settings).
For MAC authentication, set the WLAN Method to MAC Address (or 802.1X EAP & MAC) with the same service.
Step 3: Guest WLAN with a WISPr hotspot (optional)
Section titled “Step 3: Guest WLAN with a WISPr hotspot (optional)”- Create a Hotspot (WISPr) portal service:
- Logon URL: External,
https://airgate.contoso.com/portal/<tenant>/<portal>. - Walled garden:
airgate.contoso.com.
- Logon URL: External,
- Create the guest WLAN
Corp-Guestwith Authentication type Hotspot (WISPr), the portal service above, and theAirgateauthentication and accounting services. - Enable the northbound portal interface on the controller so guests can post to it on TCP 9998.
The redirect carries sip (or nbiIP), client_mac, uip, mac, ssid and the original URL. After sign-in, the Airgate portal posts the credentials to https://<sip>:9998/SubscriberPortal/hotspotlogin, and the controller sends a RADIUS PAP request to Airgate.
In Airgate, on the portal’s Login & network section: Vendor handling = Ruckus SmartZone / RUCKUS One (or Auto-detect), Login model = Web login.
Step 4: Ruckus ICX switches
Section titled “Step 4: Ruckus ICX switches”radius-server host 203.0.113.10 auth-port 1812 acct-port 1813 default key <shared-secret> dot1x mac-authip radius source-interface ve 10aaa authentication dot1x default radiusaaa accounting dot1x default start-stop radiusaaa authorization coa enable!authentication auth-default-vlan 10 dot1x enable dot1x enable ethernet 1/1/10 mac-authentication enable mac-authentication enable ethernet 1/1/10 interface ethernet 1/1/10 dot1x port-control autoIn Airgate, add the switch with Vendor profile None (generic) and Vendor (RADIUS dictionary) Brocade (under All RADIUS dictionaries), and use the Brocade RADIUS Enforcement template for roles. CoA uses the generic RFC 5176 packets (Disconnect, changing attributes).
Verify
Section titled “Verify”- Monitor › Sign-in log shows the request from
sz1. - SmartZone Clients › Wireless Clients shows the client with the VLAN or role Airgate sent.
- On Monitor › Connected now, choose Disconnect. The result is
Disconnect-ACK.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| No requests from some APs | Use controller as proxy is off, so APs send RADIUS themselves | Turn the proxy on, or register the AP subnet. |
CoA timeout |
CoA goes to an AP address, or the controller does not accept CoA from Airgate | Send RADIUS through the controller proxy; check the controller’s CoA settings for the AAA service. |
| Hotspot login fails: the controller did not send its address | The redirect has no sip / nbiIP |
Use the controller’s WISPr hotspot with the northbound interface enabled. |
| Portal page does not load | Portal host not in the walled garden | Add it. |