Control Packets
Control packets are the everyman akin of packet type. They are alleged
ascendancy packets because they are anon accompanying to the standard's Media
Access Ascendancy (MAC) rules. Currently, the accepted defines six altered
ascendancy packets, apparent in Table 3-1.
Table 3-1: Currently Defined Ascendancy Packets Type
Subtype
Description
Control
10
Power Save (PS)-Poll
Control
11
Request To Accelerate (RTS)
Control
12
Clear To Accelerate (CTS)
Control
13
Acknowledgment (ACK)
Control
14
Contention-Free (CF)-End
Control
15
CF-End + CF-Ack
Two of these ascendancy frames are anon accompanying to the PCF approach of
operation mentioned ahead (CF-End and CF-End + CF-Ack). For all applied
purposes, these frames are currently unused.
As mentioned in the antecedent section, RTS/CTS packets advice break the
hidden bulge problem. They can additionally be acclimated to abstain collisions
alike back the bulge is not hidden. Back a base wants to address a ample
packet, alike after hidden nodes, there is the achievability of a collision.
Instead of transmitting a ample packet, the base can accelerate an RTS. If the
(relatively small) RTS packet gets absent in a collision, little time is ashen
retransmitting it. Once the base receives the AP-generated CTS, it can address
the ample packet after annoying about a collision.
There are alone two ascendancy packets left, PS-Poll and acknowledgments. As
mentioned previously, PS-Poll packets are acclimated by audience to retrieve
buffered packets from the AP back the applicant is in power-savings mode. There
isn't abundant to say about acknowledgments. Acknowledgment packets are small,
and they are acclimated to accede the cancellation of unicast abstracts and
some administration packets.
The best absorbing affair about ascendancy packets is that some of them are
absolutely advised to be accustomed by different networks on the aforementioned
channel. This agency that if you and your acquaintance accept your own
networks, and your AP sends out a Clear To Accelerate (CTS), all of the 802.11
nodes that apprehend it (including your neighbors) are accepted to account the
CTS packet and not address annihilation for the continuance specified.
The actuality that nodes on absolutely different networks are accepted to
action and account assertive packets from anniversary added is interesting. It
agency that there is a baby subset of the 802.11 agreement that, by design,
cannot be authenticated. This is a attenuate but important aberration amid
802.11 and around any added agreement on the planet.
If you angle up a computer to the Internet after a firewall (or a NAT), you
have, in a sense, accustomed anyone abroad on the Internet the adeptness to
appoint your computer in the TCP/IP protocol. If you anticipate this is a bad
abstraction (and acutely you should), you can about-face on your own firewall,
stick yourself abaft a NAT, and so on.
Similarly, back you bung an Ethernet
cable into your computer, you are giving anybody on the aforementioned
advertisement area the adeptness to appoint your computer in the (relatively
simple) layer-two protocol, Ethernet. People about don't anguish about this for
two reasons. One is that Ethernet is actual simple, and accordingly cipher has
anytime begin a accidentally accommodating bug in an Ethernet accessory driver.
The added acumen is that by advantage of actuality physically affiliated to the
aforementioned active network, there is some adumbrated akin of trust. Neither
of these assurances applies to 802.11.