Ruckus IP addresses - additional DHCP server?

[Ignatius]

I work with a non-educational organisation and we have a Ruckus ZoneDirector 1000. The management IP address is on the 192.168.2.0 network and it works with several Ruckus Access Points (also on the 192.168.2.0 network). Together, they hand out addresses on the main network (192.168.3.0 / 24) from DHCP on our domain controller and these wireless devices can be accessed from our workstations on the main network.

 

Increasingly, we run out of IP addresses so have to disable guest WiFi and we're looking into ways of getting around this. Ideally, we'd like to have a separate DHCP server handing out addresses to WiFi clients but it doesn't look like this is a possibility. I realise the ultimate solution is to revamp the entire network address scheme but that's something that my colleague and I would like to avoid as it was set up some time ago by an external organisation (no longer involved) and some parts are quite difficult to understand.

 

Does anyone have any recommendations? I'd add that some staff use mobile devices and need access to resources on the main network (192.168.3.0 / 24) but the majority of staff and all visitors only require access to the internet.

 

Thanks for your time!

[Blue_Cookeh]

I work with a non-educational organisation and we have a Ruckus ZoneDirector 1000. The management IP address is on the 192.168.2.0 network and it works with several Ruckus Access Points (also on the 192.168.2.0 network). Together, they hand out addresses on the main network (192.168.3.0 / 24) from DHCP on our domain controller and these wireless devices can be accessed from our workstations on the main network.

 

Increasingly, we run out of IP addresses so have to disable guest WiFi and we're looking into ways of getting around this. Ideally, we'd like to have a separate DHCP server handing out addresses to WiFi clients but it doesn't look like this is a possibility. I realise the ultimate solution is to revamp the entire network address scheme but that's something that my colleague and I would like to avoid as it was set up some time ago by an external organisation (no longer involved) and some parts are quite difficult to understand.

 

Does anyone have any recommendations? I'd add that some staff use mobile devices and need access to resources on the main network (192.168.3.0 / 24) but the majority of staff and all visitors only require access to the internet.

 

Thanks for your time!

 

Stick your guest network on a new SSID which is on a new VLAN (which you should be doing anyway!). This will use a new subnet so you can free up addresses on your old one, and give as many as you need to your guest network.

 

If you have managed switches (HP and Cisco do this I know) you can tell them to forward DHCP requests from one VLAN to another so you can just add a new scope in your existing DHCP server.

[ITGuyWestMidlands]

Id go for two vlans. One for guests and one for staff byod. Use acl rules to block the guest vlan touching the main network. Give the byod vlan access to those servers \ ports needed on the main network

[Ignatius]

Yes, I guess VLANs are the way to go but, as I said, it was all set up by an external organisation and the configuration paperwork isn't available so I'd be flying by the seat of my pants. I might just have to grit my teeth and do some tweaking ... hoping that I don't make some foul up that takes a while to resolve!