<?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: Ruckus As DHCP Server ???? in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40012#M7091</link>
    <description>Hi,&lt;BR /&gt;I dont think using DHCP by ZD3000 is a good option.&lt;BR /&gt;Even Ruckus just recommend that only use DHCP built-in in a lab or small environment.&lt;BR /&gt;What is your requirement for the wireless? Perhaps I can help.</description>
    <pubDate>Tue, 18 Aug 2015 03:03:18 GMT</pubDate>
    <dc:creator>hoang_tung_7073</dc:creator>
    <dc:date>2015-08-18T03:03:18Z</dc:date>
    <item>
      <title>Ruckus As DHCP Server ????</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40011#M7090</link>
      <description>Can the ruckus zonedirector 3000 be used in a large wireless environment? It was an option that was brought up today during our pre-install discussions. I was under the understanding that the the zd dhcp server is very limited and not recommended. We have a dhcp running and I was going to use that until this option was presented. In a way it would seem easier to allow the ruckus equipment to handle the wireless side. I just don't see it happening though. We are looking at 4 ssid's and the equipment doesn't seem to be able to provide dhcp scopes. I don't want to find out later it won't work and I have to scramble to get our dhcp server configured.&lt;BR /&gt;&lt;BR /&gt;Thank you</description>
      <pubDate>Tue, 18 Aug 2015 02:16:53 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40011#M7090</guid>
      <dc:creator>ehctechy730</dc:creator>
      <dc:date>2015-08-18T02:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: Ruckus As DHCP Server ????</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40012#M7091</link>
      <description>Hi,&lt;BR /&gt;I dont think using DHCP by ZD3000 is a good option.&lt;BR /&gt;Even Ruckus just recommend that only use DHCP built-in in a lab or small environment.&lt;BR /&gt;What is your requirement for the wireless? Perhaps I can help.</description>
      <pubDate>Tue, 18 Aug 2015 03:03:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40012#M7091</guid>
      <dc:creator>hoang_tung_7073</dc:creator>
      <dc:date>2015-08-18T03:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: Ruckus As DHCP Server ????</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40013#M7092</link>
      <description>I was planning to use our windows dhcp server, but when using ZD as the wireless dhcp server was presented by the installers it seemed to make sense. From what I read though, it didn't seem like a good option.You confirmed what I was thinking. We are replacing our current wireless network with Ruckus. I am trying to get ground work layed so that when they come in to do the install things are in place(dhcp, vlans, etc..)</description>
      <pubDate>Tue, 18 Aug 2015 19:54:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40013#M7092</guid>
      <dc:creator>ehctechy730</dc:creator>
      <dc:date>2015-08-18T19:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: Ruckus As DHCP Server ????</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40014#M7093</link>
      <description>The local DHCP server on ZD can only provide IPs from it's subnet, and is really intended &lt;BR /&gt;for bringing up local APs, or use in a limited scale SMB where everyone is trusted.&amp;nbsp; We&lt;BR /&gt;recommend keeping ZD/APs on their own VLAN/subnet, and assigning client VLANs to&lt;BR /&gt;your WLAN traffic. &lt;BR /&gt;&lt;BR /&gt;For true Enterprise+ deployments, a company should plan to provide DHCP server(s) for &lt;BR /&gt;each client VLAN.&amp;nbsp; Often, these are Win servers with AD/AAA as well.</description>
      <pubDate>Tue, 18 Aug 2015 20:46:48 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40014#M7093</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2015-08-18T20:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: Ruckus As DHCP Server ????</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40015#M7094</link>
      <description>That was my thinking. Vlans on the switches with scopes for each created on our current dhcp server. Thank you</description>
      <pubDate>Tue, 18 Aug 2015 20:50:07 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Ruckus-As-DHCP-Server/m-p/40015#M7094</guid>
      <dc:creator>ehctechy730</dc:creator>
      <dc:date>2015-08-18T20:50:07Z</dc:date>
    </item>
  </channel>
</rss>

