<?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 Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32555#M6102</link>
    <description>Hi Rob,
&lt;BR /&gt;&lt;BR /&gt;
I would suggest creating a test wlan in the clear so you can read the wireless capture and put it on a static VLAN to match the DVLAN is supposed to be assigned to, and see if you can get an IP that way and see if the client sends a DHCP discover.
&lt;BR /&gt;&lt;BR /&gt;
You might want to mirror the AP's port and see if the AP got the Discover packet and if it's sending it out with the proper tag.</description>
    <pubDate>Fri, 11 Oct 2013 23:05:22 GMT</pubDate>
    <dc:creator>sid_sok</dc:creator>
    <dc:date>2013-10-11T23:05:22Z</dc:date>
    <item>
      <title>Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32554#M6101</link>
      <description>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.
&lt;BR /&gt;&lt;BR /&gt;
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.
&lt;BR /&gt;&lt;BR /&gt;
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.
&lt;BR /&gt;&lt;BR /&gt;
Wireshark shows no DHCP broadcast request from the client at all.
&lt;BR /&gt;&lt;BR /&gt;
The switchport for the AP is a trunk, with the VLAN tagged and allowed.
&lt;BR /&gt;&lt;BR /&gt;
Any assistance would be greatly appreciated!
&lt;BR /&gt;
Rob</description>
      <pubDate>Fri, 11 Oct 2013 21:59:33 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32554#M6101</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2013-10-11T21:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32555#M6102</link>
      <description>Hi Rob,
&lt;BR /&gt;&lt;BR /&gt;
I would suggest creating a test wlan in the clear so you can read the wireless capture and put it on a static VLAN to match the DVLAN is supposed to be assigned to, and see if you can get an IP that way and see if the client sends a DHCP discover.
&lt;BR /&gt;&lt;BR /&gt;
You might want to mirror the AP's port and see if the AP got the Discover packet and if it's sending it out with the proper tag.</description>
      <pubDate>Fri, 11 Oct 2013 23:05:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32555#M6102</guid>
      <dc:creator>sid_sok</dc:creator>
      <dc:date>2013-10-11T23:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32556#M6103</link>
      <description>DVLANs work no problem. You are probably having networking issues. You must not tagg all VLANs on a port. Suggest you use management VLAN untagged and others tagged.</description>
      <pubDate>Mon, 14 Oct 2013 06:23:52 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32556#M6103</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2013-10-14T06:23:52Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32557#M6104</link>
      <description>Write a comment...</description>
      <pubDate>Tue, 15 Oct 2013 17:21:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32557#M6104</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2013-10-15T17:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32558#M6105</link>
      <description>Sid,
&lt;BR /&gt;&lt;BR /&gt;
I did as you suggested and created a test WLAN with a static VLAN matching the DVLAN I am testing. The client associated and the DHCP request is seen in the packet capture, and the client receives an IP address assignment for the correct VLAN.
&lt;BR /&gt;&lt;BR /&gt;
Rob</description>
      <pubDate>Tue, 15 Oct 2013 17:27:29 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32558#M6105</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2013-10-15T17:27:29Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32559#M6106</link>
      <description>&lt;A href="http://forums-archive.ruckuswireless.com/forums/8/topics/1278" rel="nofollow"&gt;http://forums-archive.ruckuswireless....&lt;/A&gt;
&lt;BR /&gt;&lt;BR /&gt;
It might be a good idea to provide this information in the documentation for ZoneDirector and DVLAN configuration.</description>
      <pubDate>Tue, 15 Oct 2013 19:53:47 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32559#M6106</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2013-10-15T19:53:47Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32560#M6107</link>
      <description>Is what you needed in here as well? &lt;A href="https://support.ruckuswireless.com/answers/000002109" rel="nofollow"&gt;https://support.ruckuswireless.com/an...&lt;/A&gt;
&lt;BR /&gt;&lt;BR /&gt;
What was the "missing piece"?</description>
      <pubDate>Tue, 15 Oct 2013 19:58:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32560#M6107</guid>
      <dc:creator>keith_redfield</dc:creator>
      <dc:date>2013-10-15T19:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Vlan Assignment via RADIUS (Microsoft NPS) - DHCP Failure</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32561#M6108</link>
      <description>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.</description>
      <pubDate>Tue, 15 Oct 2013 20:03:55 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Dynamic-Vlan-Assignment-via-RADIUS-Microsoft-NPS-DHCP-Failure/m-p/32561#M6108</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2013-10-15T20:03:55Z</dc:date>
    </item>
  </channel>
</rss>

