Number of Probe Response Retry

  • 1
  • Idea
  • Updated 8 months ago
There is a problem with the response to broadcast probe requests that contain a wildcard SSID. 

Some client implementations wait only a few ms after sending a probe request while scanning. It might be impossible to get the frame out before the client leaves the channel again. If the client leaves before all probe reponses where acked this can cause the probe response to be retried quite often consuming even more airtime.

Therefore, the question arises. Is it possible to set a flag to not send more than 1 probe response retry to broadcast probe requests that contain a wildcard SSID?

Photo of Pavel Semenischev

Pavel Semenischev

  • 15 Posts
  • 1 Reply Like

Posted 8 months ago

  • 1
Photo of Michael Brado

Michael Brado, Official Rep

  • 1889 Posts
  • 269 Reply Likes
No, there is no such flag.
Photo of Pavel Semenischev

Pavel Semenischev

  • 15 Posts
  • 1 Reply Like
Hi Michael,
I know that there is no such feature, I was told about it in technical support.
I noted my message as an idea, because it is worth considering as a future request.
I captured the radio interface traffic from the street access points.
63.6% of all traffic is the probe response packets. 54.9% of all traffic - probe responce retry packages to broadcast probe requests that contain a wildcard SSID.
It's horrible. And by and large, these packages are meaningless