Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure

[rob_coote]

I'm in the process of consolidating a large number of SSID's into a single SSID using dynamic VLANS. I have followed the Ruckus documentation for configuring the appropriate attributes on the RADIUS server, and have an SSID set up for dynamic vlans on the Zonedirector.

My test clients connect to the SSID, and are prompted for credentials. I can see the credentials accepted on the NPS server, and wireshark confirms the Access-Accept message contains the Tunnel-Private-Group-ID value for the desired VLAN.

At this point the client stalls trying to get a DHCP lease. The DHCP server is working, as these are existing scopes and subnets and I can connect a wired client into the switch on an access port for the same vlan and get a lease.

Wireshark shows no DHCP broadcast request from the client at all.

The switchport for the AP is a trunk, with the VLAN tagged and allowed.

Any assistance would be greatly appreciated!
Rob

[rob_coote]

http://forums-archive.ruckuswireless....

It might be a good idea to provide this information in the documentation for ZoneDirector and DVLAN configuration.

[keith_redfield]

Is what you needed in here as well? https://support.ruckuswireless.com/an...

What was the "missing piece"?

[rob_coote]

The vendor-specific attribute piece in NPS was required. It appears that NPS does not return AD groups to the ZoneDirector, so everything got dumped into the "Default" role. Adding the VSA (25053) with the AD group to match the ZD role appears to have resolved the issue in my test lab so far.