Wireless LAN

By Nextoption7 ·
How do I achieve the following?
This is what I want to achieve.
I have two network segments used by two different departments that should not have access to each other by any means. The security I need to deploy will prevent users from one segment from accessing anything on the other segment. I wish to use Cisco Aironet Access Point to achieve this.
The work environment is not too far from the residential environment. I want to provide the two department's office network to the residential separately. I intend using one Cisco Aironet access point to trasport the two RF and another one to distribute at the residential.
Now my troubles are these:
1.How di I transmit the two department???s wireless signal with one access point, is there possibility?
2.How do I setup the access point for bridging in case if I should use more than one and how would the wireless broadcast/distribution be attained?
3.What network gadget do I need apart from the cisco aironet and where should they be installed (amplifier, firewall et al).
4.What RF spectrum, 2.4GHz, 5.8GHz, do I use for bridging and broadcasting?
Please do not be upset by some non-professional statements I might have made, kindly give me a helping hand. I love to share in your expertise, experience and your professional advice.
I thought of IEEE 802.11n which have the ability of multiple inputs multiple output antenna (MIMO) but I do not have full understanding of how it works. Could it be multiple input signal from different source or multiples input signal from one or many access point but for one network.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Without going into all the design possibilities, a couple of thoughts

by robo_dev In reply to Wireless LAN

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.

Related Discussions

Related Forums