Avoiding huge broadcast domains

[temur_kalandia]

hello,
For avoiding huge broadcast domains will be great if Ruckus has the feature "vlan range" or "vlan pooling" (it has different naming depending on vendor). with that feature you can configure one SSID and bind to it Vlan ranges. in such way each time when user connects to that SSID it will get an IP address from the different vlan.
One of our costumer has about 5k user in one building. they used above mentioned feature with previous vendor AP's. After migrating to Ruckus wireless we sew that there no such feature, with ruckus you have two options to avoid huge broadcast domains : 1) configure different ssid with the different VLAN , with causes clients to reconnect when they change location in the same building(NOT good idea ) , 2) create wlan groups and bind different vlan to the same SSID, which causes disconnections when roaming occurs, clients sometimes have to disconnect and reconnect(NOT good).

So if there anyone interested in that feature ,please give a support and may be w'll see it in near releases.

regards

[rahul_koul]

To all,

The feature of VLAN pooling will be available in version 9.9 so please wait until the release is made public. As of now we do not have any ETA for it.

-Rahul

[daniel_kuchensk]

Great, thanks for the update Rahul!

[michael_brado]

Another cause of broadcast flooding has been determined to be bad Intel NICs that
spew IPv6 discover packets. Simply configuring ZD/APs as IPv4-only does not help.
We still have to inspect all packets. If IPv6 is not important to applications used,
please filter at higher level routers/switches.