19 Wireless Technologies Flashcards
Wireless Personal Area Network (WPAN)
Bluetooth is by far the most popular type of PAN. PANs are low power, they cover short distances, and they’re small. You can stretch one of these to cover about 30 feet max, but most devices on a PAN have a short reach, making them popular for small and/or home offices.
Wireless LAN (WLAN)
Wireless LANs (WLANs) were created to cover longer distances and offer higher bandwidth than PANs. They’re the most popular type of wireless networks in use today. The ideal for a WLAN is to have many users connect to the network simultaneously, but this can cause interference and collisions because the network’s users are all competing for the same bandwidth. Like PANs, WLANs use an unlicensed frequency band, which means you don’t have to pay for the frequency band in order to transmit. And again, this attribute has resulted in an explosion of new development in the WLAN arena.
Wireless Metro Area Network (WMAN)
Wireless metro area networks (WMANs) cover a fairly large geographic area like a city or small suburb. They’re becoming increasingly common as more and more products are introduced into the WLAN sector, causing the price tag to drop. You can think of WMANs as low-budget, bridging networks. They’ll save you some real cash compared to shelling out for much more costly leased lines, but there’s a catch: to get
your discount long-distance wireless network to work, you’ve got to have a line of sight between each hub or building. Fiber connections are ideal to build an ultra-solid network backbone with, so go with them if they’re available in your area. If your ISP doesn’t offer the fiber option, or you just don’t have the cash for it, a WMAN is a perfectly fine, economical alternative for covering
something like a campus or another large area so long as you’ve got that vital line of sight factor in check!
Wireless Wide Area Network (WWAN)
So far, it’s very rare to come across a wireless wide area network (WWAN) that can provide you with WLAN speeds, but there sure is a lot of chatter about them. A good example of a WWAN would be the latest cellular networks that can transmit data at a pretty good clip. But even though WWANs can certainly cover plenty of area, they’re still not speedy enough to replace our ubiquitous WLANs. Some people—especially those shilling stuff on TV—claim to adore their infallible, turbo-charged cellular networks. These terminally happy people are usually watching high-speed video while uploading images and gaming on their smart phones, but I don’t know anyone who lives outside the TV who actually gets that kind of speed. And as for that “coverage anywhere” schtick? Off the set, dead zones and frozen phones are just reality for now. It’s possible we’ll see more efficiency and growth for WWANs soon, but since WWANs are used to provide connectivity over a really large geographic area, it follows that implementing one will separate your cell service provider from a large quantity of cash. So it’s going to come to motivation—as more people demand this type of service and are willing to pay for it, cellular companies will gain the resources to expand and improve upon these exciting networks. Another set of positives in favor of WWAN growth and development: They meet a lot of business requirements, and technology is growing in a direction that the need for this type of long-distance wireless network is getting stronger. So it’s a fairly good bet connectivity between a WLAN and a WWAN will be critical to many things in our future. For instance, when we have more IPv6 networks, the “pass-off” between these two types of networks may be seamless.
Wireless Access Points
A component that connects all wireless devices together. Wireless APs have at least one antenna. Usually there’s two for better reception (referred to as diversity) and a port to connect them to a wired network.
APs have the following characteristics:
■■ APs function as a central junction point for the wireless stations much like a switch or hub does within a wired network. Due to the half-duplex nature of wireless networking, the hub comparison is more accurate, even though hubs are rarely found in the wired world anymore.
■■ APs have at least one antenna—most likely two.
■■ APs function as a bridge to the wired network, giving the wireless station access to the wired network and/or the Internet.
■■ SoHo APs come in two flavors—the stand-alone AP and the wireless router. They can and usually do include functions like network address translation (NAT) and Dynamic Host Configuration Protocol (DHCP).
APs don’t create collision domains for each port like a switch does. An AP is a portal device that can either direct network traffic to the wired backbone or back out into the wireless realm. Data sent maintains MAC address information within the 802.11 frames. What’s more, these frames are capable of holding as many as four MAC addresses, but only when a wireless DS is in use. An AP also maintains an association table that you can view from the web-based software used to manage the AP. So what’s an association table? It’s basically a list of all workstations currently connected to or associated with the AP, which are listed by their MAC addresses. Another nice AP feature is that wireless routers can function as NAT routers, and they can carry out DHCP addressing for workstations as well. In the Cisco world, there are two types of APs: autonomous and lightweight. An autonomous AP is one that’s configured, managed, and maintained in isolation with regard to all the other APs that exist in the network. A lightweight AP gets its configuration from a central device called a wireless controller. In this scenario, the APs are functioning as antennas and all information is sent back to the wireless LAN controller (WLC). There are a bunch of advantages to this, like the capacity for centralized management and more seamless roaming. You’ll learn all about using WLC and lightweight APs throughout this book. You can think of an AP as a bridge between the wireless clients and the wired network. And, depending on the settings, you can even use an AP as a wireless bridge for bridging two, wired network segments together. In addition to the stand-alone AP, there’s another type of AP that includes a built-in router, which you can use to connect both wired and wireless clients to the Internet. These devices are usually employed as NAT routers.
Wireless Network Interface Card (NIC)
Every host you want to connect to a wireless network needs a wireless network interface card (NIC) to do so . Basically, a wireless NIC does the same job as a traditional NIC, only instead of having a socket/port to plug a cable into, the wireless NIC has a radio antenna.
Wireless Antennas
Wireless antennas work with both transmitters and receivers. There are two broad classes of antennas on the market today: omni-directional (or point-to-multipoint) and directional (or point-to-point). Yagi antennas usually provide greater range than omni antennas of equivalent gain. Why? Because yagis focus all their power in a single direction. Omnis must disperse the same amount of power in all directions at the same time, like a large donut. A downside to using a directional antenna is that you’ve got to be much more precise when aligning communication points. It’s also why most APs use omnis, because often, clients and other APs can be located in any direction at any given moment. To get a picture of this, think of the antenna on your car. Yes, it’s a non-networking example, but it’s still a good one because it clarifies the fact that your car’s particular orientation doesn’t affect the signal reception of whatever radio station you happen to be listening to. Well, most of the time, anyway. If you’re in the boonies, you’re out of range you’re out of luck—something that also applies to the networking version of Omnis.
Wireless Principles
different types of networks you’ll run into and/or design and implement as your wireless networks grow:
■ IBSS
■ BSS
■ ESS
■ Workgroup bridges
■ Repeater APs
■ Bridging (point-to-point and point-to-multipoint)
■ Mesh
Independent Basic Service Set (Ad Hoc)
This is the easiest way to install wireless 802.11 devices. In this mode, the wireless NICs (or other devices) can communicate directly without the need for an AP. A good example of this is two laptops with wireless NICs installed. If both cards were set up to operate in ad hoc mode, they could connect and transfer files as long as the other network settings, like protocols, were set up to enable this as well. We’ll also call this an independent basic service set (IBSS), which is born as soon as two wireless devices communicate. To create an ad hoc network, all you need is two or more wireless-capable devices. Once you’ve placed them within a range of 20–40 meters of each other, they’ll “see” each other and be able to connect—assuming they share some basic configuration parameters. One computer may be able to share the Internet connection with the rest of them in your group. An ad hoc network, also known as peer to peer, doesn’t scale well, and I wouldn’t recommend it due to collision and organization issues in today’s corporate networks. With the low cost of APs, you don’t need this kind of network anymore anyway, except for maybe in your home—probably not even there. Another con is that ad hoc networks are pretty insecure, so you really want to have the AdHoc setting turned off before connecting to your wired network.
Basic Service Set (BSS)
A basic service set (BSS) is the area, or cell, defined by the wireless signal served by the AP. It can also be called a basic service area (BSA), and the two terms, BSS and BSA, can be interchangeable. Even so, BSS is the most common term that’s used to define the cell area. So the AP isn’t connected to a wired network in this example, but it provides for the management of wireless frames so the hosts can communicate. Unlike the ad hoc network, this network will scale better and more hosts can communicate in this network because the AP manages all network connections.
Infrastructure Basic Service Set
In infrastructure mode, wireless NICs only communicate with an access point instead of directly with each other like they do when they’re in ad hoc mode. All communication between hosts, as well as any wired portion of the network, must go through the access point. Remember this important fact: in infrastructure mode, wireless clients appear to the rest of the network as though they were standard, wired hosts. Figure 19.6 shows a typical infrastructure mode wireless network. Pay special attention to the access point and the fact that it’s also connected to the wired network. This connection from the access point to the wired network is called the distribution system (DS) and is how the APs communicate to each other about hosts in the BSA. Basic standalone APs don’t communicate with each other via the wireless network, only through the DS. Before you configure a client to operate in wireless infrastructure mode, you need to understand SSIDs. The service set identifier (SSID) is the unique 32-character identifier that represents a particular wireless network and defines the BSS. And just so you know, lots of people use the terms SSID and BSS interchangeably, so don’t let that confuse you! All devices involved in a particular wireless network can be configured with the same SSID. Sometimes access points even have multiple SSIDs.
Service Set ID
So technically, an SSID is a basic name that defines the Basic Service Area (BSA) transmitted from the AP. A good example of this is “Linksys” or “Netgear.” You’ve probably seen that name pop up on our host when looking for a wireless network. This is the name the AP transmits out to identify which WLAN the client station can associate with. The SSID can be up to 32 characters long. It normally consists of human-readable ASCII characters, but the standard doesn’t require this. The SSID is defined as a sequence of 1–32 octets, each of which may take any value. The SSID is configured on the AP and can be either broadcasted to the outside world or hidden. If the SSID is broadcasted, when wireless stations use their client software to scan for wireless networks. The network will appear in a list identified by its SSID. But if it’s hidden, it either won’t appear in the list at all or will show up as “unknown network” depending on the client’s operating system. Either way, a hidden SSID requires the client station be configured with a wireless profile, including the SSID, in order to connect. And this requirement is above and beyond any other normal authentication steps or security essentials. The AP associates a MAC address to this SSID. It can be the MAC address for the radio interface itself—called the basic service set identifier (BSSID)—or it can be derived from the MAC address of the radio interface if multiple SSIDs are used. The latter is sometimes called a virtual MAC address and you would call it a multiple basic service set identifier (MBSSID). There are two things you really want to make note of in this figure: first, there’s a “Contractor BSSID” and a “Sales BSSID”; second, each of these SSID names is associated with a separate virtual MAC address, which was assigned by the AP. These SSIDs are virtual and implementing things this way won’t improve your wireless network’s or AP’s performance. You’re not breaking up collision domains or broadcast domains by creating more SSIDs on your AP, you just have more hosts sharing the same half-duplex radio. The reason for creating multiple SSIDs on your AP is so that you can set different levels of security for each client that’s connecting to your AP(s).
Extended Service Set
A good to thing to know is that if you set all your access points to the same SSID, mobile wireless clients can roam around freely within the same network. This is the most common wireless network design you’ll find in today’s corporate settings. Doing this creates something called an extended service set (ESS), which provides more coverage than a single access point and allows users to roam from one AP to another without having their host disconnected from the network. This design gives us the ability to move fairly seamlessly from one AP to another. For users to be able to roam throughout the wireless network—from AP to AP without losing their connection to the network—all APs must overlap by 20 percent of their signal or more to their neighbor’s cells. To make this happen, be sure the channels (frequency) on each AP are set differently.
Repeaters
If you need to extend the coverage of an AP, you can either increase the gain of a directional antenna or add another AP into the area. If neither of those options solves your problem, try adding a repeater AP into the network and extending the range without having to pull an Ethernet cable for a new AP. A wireless repeater AP isn’t connected to the wired backbone. It uses its antenna to receive the signal from an AP that’s directly connected to the network and repeats the signal for clients located too far away from it. To make this work, you need appropriate overlap between APs. Another way to get this to happen is to place a repeater AP with two radios in use, with one receiving and the other one transmitting. This works somewhat like a dual half-duplex repeater. Seems cool, but there’s an ugly downside to this design—for every repeater installed you lose about half of your throughput! Since no one likes less bandwidth, a repeater network should only be used for low-bandwidth devices, like a barcode reader in a warehouse.
Bridging
Bridges are used to connect two or more wired LANs, usually located within separate buildings, to create one big LAN. Bridges operate at the MAC address layer (Data Link layer), which means they have no routing capabilities. So you’ve got to put a router in place if you want to be able to do any IP subnetting within your network. Basically, you would use bridges to enlarge the broadcast domains on your network. Armed with a firm understanding of how bridging works, you can definitely improve your network’s capacity. To build wireless networks correctly, it’s important to have a working knowledge of root and nonroot bridges, sometimes referred to as parent and child bridges. Some bridges allow clients to connect directly to them, but others don’t, so make sure you understand exactly your business requirements before just randomly buying a wireless bridge. A point-to-point wireless network is a popular design that’s often used outdoors to connect two buildings or LANs together. A point-to-multipoint design works well in a campus environment where you have a main building with a bunch of ancillary buildings that you want to be able to connect to each other and back to the main one. Wireless bridges are commonly used to make these connections, and they just happen to be pricier than a traditional AP. The thing you want to remember about point-to-multipoint wireless networks is that each remote building won’t be able to communicate directly with each other. To do that, they must first connect to the central, main point (main building) and then to one of the other ones (multipoint buildings). Okay—now let’s get back to that root/nonroot issue I brought up a minute ago. This becomes really important to understand, especially when you’re designing outdoor networks! So look back to Figure 19.10 and find the terms root and nonroot. This figure shows a traditional point-to-point and point-to-multipoint network when one bridge, the root, accepts communications only from nonroot devices. Root devices are connected to the wired network, which allows nonroot devices, like clients, to access the wired resources through the root device. Here are some important guidelines to help you design your wireless networks:
■■ Nonroot devices can only communicate to root devices. Nonroot devices include nonroot bridges, workgroup bridges, repeater access points, and wireless clients.
■■ Root devices cannot communicate to other root devices. Examples of devices that can be roots are APs and bridges.
■■ Nonroot devices cannot communicate to other nonroot devices. But wait, there’s one exception to that last bullet point. If you have a nonroot bridge set up as a repeater AP with two radios, the device must be configured as a nonroot device!
It will then repeat and extend the distance of your outdoor, bridged network
Mesh Networks
As more vendors migrate to a mesh hierarchical design, and as larger networks are built using lightweight access points that are managed by a controller, you can see that we need a standardized protocol that governs how lightweight access points communicate with WLAN systems. This is exactly the role filled by one of the Internet Engineering Task Force’s (IETF’s) latest draft specifications, Lightweight Access Point Protocol (LWAPP). Mesh networking infrastructure is decentralized and comparably inexpensive for all the nice amenities it provides because each host only needs to transmit as far as the next host. Hosts act as repeaters to transmit data from nearby hosts to peers that are too far away for a manageable cabled connection. The result is a network that can span a large area, especially over rough or difficult terrain. Remember that mesh is a network topology in which devices are connected with many redundant connections between host nodes, and we can use this topology to our advantage in large wireless installations. Figure 19.12 shows a large meshed environment using Cisco outdoor managed APs to “umbrella” an outdoor area with wireless connectivity. Oh, and did I mention that mesh networks also happen to be extremely reliable? Because each host can potentially be connected to several other hosts, if one of them drops out of the network because of hardware failure or something, its neighbors simply find another route. So you get extra capacity and fault tolerance automatically just by adding more hosts! Wireless mesh connections between AP hosts are formed with a radio, providing many possible paths from a single host to other hosts. Paths through the mesh network can change in response to traffic loads, radio conditions, or traffic prioritization. At this time, mesh networks just aren’t a good solution for home use or small companies on a budget. As the saying goes, “If you have to ask…” As with most things in life, the more bells and whistles, the more it costs, and mesh networks are certainly no exception.