This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Request-to-send flood from access point

0

I'm experiencing constant intermittent lag spikes from my wireless network and decided the investigate using wireshark.

I found out that during one of the spikes, the transmitting address (Station A), which happens to be my wireless router (Engenius ESR9850), is sending out 25 of these RTS packets.

540 0.201225 Station A (TA) Station B (RA) 802.11 52 Request-to-send, Flags=........C

I've exhausted all my options trying to eliminate the lag spike. These are the following things I've tried.

  • Changing the wireless channel (It is using channel 11 now)
  • Changing the preamble
  • Changing the transmission bandwidth (20/40mhz)
  • Changing the RTS and fragmentation threshold

Is the router going rogue?? It is also linked to an ESR6670 via WDS. Station B is probably connected to the ESR6670 when this happened.

Please help :/

asked 06 Jun '12, 08:15

cloudsix's gravatar image

cloudsix
1111
accept rate: 0%


One Answer:

0

If the transmitting station is seeing interference or real traffic on the channel, it will not find long enough clear (silent) intervals to be able to send the size packet it wants to send. As a result, it decides that it will have to take the more expensive protocol step (in terms of overhead and channel usage) of sending out an RTS (Request To Send).

It then expects somebody, presumably the Access Point in an infrastructure network or one of the other nodes in the case of an ad hoc network, to send back a CTS (Clear To Send). When all of the other stations participating in that network see the CTS, they are obligated to hold off transmission for the interval specified in the CTS message.

So my guess is that there is either reverse direction traffic, traffic involving another station, or radio interference present that causes A to send RTS. It will do that at frequent intervals, trying to break through, until it gets a CTS back. During the time that it waits for a CTS it will be blocking and not sending outbound traffic.

Look at the RF side, look for other networks' beacons on the channnel, and look for other traffic on that network.

And of course it could just be Station A going rogue. :-)

answered 07 Jun '12, 17:31

inetdog's gravatar image

inetdog
16717
accept rate: 14%