In version 6.43.12 still not resolve.
This would be a good function to able to control the device under DDOS attacks on conntrack table.
(I need to control 900kpps on CCR1036)
Is this the new API that sends the password in plain text?? I cannot figure WHY you guys would revert to that way of operation.update your api
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login
I did - and that does workTry to upgrade the 6.40.4 first to the current version (6.42.5) and then upgrade to 6.43rc from there.
That comment made me smileWell, saying it is not crazy, the fact that it happens for some versions is a different question
What would you have Mikrotik change about MNDP's behavior? Requiring authentication of some kind is counter to the purpose of MNDP.
Thank you for that. I will keep my eyes open.Groove is still on track, for this month.
Already upgraded to 2.18. That makes no difference.Upgrade the firmware
T
I think that may be a bad idea!!nope, there will be rc12 out shortly. Just saying rc12 has a fix for this.
There is no RC12 at the moment. Is this a typing error on your part?Also, know crash issue in rc10/11. Upgrade...
Thanks Uldis. Would be great if you could do that. I'm still running some older 532's. I think the memory leak in v3rc6 caused the watchdog timer to kick in and reset the clock back to 266MHz.we will try to fix it in the next version.
Don't want to jump to conclusions here but someone still running v2.9.6 from Russia...............We have a small WiFi Hotspot running on an MT v2.9.6 router