<?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 Using DHCP on the Zone Director in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36743#M6591</link>
    <description>Hi I am new to Ruckus and am wondering the following. Since we are very low on network IP addresses in the AD DHCP, can I have the Ruckus DHCP give out IPs for just wireless clients and will it route to the corporate network? I hope I am clear with what I am trying to accomplish here. Let me know. Thank you.</description>
    <pubDate>Wed, 23 Aug 2017 20:23:30 GMT</pubDate>
    <dc:creator>steven_rizkalla</dc:creator>
    <dc:date>2017-08-23T20:23:30Z</dc:date>
    <item>
      <title>Using DHCP on the Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36743#M6591</link>
      <description>Hi I am new to Ruckus and am wondering the following. Since we are very low on network IP addresses in the AD DHCP, can I have the Ruckus DHCP give out IPs for just wireless clients and will it route to the corporate network? I hope I am clear with what I am trying to accomplish here. Let me know. Thank you.</description>
      <pubDate>Wed, 23 Aug 2017 20:23:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36743#M6591</guid>
      <dc:creator>steven_rizkalla</dc:creator>
      <dc:date>2017-08-23T20:23:30Z</dc:date>
    </item>
    <item>
      <title>Re: Using DHCP on the Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36744#M6592</link>
      <description>Hi Steven,&lt;BR /&gt;&lt;BR /&gt;The Internal DHCP server on the ZD has limited ability, when you enable it; even wired clients connected on the same VLAN as ZD/AP would get IP address. It does not have routing option so it has to be done on the Wired End.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Abilash PR.</description>
      <pubDate>Wed, 23 Aug 2017 21:16:46 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36744#M6592</guid>
      <dc:creator>abilash_p_r</dc:creator>
      <dc:date>2017-08-23T21:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Using DHCP on the Zone Director</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36745#M6593</link>
      <description>Like Abilash said, it would give up and see my dresses as your ad DHCP. Having a duplicate IP addresses on your network is never a good thing.
&lt;BR /&gt;&lt;BR /&gt;
The best thing that you could do is create a separate VLAN for your wireless clients. Then you can have your ad DHCP server and out a whole new set of IP addresses. If you want me have layer 2 switches and an additional VLAN is not possible you can always extend your network out a larger subnet.</description>
      <pubDate>Wed, 23 Aug 2017 23:38:34 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Using-DHCP-on-the-Zone-Director/m-p/36745#M6593</guid>
      <dc:creator>tim_morton_7322</dc:creator>
      <dc:date>2017-08-23T23:38:34Z</dc:date>
    </item>
  </channel>
</rss>

