jan/15/2000 10:50:58 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:51:01 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:51:09 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:51:10 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:51:36 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:51:38 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:51:43 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:51:45 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:51:56 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:51:58 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:52:07 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:52:08 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:52:26 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:52:33 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:52:40 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:52:56 wlan2-S3: 00:02:6F:34:C3:52 connected
jan/15/2000 10:53:33 wlan2-S3: 00:02:6F:34:C3:52 disconnected
jan/15/2000 10:53:35 wlan2-S3: 00:02:6F:34:C3:52 connected
Similar experiences/solutions/suggestions Please…!!
interference, poor signal, bad cpe, mis-alignment.. a million things come to mind…
I think almost everyone has had similar experiences at some point in time…
/solutions/suggestions Please…!!
Use your signal level/CCQ data from the AP to diagnose and correct:
“interference, poor signal, bad cpe, mis-alignment”…
And pay special attention to your Fresnel Zone…
Hitek
This can also be cause by “stray” clients that are constantly trying to connect to strong signals even if they aren’t supposed to…some client devices will do this regardless of what the person behind the keyboard has set their device to connect to - some bridges will do this too. We get these all the time. Unfortunately, we have to turn off the wireless logging and/or filter this out with a syslog server.
Thank you very much for sharing your thoughts on this. I am quite sure you all can understand when I say I’m beating my head against the wall to figure out some of these problems.
CPE has also had some such problems and I have seen that most of the cases it’s weak signal.
Here’s the kicker…those logs I put in in my message up there are for wlan2-s3 (which is the sector) 
Also had the same thing happen at another site with an omni. Lowering the frequency kind of reduced the occurance but is still an issue.
Thanks again,
Engineer.
Had the same problem:
Mac address 00:02:6f:xx:xx:xx is probably Pheenet AP. Just flash the firmware and problem solved. Stupid old firmware is always disconecting and connecting again when changing speed of connection. With new firmware there is no that problem…
tip: for new firmware go to Senao site