I have a problem. Since I have upgraded a couple of groove from 5.9 to 5.12 i get a lot of "lost connection, medium access timeout". They were working ok with 5.9. I will try to downgrade an see if the problem disappear. Anyone had similar problem?

You think this?

I can confirm that after downgrade to 5.9, groove is working OK. Can mtk guys join the discussion regard this problem?

I discovered it after moving to 5.11, it occurs every day, but only on one of the two grooves that I have. It's the groove with the weaker signal strength (-72 dBm) that gets this 'medium access timeout', the other one (-55 dBm) works flawless.

Where can I download 5.9? Thanks.

First groove: 57/60dBm, 92/91CCQ signal to noise 57bB
Second groove: 54/52dBm, 99/98CCQ signal to noise 63dB

On booth of them everything is OK with 5.9 downgrade. By looking at 5.10 changelog, I have found out that they have changed something about snmp. I am using snmp for dude signal reporting. Maybe I am wrong, but you can never tell:

"snmp - provide extended interface statistics when availabe"

I can't experiment any more with those grooves because they are used by important clients!

I am keeping almost every version of mtk just in case that i need it in the case like this.

If you can't google it send me PM and i will upload it somewhere for you...

5.9
http://download2.mikrotik.com/routeros-mipsbe-5.9.npk

Thanks for the link. I disabled snmp and I will give you an update shortly if this makes a difference.

Do I downgrade in the same way that I am used to do upgrades? I never did a downgrade before.

Copy old version to the routerboard, and then instead of reboot, go to system - packages. There you will find downgrade button...

the issue is only happening when you use nv2 or 802.11 wireless protocol?
Is it happening when you disable the snmp?

I am using NV2. Unfortunately I can't experiment any more. 5.9 is working, so I'll be waiting for solution...

I am using 802.11 and SNMP is off. I can experiment

thanks for the advice. after disabling snmp the issue is gone. it is nv2