Building Secure Wireless Networks with 802.11 phần 2 potx

Star Topology In a star topology, all devices are connected to a central hub (see Figure 1.9). Nodes communicate across the network by passing data through the hub. Because the protocol is easy to develop, many private networks use it. The mesh topology connects each node with every other node, creating an isolated data path between each node. Figure 1.9: Star topology. Star topology has a very high performance but works in a limited geographical area and is very costly, as the wires from each computer must run all the way to the central hub. Most wireless networks use a variation of the star topology (without wires, of course). Choosing the Right Topology Which topology you deploy should be based upon connectivity requirements, budget, and the available hardware. The bus topology is the simplest to implement and is the most widely used network topology. The ring topology is the most expensive to implement. Bus topology is extremely common in enterprise LANs; however, their backbones are often designed using the ring topology to give higher performance. Ring topology attains better performance over bus topology because the physical medium that data travels on is not shared among all computers on the network (only adjacent computers share the given medium), whereas in bus topology all computers connected to the network share the same physical medium, resulting in collision and medium congestion (network becomes too busy) and hence lower performance. Wireless LANs use the star topology because it provides a better management of the network bandwidth. Network Hardware and Software In this section we talk about the networking components, software, and the protocols that are 18 required for each computer in a network. For a network to function, all the computers must have compatible network software and hardware, and they must be connected to one another via a physical link, a cable, for example. Networking Components A computer in a network must have a network interface card (NIC) installed. These are electronic circuits that conform to the physical layer of the International Standards Organization Open Systems Interconnection (ISO/OSI) Reference Model and are IEEE−compliant. These network cards connect the computer to a network. In this section we discuss the ISO/OSI Reference Model and the IEEE view of the first two layers of this model. We also discuss NICs, hubs, routers, and repeaters. International Standards Organization Open Systems Interconnection (ISO/OSI) Reference Model Modern computer networks are designed in a highly structured way. To reduce the design complexity, most networks are organized as a series of layers, each one built upon its predecessor. The ISO/OSI Reference Model (Figure 1.10) is based on a proposal developed by the International Standards Organization (ISO). The model is called ISO/OSI Reference Model because it deals with connecting open systems—that is, systems that are open for communication with other systems. Figure 1.10: ISO/OSI Reference Model. Flexibility is the primary requirement for an acceptable open system. Prior to ISO/OSI Reference Model, most computer networks were proprietary and monolithic (you had to buy the entire network system from one vendor). They were not interoperable with other network systems and were hard to maintain. The ISO/OSI Reference Model added flexibility to the network model by dividing a network system into seven distinct parts. Control is passed from one layer to the next, starting at the application layer, proceeding to the bottom layers. Since the seven layers are stacked on top of one another, the reference model is also known as ISO/OSI stack. The reference model allows different vendors to manufacture networking components that interoperate with each other and hence 19 provides a better option to a network implementer who can build a network based upon his or her need. For example, today we use HyperText Transfer Protocol (HTTP) to surf the Internet. Let's assume that starting next week you would have to use a new protocol called ViperText Transfer Protocol (VTTP). If the protocol is written with ISO/OSI Reference Model in mind, all you would have to do is to install the VTTP protocol driver and you would be ready to use the VTTP without any other modification to your network hardware or software. The principles that were applied to arrive at the seven layers are as follows: A layer should be created where a different level of abstraction is needed.1. Each layer should perform a well−defined function.2. The function of each layer should be chosen to interoperate with internationally standardized protocols. 3. The number of layers should be large enough that distinct functions need not be thrown together in the same layer out of necessity, and small enough that the architecture does not become unwieldy. 4. The computer systems that implement their network components using the ISO/OSI Reference Model can interoperate with most other systems. A layer can be replaced with another layer of the same type from a different vendor. This provides great flexibility to systems manufacturers, IT staff, and general users where they can plug and play different protocols, adapters, and networks without making drastic changes on their computers. Now let's look at the layers that the OSI Reference Model defines. The Application Layer: Layer 7 The application layer contains a variety of protocols that are commonly needed. For example, there are hundreds of incompatible terminal types in the world. Consider the plight of a full−screen editor that is supposed to work over a network with many different terminal types, each with different screen layouts, escape sequences for inserting and deleting text, ways of moving the cursor, and so on. One way to solve this problem is to define an abstract network virtual terminal for which editors and other programs can be written. To handle each terminal type, a piece of software must be written to map the functions of the network virtual terminal onto the real terminal. For example, when the editor moves the virtual terminal's cursor to the upper left−hand corner of the screen, this software must issue the proper command sequence to the real terminal to get its cursor there too. All the virtual terminal software is in the application layer. Another application layer function is file transfer. Different file systems have different file−naming conventions, different ways of representing text lines, and so on. Transferring a file between two different systems requires handling these and other incompatibilities. This work, too, belongs to the application layer, as do electronic mail, remote job entry, directory lookup, and various other general−purpose and special−purpose facilities. The Presentation Layer: Layer 6 The presentation layer performs certain functions that are requested sufficiently often to warrant finding a general solution for them, rather than letting each user solve the problems. In particular, unlike all the lower layers, which are just interested in moving bits reliably from here to there, the presentation layer is concerned with the syntax and semantics of the information transmitted. 20 A typical example of a presentation service is encoding data in a standard, agreed−upon way. Most user programs do not exchange random binary bit strings. They exchange things such as people's names, dates, amounts of money, and invoices. These items are represented as character strings, integers, floating−point numbers, and data structures composed of several simpler items. Different computers have different codes for representing character strings, integers, and so on. In order to make it possible for computers with different representations to communicate, the data structures to be exchanged can be defined in an abstract way, along with a standard encoding to be used "on the wire." The job of managing these abstract data structures and converting from the representation used inside the computer to the network standard representation is handled by the presentation layer. The presentation layer is also concerned with other aspects of information representation. For example, data compression can be used here to reduce the number of bits that have to be transmitted, and cryptography is frequently required for privacy and authentication. The Session Layer: Layer 5 The session layer allows users on different machines to establish sessions between them. A session allows ordinary data transport, as does the transport layer, but it also provides some enhanced services useful to an application. A session might be used to allow a user to log into a remote time−sharing system or to transfer a file between two machines. One of the services of the session layer is to manage dialogue control. Sessions can allow traffic to go in both directions at the same time, or in only one direction at a time. If traffic can go only one way at a time, the session layer can help keep track of whose turn it is. A related session service is token management. For some protocols, it is essential that both sides do not attempt the same operation at the same time. To manage these activities, the session layer provides tokens that can be exchanged. Only the side holding the token may perform the critical operation. Another session service is synchronization. Consider the problems that might occur when trying to do a two−hour file transfer between two machines on a network with a one−hour mean time between crashes. After each transfer was aborted, the whole transfer would have to start over again, and would probably fail again with the next network crash. To eliminate this problem, the session layer provides a way to insert checkpoints into the data stream, so that after a crash, only the data after the last checkpoint has to be repeated. The Transport Layer: Layer 4 The basic function of the transport layer is to accept data from the session layer, split it up into smaller units if need be, pass these to the network layer, and ensure that the pieces all arrive correctly at the other end. Furthermore, all this must be done efficiently and in a way that isolates the session layer from the inevitable changes in the hardware technology. Under normal conditions, the transport layer creates a distinct network connection for each transport connection required by the session layer. If the transport connection requires a high throughput, however, the transport layer might create multiple network connections, dividing the data among the network connections to improve throughput. On the other hand, if creating or maintaining a network connection is expensive, the transport layer might multiplex several transport connections onto the same network connection to reduce the cost. In all cases, the transport layer is required to make the multiplexing transparent to the session layer. 21 The transport layer also determines what type of service to provide to the session layer, and ultimately, the users of the network. The most popular type of transport connection is an error−free point−to−point channel that delivers messages in the order in which they were sent. However, we have other possible kinds of transport, service, and transport−isolated messages with no guarantee about the order of delivery, and broadcasting of messages to multiple destinations. The type of service is determined when the connection is established. The transport layer is a true source−to−destination or end−to−end layer. In other words, a program on the source machine carries on a conversation with a similar program on the destination machine, using the message headers and control messages. Many hosts are multiprogrammed, which implies that multiple connections will be entering and leaving each host. There needs to be a way to tell which message belongs to which connection. The transport header is one place this information could be put. In addition to multiplexing several message streams onto one channel, the transport layer must take care of establishing and deleting connections across the network. This requires some kind of naming mechanism so that a process on one machine has a way of describing with whom it wishes to converse. There must also be a mechanism to regulate the flow of information so that a fast host cannot overrun a slow one. Flow control between hosts is distinct from flow control between switches, although similar principles apply to both. The Network Layer: Layer 3 The network layer is concerned with controlling the operation of the subnet. A key design issue is determining how packets are routed from source to destination. Routes could be based on static tables that are "wired into" the network and rarely changed. They could also be determined at the start of each conversation—for example, a terminal session. Finally, they could be highly dynamic, being determined anew for each packet, to reflect the current network load. If too many packets are present in the subnet at the same time, they will get in each other's way, forming bottlenecks. The control of such congestion also belongs to the network layer. Since the operators of the subnet may well expect remuneration for their efforts, there is often some accounting function built into the network layer. At the very least, the software must count how many packets, characters, or bits each customer sends, to produce billing information. When a packet crosses a national border, with different rates on each side, the accounting can become complicated. When a packet has to travel from one network to another to get to its destination, many problems can arise. The addressing used by the second network may be different from the first one. The second one may not accept the packet at all because it is too large. The protocols may differ, and so on. It is up to the network layer to overcome all these problems to allow heterogeneous networks to be interconnected. In broadcast networks, the routing problem is simple, so the network layer is often thin or even nonexistent. The Data−Link Layer: Layer 2 The main task of the data−link layer is to take a raw transmission facility and transform it into a line that appears free of transmission errors in the network layer. It accomplishes this task by having the sender break up the input data into data frames (typically a few hundred bytes), transmit the frames 22 sequentially, and process the acknowledgment frames sent back by the receiver. Since the physical layer merely accepts and transmits a stream of bits without any regard to meaning of structure, it is up to the data−link layer to create and recognize frame boundaries. This can be accomplished by attaching special bit patterns to the beginning and end of the frame. If there is a chance that these bit patterns might occur in the data, special care must be taken to avoid confusion. The data−link layer should provide error control between adjacent nodes. Another issue that arises in the data−link layer (and most of the higher layers as well) is how to keep a fast transmitter from drowning a slow receiver in data. Some traffic regulation mechanism must be employed in order to let the transmitter know how much buffer space the receiver has at the moment. Frequently, flow regulation and error handling are integrated for convenience. If the line can be used to transmit data in both directions, this introduces a new complication that the data−link layer software must deal with. The acknowledgment frames for A to B traffic compete for the use of the line with the data frames for the B to A traffic. A clever solution (piggybacking) has been devised. The Physical Layer: Layer 1 The physical layer is concerned with transmitting raw bits over a communication channel. The design issues have to do with making sure that when one side sends a 1 bit, it is received by the other side as a 1 bit, not as a 0 bit. Typical questions here are how many volts should be used to represent a 1 and how many for a 0, how many microseconds a bit lasts, whether transmission may proceed simultaneously in both directions, how the initial connection is established and how it is torn down when both sides are finished, and how many pins the network connector has and what each pin is used for. The design issues here deal largely with mechanical, electrical, and procedural interfaces, and the physical transmission medium, which lies below the physical layer. Physical layer design can properly be considered to be within the domain of the electrical engineer. IEEE's View of the ISO/OSI Reference Model The Institute of Electrical and Electronics Engineers (IEEE) has subdivided both the data−link layer and the physical layer into sublayers to attain a higher level of interoperability between devices (Figure 1.11). Figure 1.11: IEEE's ISO/OSI subdivision. The data−link layer is divided into logical link control (LLC) and the media access control (MAC) layer. LLC interfaces with the network layer and interprets commands and performs error recovery. It provides a common protocol between the MAC and network layer. The MAC layer controls the data transfer to and from the physical layer. 23 The physical layer is subdivided into the physical layer convergence procedure (PLCP) and the physical medium dependent (PMD). PLCP properly maps the MAC−specified data to the format that can be understood by the PMD layer and vice versa. The PMD layer provides the point−to−point communications between computers in the network. For example, on an Ethernet network, PMD on the network card communicates with PMDs of other network cards to establish communication between the computers. IEEE's subdivision has enabled both software and hardware vendors to develop solutions that interoperate with each other and are easier to implement. Network Interface Cards (NIC) Hardware network adapters implement the physical layer of the OSI layer. Almost all computers today use one of the IEEE standard cards to add the networking functionality. The NICs are technically named after the IEEE standard that they follow along with the physical connectivity and type of media they use. For example, an Ethernet NIC works with a MAC adapter that knows how to format data for the IEEE 802.3 Ethernet standard. A twisted pair Ethernet adapter connects to the network with a twisted pair cable and follows the IEEE Ethernet standard. Commonly used network adapters include Ethernet NICs and Token Ring NICs. Networking Cable and Physical Connections In all wired networks, an NIC is connected with the network through NIC−supported connectors and cables. There are two major types of cables used with LANs, these are twisted pair cable and coaxial cable. Twisted Pair Cable Twisted pair cables (see Figure 1.12) are available both as shielded and unshielded. The cable has four pairs of wires inside the jacket. Each pair of wires is twisted with a different number of twists per inch to help eliminate interference from adjacent pairs and other electrical devices. Figure 1.12: Twisted pair cable. The tighter the cable is twisted, the higher the supported transmission rate and the greater the cost per foot. The Electronic Industry Association/Telecommunication Industry Association (EIA/TIA) have established standards for unshielded twisted pair (UTP) cables. There are five categories of UTP cables (see Table 1.1). Table 1.1: The Five Twisted Pair Cable Categories CATEGORY USE 1 Voice Only (Telephone Wire) 24 2 Data up to 4 Mbps (LocalTalk) 3 Data up to 10 Mbps (Ethernet) 4 Data up to 20 Mbps (16 Mbps Token Ring) 5 Data up to 100 Mbps (Fast Ethernet) When selecting the network cable, you should choose the best cable you can afford. This helps in upgrading the network in the future when faster technologies are available. Unshielded twisted pair cables have the disadvantage of being susceptible to radio and electrical frequency interference. Shielded twisted pair is suitable for environments with electrical interference; however, the extra shielding can make the cables quite bulky. Shielded twisted pair is often used on networks using Token Ring topology. Coaxial Cable Coaxial cabling (see Figure 1.13) has a single copper conductor at its center. A plastic layer provides insulation between the center conductor and a braided metal shield. The metal shield helps to block any outside interference from fluorescent lights, motors, and other computers. Figure 1.13: Coaxial cable. Although coaxial cabling is difficult to install, it is highly resistant to signal interference. In addition, it can support greater cable lengths between network devices than twisted pair cable. The two types of coaxial cabling are thick coaxial and thin coaxial. Thin coaxial cable is also referred to as thinnet. 10Base2 refers to the specifications for thin coaxial cable carrying Ethernet signals. The 2 in 10Base2 refers to the approximate maximum segment length, which is 200 meters. In actuality, the maximum segment length is 185 meters. Thin coaxial cable is popular in school networks, especially linear bus networks. Thick coaxial cable is also referred to as thicknet. 10Base5 refers to the specifications for thick coaxial cable carrying Ethernet signals. The 5 in 10Base5 refers to the maximum segment length being 500 meters. Thick coaxial cable has an extra protective plastic cover that helps keep moisture away from the center conductor. This makes thick coaxial a great choice when running longer lengths in a linear bus network. One disadvantage of thick coaxial is that it does not bend easily and is difficult to install. Hubs Hubs are used in situations where two or more computers need to be physically wired together (see Figure 1.14). In other words, hubs physically connect computers on a LAN. 25 Figure 1.14: Hub. Hubs can be chained together to extend the number of computers participating on a network. Routers Routers (see Figure 1.15) restrict and route the network data traffic on a network. Consider a scenario where two different departments are interconnected with each other using the same network; assume that the two departments hardly need to communicate with each other. Because they both share the same network bandwidth, the networks get jammed and a little too busy. But if the network is divided into two separate networks and a router is put in between them, then the network is much cleaner and does not get clogged or too busy, as each department is concerned only with its own traffic and does not have to be concerned with the other's. Whenever data needs to be sent to the other department, the router acts as a network traffic controller and simply allows that data to pass through to the other network. Figure 1.15: Router. Routers, therefore, simplify the network and greatly improve the network performance. Repeaters Wired LANs can cover a limited geographical area, which usually ranges from 150 to about 300 meters with most wired networks. The maximum range that a LAN can cover depends upon the equipment and the type of cable used. Repeaters are a simple solution to overcome and extend the geographic limit. The reason for the limited area that LANs cover lies in the fact that electrical signals become weaker as they travel on a medium. Repeaters are devices that act like a relay station and strengthen an incoming weak electrical signal, without any alteration in the data that signal carries, and retransmit the data for further use. Repeaters should be placed at distances whenever a weaker signal is detected. In most networks, repeaters are needed at every 150 to 300 meters. Networking Software In order to access a network, a user must install network software on his or her computer. The 26 network software includes the proper network protocols and the NIC drivers. A common example of the application software one might want to use would be a Web browser. A Web browser uses the network software to communicate with another computer and displays the results of the communication. The networking protocols identify the computer and the user on a network to another computer and user. The most widely used network protocol is Transmission Control Protocol/Internet Protocol, or TCP/IP (see the next section on TCP/IP), which is also used on the Internet. NIC drivers are normally devised by the NIC manufacturer and are set according to their specifications. Network drivers must be made compatible with the operating system. Network drivers communicate both with the networking protocols and the LLC to facilitate the data transmission over the wire. Networking Protocol: TCP/IP Networking protocols provide computer application software to access the network. These protocols provide an abstraction of the computer hardware, operating system, and physical characteristics of the network. As already mentioned, TCP/IP is by far the most commonly used protocol, so its basic operation bears some examination. Many of the overall principles used in this protocol apply to other types of protocols. As a result of the explosive growth that the Internet has seen over the past decade, TCP/IP has become the de facto standard protocol for networking. Most vendors have dropped their proprietary protocols and adopted TCP/IP as the protocol for their networking software. (WAP is irrelevant for this discussion. This book is about 802.11b, which is essentially wireless Ethernet.) The history of TCP/IP and the Internet begins in 1973, when the U.S. DoD Advanced Research Projects Agency (DARPA) initiated a research program to investigate techniques and technologies for interlinking packet networks of various kinds. The objective was to develop communication protocols that would allow networked computers to communicate transparently across multiple, linked packet switching networks. The network was initially known as ARPANET. One of the lasting legacies of ARPANET was a host of protocols that worked on packet switching network protocols including TCP/IP. The system of interconnected networks that emerged from this research eventually became commonly known as the Internet. The initial network protocol adapted by ARPANET was known as Network Control Protocol (NCP). By 1974 NCP was deemed inadequate to handle the growing traffic over the rapidly expanding network. At that time a more robust network Transmission Control Protocol (TCP) was adopted. The initial TCP design defined both the information required for the routing of the data−packets from one end to the other as well as structure of the data or payload. This protocol was considered too heavyweight for the intermediate routers because they had to deal with end−to−end data. So in 1978 this protocol was divided into parts: one to handle the routing of data−packets, the other to handle end−to−end data transmission. The system of protocols that was developed over the course of this research effort became known as the TCP/IP Protocol Suite, after the two initial protocols developed: Transmission Control Protocol (TCP) and Internet Protocol (IP). TCP corresponds to the transport layer of the ISO/OSI model, and IP is the implementation of the network layer. The current version of IP is IPv4, and the upcoming version is IPv6. IPv4 or the current implementation of IP that is used throughout the Internet uses 32−bit addresses commonly represented by a set of four 8−bit numbers ranging from 0 to 255 separated by periods or dots. This is commonly known as the IP address. Each IP address identifies a particular node in the network. 27 [...]... 1 92. 168.0 .2 Pinging 1 92. 168.0 .2 with 32 bytes of data: Reply Reply Reply Reply from from from from 1 92. 168.0 .2: 1 92. 168.0 .2: 1 92. 168.0 .2: 1 92. 168.0 .2: bytes= 32 bytes= 32 bytes= 32 bytes= 32 time . bytes= 32 time<10ms TTL= 128 Reply from 1 92. 168.0 .2: bytes= 32 time<10ms TTL= 128 Reply from 1 92. 168.0 .2: bytes= 32 time<10ms TTL= 128 Reply from 1 92. 168.0 .2: bytes= 32 time<10ms TTL= 128 6 "ping 1 92. 168.0 .2& quot; from the computer with IP address 1 92. 198.0.3. The program should reply with: C:>ping 1 92. 168.0 .2 Pinging 1 92. 168.0 .2 with 32 bytes of data: Reply from 1 92. 168.0 .2: bytes= 32. second (Mbps). Eventually, 8 02. 11b—also known as wireless fidelity, or Wi−Fi, or 8 02. 11 high rate, which is a modified version of the 8 02. 11 standard— operated at 11 Mbps. Today, higher speeds