+ 0 Votes Without going into all the design possibilities, a couple of thoughts robo_dev 2 years ago First of all, at a high level, you should consider a managed wireless network (e.g. Cisco Wireless LAN Controller or AeroHive, or Aruba) vs old-school autonomous access points. Aerohive does what Cisco WLAN Controller does ( a lot cheaper), and handles both the AP-to-AP communication/roaming AND the backhaul/mesh topology needed for many environments (while still being centrally managed). (I am a big Cisco fan, but recently deployed Aerohive). Second, you CAN do separate wireless VLANs to map to separate Wired VLANs.....HOWEVER, there are two issues, scalability and supportability. While Cisco Aironet APs are great units, there are limits in terms of number of concurrent users, throughput, etc. In general, it's far better to make separate wireless networks be on separate devices. At a high level, you can do both bridging and provide local WLAN access on an autonomous access point, but if you do this with an AP with one radio, your throughput suffers. You can use an AP that does the bridging on one radio/frequency and the local access on another radio/frequency, but then you do have one huge single point of failure. Therefore the best solution is often to use a separate dedicated WLAN bridge for bridging and APs for local WLAN access. But then you circle back to configuring/managing/deploying such a solution, and then a Cisco WLAN controller or Aerohive starts to look very attractive.