ok, is anyone else seeing this issue? Please speak up if you are.. this is getting worse and worse. Last week it was on 2 nodes. this week, it is now affecting 5 nodes.
I have it on every one of my RB532 boards. Makes me VERY wary of making any changes to anything, for fear of dumping everyone off and having them not come back.
Why does this happen??
Adam
Obviously there is a problem either within mikrotik or the cards. I am wondering why someone from mikrotik hasn’t chimed in yet to let us know which one it is. At least let us know which cards do work fine with this configuration.
This is what I was going to upgrade all of my APs to and use for all of my new installs, but am going to start testing other hardware now.
When I had sent this complaint to Serjegs, with the corresponding Supout file, AND the log, Serjegs told me that I needed to get better clients; suggesting the Rb133C.
Come on MikroTik… There are more people with this problem than I. We need some support from either M.T. or Ubiquity Networks.
Keep in mind that I have the same problem with the R52, SO: this makes me consider that we have a RouterOS issue.
But, then again, I am a noob after converting to MikroTik from BriLan.
Adam
Better CPE? I thought their 133 boards were having the same problem. From what I have heard it happens with just about every chipset out there for CPEs.
Maybe we need to find better APs? Haven’t had this type of problem with any of the other APs I have had.
I’ve got 2 RB133c as a ptp bridge.
2 rb133c ROS 2.9.38
2 SR9
2 13dBi Pacwireless yagi
Laptop AC as the 18v Wisp-router recommended wasn’t enough.
Every time I make the slightest change to the AP, try to find a clearer channel, etc, the CPE (of course, at my home) refuses to reassociate.
I have to change the AP back to previous config, change the client, then change the AP, then reboot the AP. This is a pain in the @#$@#$. I have a thread about it, not a response that I’ve seen. Its somewhere along the bottom of the page.
If I remotely change the AP without power cycle, the CPE will not reassociate. Even with watchdog. Apparently, a soft reboot won’t do the job. I can see the AP sometimes, but cannot associate.
I have to change the AP back to previous config, change the client, then change the AP, then reboot the AP. This is a pain in the @#$@#$.
Next time this happens just try to disable - enable the card over and over till everyone connects , if that works, then you are in the same boat as the rest of us.
What I do is do a MAC ping on one of the 133 clients, the I start re-enabling the card, I can tell when it works cause the ping times on the 133 goto 2.. if it doesn’t work, then they ping with 80%packet loss and 500ms+ ping times.
I wonder if the reason MK doesn’t see it in testing, is they don’t have a big enough test set up, I have at least 20 people on the least crowed card that is having this problem.
This is exactly what I am seeing too.
I am about to roll out one of the RB133Cs in the field on Monday. I hope this doesn’t make the situation any worse.
In the mean time, I wish that someone from MikroTik would help us address this. I do concur, the problem happens when the A.P. sees more than fifteen clients.
One or two, no problem at all.
Adam
Is there anyone having this problem with a NL-2511MP in the AP and all prizm CPE’s?
I think if you have all Atheros (AP and CPE) or all Prizm you don’t have this problem.
Maybe somethimes things work fine untill you hit that magic number of clients and then things go nuts.
My network is made up of 70% CB3, 5% Deliberant, and 5% Tranzeo. I never had any problem till I started adding RB133 with R52 cards in them. I dont have the problem on nodes where there are no mikrotik CPEs, I dont have this problem if I user Prism chipsets in the APs, but when I do that I get all sort of complaints, the prism cards are just not good enough in crowed environment.
I have an old routerboard don’t remember the model number, running prism and never have a problem using Mikrotik 2.8.21. Have a mix of tranzeo, CB3s, zinwell, and Smartbridges for CPEs. Been up for over 2 years without a problem.
The only reason I upgrade to Atheros cards is when I start getting a lot complaints, With Prism you cant see the noise, nor any CCQ readings. When I switch to atheros, I get both, and I am able to track down and fix these types of noise/CCQ issues. That has been working great for about 1 year.. then suddenly a few months ago this disconnect problem started happening, I replaced everything , Motherboard, wifo cards, pigtails, antenna,powers supplies, and nothing worked. then after looking at some other nodes, I noticed they were running prism cards. so I stuck in the prism card, and everyone connected. But that I had the old complaints of slow service at night, bla bla.. high ping times.. so I am damned if I do, and damned if I dont.
Hi guys ,
i have same problem with XR5 with 2.9.42 . When use winbox to control/config the AP , the system come instable. Deauth , variation of noise-floor ( from -100 to -115 ) .
RB532 with 2 miniPci ( 1 XR5 and 1 SR2 ) , but with problem only on XR5.
an suggestion’s ?
Just to let everyone know I have seen the same problems and my clients were tranzeo and teletronics. I’ve had several people tell me not to mix client equipment or you will see problems ( prism or atheros) . Although you can use a tranzeo AP and not see these same issues, just high ping times and mad customers. I had tried the sr2 about a year ago but these issues weren’t getting resovled. Then I got lucky and lightning struck it dead so I put another unit up with the 2511 card and all was well. Then about a month ago I tried to install a Tr-cpq on this tower and it won’t connect to the prism card in the AP although ealrier firmware versions of the same unit would ( strange ). So within the last month I installed another rb532 with an xr2 to see how things go. Its still up in the air because this tower only had 12 clients but I have seen a small case of the connection issue. By this I mean I only need to disable and enable a few times and all is well. Sometimes never. I’m getting ready to deploy 3 more xr2’s were I currently have a tr-4500 with about 60 clients and use pac-wireless omni sector on it so I will have more to report in about a week. I hope all this compatible equipment becomes compatible sooooooooooon!!!
My link is ptp, rb133c and SR9 on both sides. About as simple as you can get.
Hi everyone
I’ve read through all the post’s on this thread to see if I can find a common factor or more. I think I have the same kind of problem on my AP with an Atheros chipset, SR2. Someone mentioned it only occurs on AP with more than 15 clients on the interface, mine has 30, so with that I concur, because while most of my other AP’s run on Prism 2511 where I have more than 15 and up to 30 clients or more with no problems whatsoever. I have other AP’s running Atheros but with less than 15 clients at the moment where I have not seen the problem described.
Further I don’t think it is Mikrotik OS related, because I had the same problem on a Wrapboard running 2.8.28 with the SR2 in, when the same problem started happening when my clients became more than 20 on the AP. I then replaced the setup with a RB532 and Mikrotik 2.9.23 and still the same problem exists. When something happens that causes all the clients to connect simultaneously again, like power failure or scan or setup changes etc, the AP struggles to connect all the clients again, and those that do, have slow traffic and high pings. It only happens on the interface AP with the many clients, the other atheros AP in the bridge with about 8 clients never has the problem.
It might still be a driver issue though for the Atheros cards which Mikrotik uses?
I think all of us with the problem should write down their configs like, hardware (wrap or RB’s or other), software (Mikrotik version etc), Wireless card used in AP, bridge config or not, how many clients on AP, type of clients (mixed or not), wds or not, etc
Mine is:
RB532 with 2 SR2’s in AP-bridge mode setup in a bridge
AP interface with the problem has 30 clients, mix of prism CB3 and mikrotik with atheros card clients
Mikrotik OS 2.9.23
no WDS
Best regards and hoping for a solution soon
Albie
I am seeing the problem on every A.P. that I use the R52 or SR2 on.
My A.P. configs are as follows:
24 clients:
RB532
SR2
Router OS 2.9.43
25 clients PLUS WDS:
RB532
R52
Router OS 2.9.43
And yes, I have the same problem on both of these units. It is both disturbing and annoying.
Adam
Is there anyone out there that is NOT having trouble with Atheros chipsets and prism clients? This problem is not going away, and needs some mikrotik attention.
I’m also having these issues, pretty much as everyone else has described them. Sometimes it helps to change the MAC address and B/G vs B only modes on the AP.
I run in B mode only on all my nodes, no G cpes in my network..