RTS/CTS -unicast or broadcast + Random backoff time
Iam reading through the frame handshake in WiFi. Also went through some of the good articles in this forum.
I understand that to avoid collision, RST/CTS handshake is used in the wireless Air medium.
I have attached the RTS-CTS handshake and I would like to know if these frames are unicast or broadcast.
Since they are sent from a specific source say Wifi Client to a specifc destination say Wifi AP, i assume the RTS and CTS signals to be unicast but i dont understand then how the other wifi stations/clients will listen/get the duration (NAV)
Also regarding the backoff time interval, I would like to know how this time is decided by the waiting clients? Say client A and Client B are waiting for the medium to be free. Both get the NAV duration as client C is using the medium. Now after the NAV time is complete, the clients A and B will wait for a backoff time.
>how much is this random time?
>Can both set the same backoff time say 1? >Will the clients with min backoff time will get to check the medium first.
>What is the max time each client will get to use the medium? What if Cient C using the medium has lots of data to send. Will clients A and B have to wait till Client C finishes? OR is there a max time duration.
Re: RTS/CTS -unicast or broadcast + Random backoff time
Whenever a wireless client wants to send a data packet to the access point, it actually transmits a four-packet sequence called the RTS-CTS-DATA-ACK packet sequence. Each of the four 802.11 frames carries a NAV field that indicates the number of microseconds that the channel is reserved for by a wireless client. During the RTS/CTS handshake between the wireless client and access point, the wireless client sends a small RTS frame that includes a NAV interval large enough to complete the entire sequence. This includes the CTS frame, the data frame, and the subsequent acknowledgment frame from the access point.
When the wireless client transmits its RTS packet with the NAV set, the transmitted value is used to set the NAV timers on all other wireless clients associated to the access point. The access point replies to the RTS packet from the client with a CTS packet that contains a new NAV value updated to account for the time already elapsed during the packet sequence. After the CTS packet is sent, every wireless client that can receive from the access point has updated their NAV timer and defers all transmissions until their NAV timer reaches 0. This keeps the channel free for the wireless client to complete the process of transmitting a packet to the access point.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...