I just replaced a CB3 in AP mode with a router board 532 MT version 2.9.6.

The CB3 just did not have the feature set we needed. But now we have several clients that associate and disassociate constantly. The log file is filled with these entries "Wlan1 disconected xx:xx:xx:xx:xx:xx extensive data loss"

These are people that use Tranzeo and CB3's as CPE's MT shows a -100 for signal strength but they are solid with the CB3.

I will send a support file.

Is anyone else having still having this problem??

The CB3 just did not have the feature set we needed. But now we have several clients that associate and disassociate constantly. The log file is filled with these entries "Wlan1 disconected xx:xx:xx:xx:xx:xx extensive data loss"

...

Is anyone else having still having this problem??

Several people are. I have seen it, but it seems that these users do not have problems staying online. Are your users having problems staying online (i.e. passing traffic)?

Are your users having problems staying online (i.e. passing traffic)?

Actually it is hard to tell. They blink in and out of the registration table constantly. However they are not complaining. Other Non-senao/cb3 based CPE's do not exhibit this they stay in the registration table.

Can anyone shed any light on this behavior???

Thanks

Joe

Not sure about what is causing it, but most folks, like you, see the log entries, but are not seeing it be a problem for their customers.

I am seeing this also on a router used for backhaul to two towers after upgrading to 2.9.6. One of the links that is running -48 to -52 will drop with the 'extensive data loss' message. It seems to usually connect right back and I have had no complaints from customers. My main problem is it fills up the log file with this stuff. On the upside the cpu usage has dropped from peaking around 80% down to 40% peaks since upgrading from 2.8. Both links are running nstreme.

I spoke to soon.

We are getting complaints. So far 2 clients say the connection is very slow, and pauses alot.

CAn't anyone explain why this is happening, and what to do to fix it?

Hi All,

I know a fix :-) try to disable the Periodic Calibration under the Advance tab.
It gets better but not good.

//Rickard

Hello,

I get the problems after upgrading from 2.9.

The problem stays with the CB3's on Prism II mPCI
But a lot worse is that my backbone connections with several of cards 5211, 5212 and 5213 has the same problem, the disconnect random.

My problem is also there are running PPPoE sessions over it and the will all disconnect. With the lastest versions of 2.8 the wouldn´t occur, with versions like 2.8.10 we had the same problems.

We use some rb532´s so we could go back to 2.8

I would prompt MikroTik on this problem, bacause I think it´s a serios problem

we are running all 2.9.7 all signals are <-80 and CCQ´s are >20

one of the backbone links exits with this messages

12:22:35 wireless,info sj: disconnected 00:02:6F:20:FC:B0, no beacons
12:22:35 wireless,debug sj: deactivated WDS link 00:02:6F:20:FC:B0, name wds2.sj.johan
12:22:35 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:35 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:35 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:36 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:36 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:40 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth (27 events suppressed)
12:22:41 wireless,debug sj: 00:02:6F:20:FC:B0 attempts to connect
12:22:41 wireless,debug sj: AP 00:02:6F:20:FC:B0 not matched by connect-list, by default accept
12:22:41 wireless,debug sj: activated WDS link 00:02:6F:20:FC:B0, name wds2.sj.johan
12:22:41 wireless,info sj: 00:02:6F:20:FC:B0 connected, is AP, wants WDS

I will send also a supout.rif file to support@mikrotik.com

Johan

I have the same problem in 2.9.7 with Senao bridges, on wlan minipci (senao and SR2) that have atheros 5213 (in prism cards not have the problem), my log show the next messages:

wlan1: disconnected 00:02:6F:22:AA:AA, got disassoc: sending station living (8)
wlan1: 00:02:6F:22:AA:AA connected

We have the same problem still!! Once we uploaded to 2.9.x all our clients connecting with Prism's connect for a few seconds then drop off, this happens all the time. THe only thing that solves it is reverting back to 2.8.x. We have tried everything recommended by Mikrotik and other users on the forum, and we have been having this problem since the official release of 2.9. We asked Support to release a wireless legacy driver for the Atheros chipset (we are distributing from 5213) and they said no its old, they then released legacy drivers for the Prism??? We have sent our sip-outs numerous times. All we want now is a fix so that we can finally upgrade to 2.9.x

I only have this problem in channel 2412 Mhz and 2472 Mhz, with CB3.

Have someone the problem on the same channels?

just put legacy wireless for prism cards, and new package for atheros, :D
works fine with atheros in my case :)

Yeah, I'm seeing similar problems: Disconnected, Reassociating, Connected over and over again on the same clients.

So what you are saying is I should remove the wireless package on my production AP, ftp the wireless legacy 2.9.7 package to my 2.9.6 Routerboard 230 and then reboot?

How do I remove just the wireless package (I only see disable/enable).
How do I get the latest Atheros wireless on this then if I'm loading the legacy wireless package?

I've got prism and atheros cards in this Routerboard AP.

Or does 2.9.7 take care of everything?

@INFRALINK

SO DID UPDATING the wireless package solve the problem for you.
am thinking of moving from 2.9.6 to 2.9.7 is it advisable

Has anyone tried this again???

We had to change the AP to another platform. I do want the features of 2.9, but can't have that much trouble again. We lost 2 clients, before we switched.

Joe

Hello,

I get the problems after upgrading from 2.9.

The problem stays with the CB3's on Prism II mPCI
But a lot worse is that my backbone connections with several of cards 5211, 5212 and 5213 has the same problem, the disconnect random.

My problem is also there are running PPPoE sessions over it and the will all disconnect. With the lastest versions of 2.8 the wouldn´t occur, with versions like 2.8.10 we had the same problems.

We use some rb532´s so we could go back to 2.8

I would prompt MikroTik on this problem, bacause I think it´s a serios problem

we are running all 2.9.7 all signals are <-80 and CCQ´s are >20

one of the backbone links exits with this messages

12:22:35 wireless,info sj: disconnected 00:02:6F:20:FC:B0, no beacons
12:22:35 wireless,debug sj: deactivated WDS link 00:02:6F:20:FC:B0, name wds2.sj.johan
12:22:35 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:35 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:35 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:36 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:36 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth
12:22:40 wireless,info sj: data from unknown device 00:02:6F:20:FC:B0, sent deauth (27 events suppressed)
12:22:41 wireless,debug sj: 00:02:6F:20:FC:B0 attempts to connect
12:22:41 wireless,debug sj: AP 00:02:6F:20:FC:B0 not matched by connect-list, by default accept
12:22:41 wireless,debug sj: activated WDS link 00:02:6F:20:FC:B0, name wds2.sj.johan
12:22:41 wireless,info sj: 00:02:6F:20:FC:B0 connected, is AP, wants WDS

I will send also a supout.rif file to support@mikrotik.com

Johan

Johan, please send us the latest support output files from the backbone link when you have such issues.
To other users, if you have problems with the wireless please email to support@mikrotik.com with detailed information on the problem and include the support output files.

Has anyone tested the new packages with lots of Prism based clients?

I am running V2.9.8 RB500 Prism AP in my house and it seems OK. I am afraid to install it again untill more people report no trouble with various clients.

Joe

The solution I use is to set the frequency mode to "manual tx power", and the tx power to "all rates fixed".
Hope this work for you.