Appendix B Wireless LANs
P-660W-Tx v2 User’s Guide
212
Figure 118
RTS/CTS
When station
A
sends data to the AP, it might not know that the station
B
is already using the
channel. If these two stations send data at the same time, collisions may occur when both sets
of data arrive at the AP at the same time, resulting in a loss of messages for both stations.
RTS/CTS
is designed to prevent collisions due to hidden nodes. An
RTS/CTS
defines the
biggest size data frame you can send before an RTS (Request To Send)/CTS (Clear to Send)
handshake is invoked.
When a data frame exceeds the
RTS/CTS
value you set (between 0 to 2432 bytes), the station
that wants to transmit this frame must first send an RTS (Request To Send) message to the AP
for permission to send it. The AP then responds with a CTS (Clear to Send) message to all
other stations within its range to notify them to defer their transmission. It also reserves and
confirms with the requesting station the time frame for the requested transmission.
Stations can send frames smaller than the specified
RTS/CTS
directly to the AP without the
RTS (Request To Send)/CTS (Clear to Send) handshake.
You should only configure
RTS/CTS
if the possibility of hidden nodes exists on your network
and the "cost" of resending large frames is more than the extra network overhead involved in
the RTS (Request To Send)/CTS (Clear to Send) handshake.
If the
RTS/CTS
value is greater than the
Fragmentation Threshold
value (see next), then the
RTS (Request To Send)/CTS (Clear to Send) handshake will never occur as data frames will
be fragmented before they reach
RTS/CTS
size.
"
Enabling the RTS Threshold causes redundant network overhead that could
negatively affect the throughput performance instead of providing a remedy.
Fragmentation Threshold
A
Fragmentation Threshold
is the maximum data fragment size (between 256 and 2432
bytes) that can be sent in the wireless network before the AP will fragment the packet into
smaller data frames.
A large
Fragmentation Threshold
is recommended for networks not prone to interference
while you should set a smaller threshold for busy networks or networks that are prone to
interference.
Summary of Contents for P-660W-T1 v2
Page 2: ......
Page 8: ...Safety Warnings P 660W Tx v2 User s Guide 8 ...
Page 10: ...Contents Overview P 660W Tx v2 User s Guide 10 ...
Page 18: ...Table of Contents P 660W Tx v2 User s Guide 18 ...
Page 22: ...List of Figures P 660W Tx v2 User s Guide 22 ...
Page 25: ...25 PART I Introduction Introducing the ZyXEL Device 27 Introducing the Web Configurator 31 ...
Page 26: ...26 ...
Page 30: ...Chapter 1 Introducing the ZyXEL Device P 660W Tx v2 User s Guide 30 ...
Page 36: ...Chapter 2 Introducing the Web Configurator P 660W Tx v2 User s Guide 36 ...
Page 37: ...37 PART II Setup Wizard Connection Setup Wizard 39 Media Bandwidth Management Wizard 47 ...
Page 38: ...38 ...
Page 46: ...Chapter 3 Connection Setup Wizard P 660W Tx v2 User s Guide 46 ...
Page 50: ...Chapter 4 Media Bandwidth Management Wizard P 660W Tx v2 User s Guide 50 ...
Page 52: ...52 ...
Page 83: ...Chapter 7 WAN Setup P 660W Tx v2 User s Guide 83 Figure 32 WAN Setup PPPoE ...
Page 104: ...Chapter 8 Network Address Translation NAT Screens P 660W Tx v2 User s Guide 104 ...
Page 130: ...Chapter 11 Firewall Configuration P 660W Tx v2 User s Guide 130 ...
Page 156: ...Chapter 15 Logs Screens P 660W Tx v2 User s Guide 156 ...
Page 169: ...169 PART IV Maintenance Maintenance 171 ...
Page 170: ...170 ...
Page 184: ...Chapter 17 Maintenance P 660W Tx v2 User s Guide 184 ...
Page 185: ...185 PART V Troubleshooting and Specifications Troubleshooting 187 Product Specifications 193 ...
Page 186: ...186 ...
Page 192: ...Chapter 18 Troubleshooting P 660W Tx v2 User s Guide 192 ...
Page 200: ...200 ...
Page 208: ...Appendix A Pop up Windows JavaScripts and Java Permissions P 660W Tx v2 User s Guide 208 ...
Page 226: ...Appendix C Common Services P 660W Tx v2 User s Guide 226 ...
Page 232: ...Appendix D Legal Information P 660W Tx v2 User s Guide 232 ...