cancel
Showing results for 
Search instead for 
Did you mean: 

A lot of probe requests

FCervini
New Contributor

Hi all,

We have R310 AP's with a Zonedirector 1200. Recently we started noticing short break ups in the Wifi connectivity many times a day. When looking at the log of an AP I can see a lot of the following lines:

Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:31 RAP11 user.warn kernel: ieee80211_send_probereq: chan=11, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15
Feb 7 20:16:51 RAP11 user.warn kernel: ieee80211_send_probereq: chan=1, v54_ie2_size=15

They are usual preced by user.debug kernel: Neighbour found.

and end a bit later with

user.debug kernel: Route found: xmitdev=br0

As you can see, they are grouped together on the same time (2 groups in this example). I am wondering if this has anything to do with the signal breaking up, and if it is, how it can be fixed? I can't seem the find much documentation on this.

Can anyone help me figuring this one out?

Thanks

Frederic

1 ACCEPTED SOLUTION

Dickson
RUCKUS Team Member

Hello Fredric,

Please check the channelfly setting. For next, I would suggest to check the OTA capture; if you have macbook you may turn on the monitor mode with the wireshark to check what is going on in the 2.4G medium. If you need to debug more, please log a tac case with us and we can have a debug session with you. 

Thanks,

Dickson

View solution in original post

3 REPLIES 3

Dickson
RUCKUS Team Member

Hello Fredric,

Please check the channelfly setting. For next, I would suggest to check the OTA capture; if you have macbook you may turn on the monitor mode with the wireshark to check what is going on in the 2.4G medium. If you need to debug more, please log a tac case with us and we can have a debug session with you. 

Thanks,

Dickson

Hi Dickson

Thank you for your reply. The channelfly option was on for the 2.4GHz band (Not for the 5 GHz band).

I have set it to background scanning. I'll monitor it for the next week and see if there is any improvement.

Thanks,

Frederic

FCervini
New Contributor

I still see quite a bit of those user.warn kernel in the logs but the stability of the network has been vastly improved by turning off the channelfly option. I consider it solved for now. Thank you again for your help.