Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| airodump-ng [2010/11/21 16:20] – typos sleek | airodump-ng [2014/05/19 22:22] – [Usage] documented -t as short form for --encrypt darkaudax |
|---|
| |
| Filter options: | Filter options: |
| --encrypt <suite> : Filter APs by cipher suite | --encrypt <suite> : Filter APs by cipher suite (short form: -t) |
| --netmask <netmask> : Filter APs by mask | --netmask <netmask> : Filter APs by mask |
| --bssid <bssid> : Filter APs by BSSID | --bssid <bssid> : Filter APs by BSSID |
| |
| RXQ expanded:\\ | RXQ expanded:\\ |
| Its measured over all management and data frames. That's the clue, this allows you to read more things out of this value. Lets say you got 100 percent RXQ and all 10 (or whatever the rate) beacons per second coming in. Now all of a sudden the RXQ drops below 90, but you still capture all sent beacons. Thus you know that the AP is sending frames to a client but you can't hear the client nor the AP sending to the client (need to get closer). Another thing would be, that you got a 11MB card to monitor and capture frames (say a prism2.5) and you have a very good position to the AP. The AP is set to 54MBit and then again the RXQ drops, so you know that there is at least one 54MBit client connected to the AP. | Its measured over all management and data frames. The received frames contain a sequence number which is added by the sending access point. RXQ = 100 means that all packets were received from the access point in numerical sequence and none were missing. That's the clue, this allows you to read more things out of this value. Lets say you got 100 percent RXQ and all 10 (or whatever the rate) beacons per second coming in. Now all of a sudden the RXQ drops below 90, but you still capture all sent beacons. Thus you know that the AP is sending frames to a client but you can't hear the client nor the AP sending to the client (need to get closer). Another thing would be, that you got a 11MB card to monitor and capture frames (say a prism2.5) and you have a very good position to the AP. The AP is set to 54MBit and then again the RXQ drops, so you know that there is at least one 54MBit client connected to the AP. |
| |
| N.B.: RXQ column will only be shown if you are locked on a single channel, not channel hopping. | N.B.: RXQ column will only be shown if you are locked on a single channel, not channel hopping. |
