04.01.2015 Views

Wireles Networks The Definitive Guide.pdf - Csbdu.in

Wireles Networks The Definitive Guide.pdf - Csbdu.in

Wireles Networks The Definitive Guide.pdf - Csbdu.in

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.5.6 Frame Check Sequence<br />

As with Ethernet, the 802.11 frame closes with a frame check sequence (FCS). <strong>The</strong> FCS is often<br />

referred to as the cyclic redundancy check (CRC) because of the underly<strong>in</strong>g mathematical operations.<br />

<strong>The</strong> FCS allows stations to check the <strong>in</strong>tegrity of received frames. All fields <strong>in</strong> the MAC header and<br />

the body of the frame are <strong>in</strong>cluded <strong>in</strong> the FCS. Although 802.3 and 802.11 use the same method to<br />

calculate the FCS, the MAC header used <strong>in</strong> 802.11 is different from the header used <strong>in</strong> 802.3, so the<br />

FCS must be recalculated by access po<strong>in</strong>ts.<br />

When frames are sent to the wireless <strong>in</strong>terface, the FCS is calculated before those frames are sent out<br />

over the RF or IR l<strong>in</strong>k. Receivers can then calculate the FCS from the received frame and compare it<br />

to the received FCS. If the two match, there is a high probability that the frame was not damaged <strong>in</strong><br />

transit.<br />

On Ethernets, frames with a bad FCS are simply discarded, and frames with a good FCS are passed up<br />

the protocol stack. On 802.11 networks, frames that pass the <strong>in</strong>tegrity check may also require the<br />

receiver to send an acknowledgment. For example, data frames that are received correctly must be<br />

positively acknowledged, or they are retransmitted. 802.11 does not have a negative acknowledgment<br />

for frames that fail the FCS; stations must wait for the acknowledgment timeout before retransmitt<strong>in</strong>g.<br />

3.6 Encapsulation of Higher-Layer Protocols With<strong>in</strong> 802.11<br />

Like all other 802 l<strong>in</strong>k layers, 802.11 can transport any network-layer protocol. Unlike Ethernet,<br />

802.11 relies on 802.2 logical-l<strong>in</strong>k control (LLC) encapsulation to carry higher-level protocols. Figure<br />

3-13 shows how 802.2 LLC encapsulation is used to carry an IP packet. In the figure, the "MAC<br />

headers" for 802.1h and RFC 1042 might be the 12 bytes of source and dest<strong>in</strong>ation MAC address<br />

<strong>in</strong>formation on Ethernet or the long 802.11 MAC header from the previous section.<br />

Figure 3-13. IP encapsulation <strong>in</strong> 802.11<br />

Two different methods can be used to encapsulate LLC data for transmission. One is described <strong>in</strong> RFC<br />

1042, and the other <strong>in</strong> 802.1h. As you can see <strong>in</strong> Figure 3-13, though, the two methods are quite<br />

similar. An Ethernet frame is shown <strong>in</strong> the top l<strong>in</strong>e of Figure 3-13. It has a MAC header composed of<br />

source and dest<strong>in</strong>ation MAC addresses, a type code, the embedded packet, and a frame check field. In<br />

the IP world, the Type code is either 0x0800 (2048 decimal) for IP itself, or 0x0806 (2054 decimal) for<br />

the Address Resolution Protocol (ARP).<br />

38

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!