one of my wireless adapters witch is set as an access point, suddenly blocks client connections and on registration table shows big numbers on "last activity" column. when i disable wireless adapter, and enable it after, everything works perfectly for couple of hours, then again the same problem. I have to mention that everything works OK with previous version.

one of my wireless adapters witch is set as an access point, suddenly blocks client connections and on registration table shows big numbers on "last activity" column. when i disable wireless adapter, and enable it after, everything works perfectly for couple of hours, then again the same problem. I have to mention that everything works OK with previous version.

Yup, 5.15 is broken. Good results with 6.0b2

are you positively sure about the latest beta version?

are you positively sure about the latest beta version?

What do you mean by sure? You have to try stuff for yourself.

Mikrotik doesn't recommend using 6b in production environments... but their "stable" 5.15 is bad anyway...

Read around here on the forums, you will see various people that are getting good results from 6.0b

Also can confirm the no passwords by script bug.
Sigh...

tk

v 5.15 is SEVERELLY BROKEN !!! It freeze 2.4g interfaces. Clients stay associated, but interface show 0 bytes send and 0 bytes received, and no throughput to assiciated clients. I update several mikrotiks that works perfectly without 5.15 relase and I found this problem. I wish I have a 5.14 or earlier npk files. F**K !

v 5.15 is SEVERELLY BROKEN !!! It freeze 2.4g interfaces. Clients stay associated, but interface show 0 bytes send and 0 bytes received, and no throughput to assiciated clients. I update several mikrotiks that works perfectly without 5.15 relase and I found this problem. I wish I have a 5.14 or earlier npk files. F**K !

have you contacted support about this?

Hello Folks!

Do I dare to rollout ROSA5.15 on our production AP's now
All wireless is nv2 point to multipoint networks ?

Is there any who had problems also with wireless nv2 ?

Thank you in advance.

Hello Folks!

Do I dare to rollout ROSA5.15 on our production AP's now
All wireless is nv2 point to multipoint networks ?
Is there any who had problems also with wireless nv2 ?

http://forum.mikrotik.com/viewtopic.php?f=7&t=60980

Hello Folks!

Do I dare to rollout ROSA5.15 on our production AP's now
All wireless is nv2 point to multipoint networks ?
Is there any who had problems also with wireless nv2 ?

http://forum.mikrotik.com/viewtopic.php?f=7&t=60980

We have no such problems, links are very stable (usaly they are up till next routerboard versions is loaded). We did frequence scan and correct our channel separating on all AP's also splatter effects taken in to calculus and we use directioal antennas with H polarization.

Here we have some problem with RoS5.15.
RoS5.14 is 100% stable exept it generates some autosupout files now and then, maby every second week for the full park.

...I wish I have a 5.14 or earlier npk files...

I'm not sure how many others are still seeding it, but this link still works.

new in 5.15

/interface wireless> multicast-helper=

description ?

Checking this box will send multicast messages in unicast mode, thus greatly increasing the probability of correct delivery, since unicast packets are acknowledged by the receiver and resent if garbled.

This is only useful if you have a small number of clients. If the number of clients is large, the benefit of multicast is lost, since there will be a separate data stream sent to each device associated with the AP, rather than a single multicast stream.

I did some of the testing on a pre-release version of 5.15 to test a multicast feature fix that was reported here.

After many iterations, the multicast feature worked again, having been absent since ROS v3. However a new problem arose: the AP would randomly freeze.

I've been testing to help Mikrotik fix this problem for about a month. I've sent them many, many supout.rif and other documentation. They have seen the AP freeze in their lab, but rarely. I see it nearly every day in my lab, but sometimes I test for a few days and it doesn't fail.

I originally thought the AP freeze was caused by my high speed multicast transmissions, but having read the many reports on this thread, perhaps this is a protocol-independent problem.

I suggest anyone who sees this problem to make a supout.rif file, preferably while the AP is frozen, and file it with a support request to Mikrotik. I have found them to be very responsive if you provide details of the failure.

Many of you can fall back to v5.14, but I need the multicast feature which is only in v5.15, so I'm stuck with AP freezes.

My experience has been that disable/enable of the AP restores it to normal service.

As Normis has said before, the best way to get support for a bug is to contact support@mikrotik.com with as much documentation as you have.

Perhaps someone should start a new thread dedicated to just the AP freeze problem in v5.15.

Version 5.15 is broken.

My AP has been running for years. I just upgraded yesterday and the problems started.
My AP is a RB433AH - Bridge AP (no nat at AP) (average CPU load is 0% to 3%) - two 2.4 Ghz wlans (B-Mode only) - 70 to 80 connections at any time normally about 40 connections to either wlan.
Note - I own all client radios - outdoor antenna - 3 to 10 mile shots.

What happens is one of the wlans (or both) will stop talking - but there are still client connections.
When there is a problem --> Using winbox Wireless-Registration -- under the "Last Activity(s)" column -- all clients show a value between 56000 to 57000 -- none of the clients on the wlan are talking.

I attached a file which is a screen snapshot of the winbox showing the above.

When I disable then enable the wlan, all clients reconnect and start talking again (no reboot needed).

I have seen this three times in less than 24 hours now.

I do not have easy access to my mikrotik AP - it is located on top of a mountian 20 miles away.
Can I remotely downgrade to 5.14 or should I upgrade to a version 6 beta version?

Thank You MT staff

The "set always-allow-password-login=" addition to SSH is much appreciated.

(so ssh in 5.x works like all previous versions and most linux machines allowing both password and key based access)

To downgrade from 5.15 to 5.14 - do I have to use netinstall or will winbox do the job for me?

The problem 5.15 APs are remote and hard to get to - thus I hope I can remote downgrade to 5.14

To downgrade from 5.15 to 5.14 - do I have to use netinstall or will winbox do the job for me?

The problem 5.15 APs are remote and hard to get to - thus I hope I can remote downgrade to 5.14

I downgraded from within the dude on some wireless routers 90Km away, just picked 5.14 and upgrade, guess it also works with winbox. The router restarted and 5.14 was there, no problems.

one of my wireless adapters witch is set as an access point, suddenly blocks client connections and on registration table shows big numbers on "last activity" column. when i disable wireless adapter, and enable it after, everything works perfectly for couple of hours, then again the same problem. I have to mention that everything works OK with previous version.

I've got the same problem with R52H.

To downgrade from 5.15 to 5.14 - do I have to use netinstall or will winbox do the job for me?

The problem 5.15 APs are remote and hard to get to - thus I hope I can remote downgrade to 5.14

Drag-n-drop the v5.14 package to files and then go into the "packages" link and use the "downgrade" button - all in winbox.
Rod

BTW - currently running v6beta2 on select towers - only a couple of glitches - seems to perform very well - keep up the good work MT!

BTW - currently running v6beta2 on select towers - only a couple of glitches - seems to perform very well - keep up the good work MT!

That's GREAT! By the way, what glitches are you having?

BTW - currently running v6beta2 on select towers - only a couple of glitches - seems to perform very well - keep up the good work MT!

That's GREAT! By the way, what glitches are you having?

Just had a glitch actually about an hour ago - AP did the same thing that v5.15 does - shows connections with a crazy time associated and does not pass traffic - reset interface and all is well. Very strange! Also had one of our primaries loose Ethernet ports but not direct RF connections. We are running v6beta2 on one primary Back-haul system that encompasses 12 back-hauls on p-t-p and p-t-mp and also quite a few secondaries and edge towers with APs.
No problem with remote upgrade and downgrades so far and three failures on systems that haven't glitched since the v5.15 tryout.
One thing in common - all were RB433 but in separate configurations - 1. only 5.8bh with APs connected via ethernet 2. two different edge with 5.8 BH and 2.4 AP (BHs never fail but APs do)
Total of three failures now.

Thank you,
Rod

Another screenshot on another AP.
No data on the ones with big numbers.
Run a scan on the interface and the connections are reset and they work - kick the individual connections and they reconnect but no thru-put.
Rod

Exactly same problem wireless card AP mode stoppes after some minutes. Had to downgrade all nodes.
Any idea about which bug causes this?

Another screenshot on another AP.
No data on the ones with big numbers.
Run a scan on the interface and the connections are reset and they work - kick the individual connections and they reconnect but no thru-put.
Rod

Exactly same problem wireless card AP mode stoppes after some minutes. Had to downgrade all nodes.
Any idea about which bug causes this?

seems that the version 6.x is not a new version, but an update 5.x

Please, Link to routeros-mipsbe-5.14.npk because I can't find it anywhere

Please, Link to routeros-mipsbe-5.14.npk because I can't find it anywhere

here: http://www.mirror.mikrotik-bg.net/?dir=v5/5.14/ ... if it's visible from outside Bulgaria.

FYI - I am finding that the problem is on RB100 series & RB400 series & RB500 series & RB600 series

also - on APs with two wlans (2.4 ghz wlans) - sometimes the problem is just one wlan

IPSec is broken since 5.14, flushing doesn't even work anymore. I need to reboot the router multiple times a day. I'm downgrading to 5.13.

IPSec is broken since 5.14

I also have problems with IPSec, tunnel worked flawlessly for months,
but now establishes and expires after 10 seconds (configuration was not changed in any way).
This occurs when MT is initiator, not responder.
Does someone have similar problem???

Regards,

[/quote]That's GREAT! By the way, what glitches are you having?[/quote]

[/quote]Just had a glitch actually about an hour ago - AP did the same thing that v5.15 does - shows connections with a crazy time associated and does not pass traffic - reset interface and all is well. Very strange! Also had one of our primaries loose Ethernet ports but not direct RF connections. We are running v6beta2 on one primary Back-haul system that encompasses 12 back-hauls on p-t-p and p-t-mp and also quite a few secondaries and edge towers with APs.
No problem with remote upgrade and downgrades so far and three failures on systems that haven't glitched since the v5.15 tryout.
One thing in common - all were RB433 but in separate configurations - 1. only 5.8bh with APs connected via ethernet 2. two different edge with 5.8 BH and 2.4 AP (BHs never fail but APs do)
Total of three failures now.

Thank you,
Rod[/quote]

OK - now having more troubles with AP's with the beta on them - rolling back to v5.14.
Rod

Please, Link to routeros-mipsbe-5.14.npk because I can't find it anywhere

I'm not sure how many others are still seeding it, but this link still works.

So - is there an active Mikrotik staff person looking into the 5.15 AP wlan lockup problem or is this problem so far just noted in this forum?

So - is there an active Mikrotik staff person looking into the 5.15 AP wlan lockup problem or is this problem so far just noted in this forum?

You have to contact the MT support for that answer (if you are eligible to do that directly). Forum here is mostly for venting purposes.

there seems to be a bug whereby on 5.15 on an rb411, the serial to ssh passthrough does not work (special login)
it works on 6.0b2

f.

Version 5.15 is broken.

My AP has been running for years. I just upgraded yesterday and the problems started.

So why you upgraded a system that have been working for running/working for years?

I also had wifi problems with 5.15 on RB493 .. clients all got disconnected (unicast key exchange timeout) and clients were not able to connect again but the ssid was still broadcasted. Looks like "one-way" transfer ... disable/enable of the wifi interface fixed it for some days.

i downgraded to 5.14 again and everything is fine.

Version 5.15 is broken. My AP has been running for years. I just upgraded yesterday and the problems started.

So why you upgraded a system that have been working for running/working for years?

Because newer features might yield better performance? For compatibility with newer, possibly not-MT products? Just because a system works doesn't mean it is never necessary to change it.

FWIW, I posted here about a change introduced in 5.x (and continuing at least into 6.0beta2) that rendered our AP-to-AP backhaul links unstable, meaning that the equipment carrying the bulk of our traffic has been stuck at 4.17 while we look for a solution.

5.15 has been pulled from the downloads, it seems... (?)

Meanwhile version 5.15 disappeared from download page.
Obviously it is considered fake officially.

5.15 has been pulled from the downloads, it seems... (?)

20 days is stable and NOW is not stable

5.15 has been pulled from the downloads, it seems... (?)

20 days is stable and NOW is not stable

The bugs were stable. It's actually a good sign that they pulled it; it means they identified a definite problem.

After numerous exchanges of email and submission of many supout files, I've just received a beta of v5.16 which Mikrotik feels has fixed the freezing AP problem.

So far, the AP hasn't frozen, although it will take awhile to convince ourselves that it's really fixed.

The Mikrotik folks worked hard to get this fixed quickly, and I appreciate their efforts.

Thank you all for sending supout.rif files to support. We have able to identify the wireless problem, therefore we removed the version from the webpage. If you have this version running, and have not seen any wireless issues, you can keep using it, otherwise this version is working fine.

If anyone wants to test the fixed v5.16 before we released, contact support please

5.16 0905 release?

If anyone wants to test the fixed v5.16 before we released, contact support please

yes that one

Currently, we are using v. 5.15 at least 2 weeks until now and found nothing about wireless problems.

Currently, we are using v. 5.15 at least 2 weeks until now and found nothing about wireless problems.

In that case, you don't need to update.

On 751g-2Hnd with AP enabled after 3 days of running no problem i see 2 wireless networks same SSID, one encrypted the other not.
It should be just the encrypted one.

me too, since i upgraded my RBSXT i found nothing problem.

The Mikrotik folks worked hard to get this fixed quickly, and I appreciate their efforts.

yes, me too.

Dear Mikrotik,

would you please inform us if there are any improvements on nv2 wireless link stability?


Thanks

Dear Mikrotik,

would you please inform us if there are any improvements on nv2 wireless link stability?


Thanks

Changelog does not list anything wireless related, so apparently there isn't nothing for NV2.