To build a network that delivers solid coverage to both offices, you must solve two problems: First, you must extend...
802.11n WLAN coverage provided by your indoor WLAN, and then you must join two indoor WLANs together with a short outdoor wireless link.
There are at least three ways to extend an 802.11n WLAN inside.
1. You could deploy a wireless repeater to extend the reach of your existing AP. Many inexpensive APs can be configured to operate as repeaters. This is rarely a good solution because it cuts available capacity in half. Think of this as talking to someone on the phone who then repeats what you said to a third person standing near them, then waiting for that person's reply to be repeated to you over the phone. Repeaters are easy, but getting anything accomplished takes much longer.
2. Most businesses build larger indoor WLANs by cabling many wireless APs to the same upstream Ethernet switch or WLAN controller. Each AP uses Ethernet to communicate to the switch/controller and 802.11 to communicate to Wi-Fi clients. All APs advertise the same wireless network name (SSID) and together form a single subnet on which clients can easily roam from one AP to another without significant disruption. This can be accomplished with nearly any residential or enterprise AP. However, if you have more than a few APs in one office, choosing a centrally managed enterprise AP will improve control and reduce total cost of operation.
3. Some businesses build indoor WLANs by deploying wireless APs that can communicate with each other over 802.11. These are typically dual-radio APs that dedicate one radio to communicating with clients and a second radio to communicating to other APs. In order to avoid interference, inter-AP communication often occurs over a 5 GHz "backhaul" channel not used by clients. Some inexpensive consumer APs can be configured to communicate with each other over static wireless bridge links using a method called wireless distribution system (WDS). Some enterprise APs use their own wireless mesh management and routing protocols to automatically form dynamic, optimized, self-healing backhaul links. The resulting wireless mesh may allow APs to communicate directly with each other or APs may route traffic through nearby APs to reach more distant APs. However, at least one "root" AP will still need an Ethernet connection leading to the Internet.
Connecting two WLANs
Now for your second problem: Connecting two indoor WLANs with a short outdoor wireless link. As you might imagine, the indoor bridge and mesh solutions described in option 3 above can easily be extended to cover an outdoor distance of just 125 feet. If you are using WDS, just configure a WDS bridge link between APs positioned at the edge of each network, preferably using directional antennas to focus transmissions between them, keeping data rates high. If you are using a proprietary wireless mesh, follow vendor instructions for deploying outdoor mesh nodes. For example, you may dedicate one AP in each building to serve as the "root" for that building's indoor mesh, and then bridge traffic point to point between root APs. Alternatively, your second building may be small enough and close enough that just deploying one mesh AP there and letting it join the indoor mesh in your main building will do the job.
Finally, you may have heard there is a wireless mesh standard being defined by the IEEE. The draft 802.11s standard specifies a Hybrid Wireless Mesh Protocol used to route 802.11 traffic between cooperating mesh stations with some mesh stations also serving as mesh portals to reach a wired network or the Internet. However, 802.11s is not yet completed, so enterprise wireless mesh APs that you buy today use proprietary protocols.
Related Q&A from Lisa Phifer
The enterprise mobility management market for wearable devices is in its infancy, but IT can still use existing EMM tools to manage wearables.continue reading
Wireless expert Lisa A. Phifer explains to what extent WEP cracking remains a worrisome issue. It all depends on your company's WLAN security policy.continue reading
Wireless expert Lisa A. Phifer explains why you shouldn't stop using 802.1X authentication methods for enterprise WLAN access control.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.