<?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 Force DHCP disconnecting large number of clients with valid IP addresses in SmartZone and Virtual SmartZone</title>
    <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Force-DHCP-disconnecting-large-number-of-clients-with-valid-IP/m-p/105283#M5910</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have a vSZ with 180 APs split across 2 zones and multiple subnets with 600 - 1000 clients. I am utilizing R700 APs. I have an issue where clients were sticking with an IP address of one subnet after successfully roaming from one building's subnet to another. I looked around and found the Force DHCP option which looked like it did the trick, however I am getting A LOT of Force DHCP disconnection events.&lt;/P&gt;&lt;P&gt;I can confirm the Force DHCP option did handle the clients that were stuck on the wrong subnet, but there appears to be a lot of clients that have valid IP addresses on the correct subnet that are also getting kicked off.&lt;/P&gt;&lt;P&gt;I am using external DPSK authentication for this network. I've also had a couple people with multiple devices which were able to join the network on 4 of 5 devices and the other just lagged and then refused to connect. I confirmed the 5th device was getting kicked due to the Force DHCP option. I had the person connect to an alternative WLAN with same authentication but no Force DHCP option enabled and it connected fine.&lt;/P&gt;&lt;P&gt;Does anyone have some insight as to how the SmartZone or APs apply this option? A few things that are not immediately clear are:&lt;/P&gt;&lt;P&gt;1) How does the SmartZone judge if a device got a valid DHCP address?&lt;/P&gt;&lt;P&gt;2) What occurs that causes the SmartZone (or AP?) to start the timeout counter for getting a valid DHCP address?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Otherwise, any other suggestions on how to either fix this Force DHCP issue or to get rid of my "sticky client to a subnet" issue would be very appreciated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 10 May 2025 16:01:19 GMT</pubDate>
    <dc:creator>kyle_connor</dc:creator>
    <dc:date>2025-05-10T16:01:19Z</dc:date>
    <item>
      <title>Force DHCP disconnecting large number of clients with valid IP addresses</title>
      <link>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Force-DHCP-disconnecting-large-number-of-clients-with-valid-IP/m-p/105283#M5910</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have a vSZ with 180 APs split across 2 zones and multiple subnets with 600 - 1000 clients. I am utilizing R700 APs. I have an issue where clients were sticking with an IP address of one subnet after successfully roaming from one building's subnet to another. I looked around and found the Force DHCP option which looked like it did the trick, however I am getting A LOT of Force DHCP disconnection events.&lt;/P&gt;&lt;P&gt;I can confirm the Force DHCP option did handle the clients that were stuck on the wrong subnet, but there appears to be a lot of clients that have valid IP addresses on the correct subnet that are also getting kicked off.&lt;/P&gt;&lt;P&gt;I am using external DPSK authentication for this network. I've also had a couple people with multiple devices which were able to join the network on 4 of 5 devices and the other just lagged and then refused to connect. I confirmed the 5th device was getting kicked due to the Force DHCP option. I had the person connect to an alternative WLAN with same authentication but no Force DHCP option enabled and it connected fine.&lt;/P&gt;&lt;P&gt;Does anyone have some insight as to how the SmartZone or APs apply this option? A few things that are not immediately clear are:&lt;/P&gt;&lt;P&gt;1) How does the SmartZone judge if a device got a valid DHCP address?&lt;/P&gt;&lt;P&gt;2) What occurs that causes the SmartZone (or AP?) to start the timeout counter for getting a valid DHCP address?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Otherwise, any other suggestions on how to either fix this Force DHCP issue or to get rid of my "sticky client to a subnet" issue would be very appreciated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 10 May 2025 16:01:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/SmartZone-and-Virtual-SmartZone/Force-DHCP-disconnecting-large-number-of-clients-with-valid-IP/m-p/105283#M5910</guid>
      <dc:creator>kyle_connor</dc:creator>
      <dc:date>2025-05-10T16:01:19Z</dc:date>
    </item>
  </channel>
</rss>

