AccessPoint or Router with totally separate guest network (subnet, isolation, dhcp, etc)

jeff_tech

Reputable
May 7, 2015
1
0
4,510
I am searching for an access point or router for a medium size business (35 people, ~100 nodes). I would like the access point or router to have the ability to create a guest wifi network that is totally separate while at the same time allowing the non-guest network to retain access to the LAN resources.

So, the access/point router should have the following features:
--Guest wifi network/SSID
--Isolation mode for guest network to prevent guests from seeing other wifi clients or from seeing LAN resources (servers, PCs, printers, etc) -- BUT ONLY for the guest (the non-guest network needs to be able to access these things)
--Separate subnet for the guest network (preferably)
--Separate DHCP for guest network

Does anyone know of a something that natively (i.e. does this without relying on VLAN tags which would require switch and router support/config of those VLAN tags)?

Thanks,
Jeff
 
Solution
Unless this device is acting as your main internet router you are going to have to have vlans and tagging. Different subnets also tends to be function that will force you into a more commercial product.

The reason you would need vlans is because you need to build a isolated path between the device and your internet router. When you are running in a single router it can be smart enough to keep the data separate but when you have 2 physical devices the data must travel over the same wires and without vlan tags it is mixed.

As pointed out you likely are going to have capacity issues with that many people. This likely means you are going to have to go to a more advanced design that 1 router.
Most mid-range consumer gateways provide for "Guest network", but I doubt consumer-level unit will be able to handle your 35 people / 100 nodes.

I suppose you also want to cover a substantial area with your WiFi network, so you better contact a professional who can do a site survey and offer you a solution.

If you are going to do it by yourself - Ubiquity line of products is a good starting point.
 
Unless this device is acting as your main internet router you are going to have to have vlans and tagging. Different subnets also tends to be function that will force you into a more commercial product.

The reason you would need vlans is because you need to build a isolated path between the device and your internet router. When you are running in a single router it can be smart enough to keep the data separate but when you have 2 physical devices the data must travel over the same wires and without vlan tags it is mixed.

As pointed out you likely are going to have capacity issues with that many people. This likely means you are going to have to go to a more advanced design that 1 router.
 
Solution