I have exprienced weird problem one of our hotel installations.
Problem is after a year later three of our outdoor ap’s stop transmitting after a while like it is freezing, showing clients connected in registeration table some of them with huge last activity time. I have to disable and enable interface to start working again. I tired every possible tuning option (ani/rts/cts/dfs/ack timeouts etc.) none of them helped, i also check frequency noise floor is at -89,-100 range but clients are affecting regardles of their receive strenght (-49 dbm client also affected). AP’s are different models (rb600, rb433ah) and have different radio cards (r52h, engenius, jjplus) all of them stop transmitting (tx rate drops to 1Mbit rx still fine 54Mbps). Masts have grounding but taking heavy winds. I used 70 degree circular polarized sector antennas and LMR400 cables.
Does any one has an idea about what is causing this?
It was working for a year and you made no configuration changes during that time, and now it doesn’t work? Sounds like hardware has gone bad. Make sure it is getting stable power. Try swapping out radios.
Yes i only did upgrade routeros and firmware.
There is a power stablity problem but i cannot relate problem with this it should effect power adapter not the wireless cards plus grounding is fine, all of effected nodes are outdoor modules indoor modules are working under much heavy load (20 connections per outdoor sector total 60 per node at max. 50-60 clients per indoor radio working perfect) .
I torched interfaces actualy there is a lot of broadcast and multicast traffic going on but clients are unable to enter bridge to get an ip address from hotspot/dchp hotspot logs are full of offering lease without success.
If i disable and enable interface manually traffic goes to normal for a while (10 to 50 minutes).
When the problem starts affected radios are accepting new clients transmit few packeges (like dhcp requests) then freezes tx traffic (still getting requests from clients but doesn’t answering them).
About a week before problem starts, i upgraded 5.14 to 5.15.
It worked very well for a week then this thing happened, plus all other indoor nodes are upgraded also and they are working fine.
I thoght may be it was related with multicast option which introduced in 5.15 but enabling and disabling doesn’t make any difference only thing works regulary enable and disable interfaces via schedule.
when this problem starts last activity timer went crazy showing 21769.650 seconds on some clients.
Well it is a right hand circular antenna from luxul wireless. It has built in nosie filter by circular design and execptional wall penetration for nlos installations (like buuilding covarege) as twice as better than any other vertical polarized sector antenna at same dbi.
I use 11 dbi sectors but i get better results than 17 dbi regular sectors, i think it is because 17 dbi has very narrow vertical angle compared to 11 dbi 70 degree Hor. 36 degree Ver. angles of circular antenna and built in noise filter of circular design.
I tried to downgrade one of outdoor nodes i hope it will work.
Yes this is.
I downgraded 5.14 all of problematic nodes are returned to normal execpt for one it still has some weird ping drops and traffic freezes, i think problem was 5.15 upgrade. it somehow effected max client count of radio cards.
Under light usage 5.15 seems fine but under heavy client count with lots of hidden nodes, low powered mobil devices routeros reveal its buggy behavior.
I hope they fix this as soon as possible.
its not hardware problem its not power problem something wrong with MT OS 5.9-5.15v cos its not happaning on 1RBoard it is happening on 14-15 RB’s
one or two mounts ago I don’t have this problem
Mikrotik has found a bug in v5.15 that causes the AP to randomly freeze.
Version 5.15 has been removed from the download page.
I’ve been working with Mikrotik for several weeks on this and they just gave me a beta of v5.16, which, so far, has been stable, with no freezes.
Don’t use v5.15 for wireless; use v5.14 until v5.16 is available.
Also, as the Mikrotik folks have told me and others, if you find a bug, submit a supout file to support@mikrotik.com. It’s fine to post reports on the forum so we can all share our knowledge, but the support email is the right place to get their attention regarding bugs.
If you are using v5.16, you shouldn’t see this issue.
What version are you using?
Or are you letting us know that you were able to resolve this problem by going to v5.16?