MikroTik

Hello,

I've got big trouble with my mikrotik devices. I use Dude and some custom software which is contacting the devices via the API connection. Since v4 the API connections won't disconnect and the active user lists is full after a few days. After a month no new api connections are possible, even the dude fails to log in. There is no login message in the logfile.

I would say this is a critical bug.. so lets see what mtik does about it (i've reported it when 4.6 was the latest stable release):

What's new in 4.7:

*) fixed problem - wireless packet bridging with nstreme enabled
sometimes was very slow on RB1xx, RB5xx and RB4xx;
*) fixed problem - ipv6 traffic was not bridged if ipv6 package was not enabled;
*) '/user active' now lists type of api connections as 'api'


well something happened, but now api connections are listed as unknown.. congratulations.. they still won't disconnect..

Yesterday i ran a new try and contacted mtik support. Here the answer:

-------
Hello,

Thank you for the report, it is known problem and was fixed in beta versions, however it is not so easy to backport it to v4. We will fix it in one of the future versions.

Regards,
M
-------

This is what i call customer relationship! No fix since 5 versions... And no chance to fix it by myself, as routeros is closed source.. great! tell me why i should buy mtik hardware?

Same thing with a bug concerning the ovpn server.. in v4 and in v5beta the ovpn server stops accepting incoming connections. Here the answer i got from mtik support:

-------
Hello,
There are known problems with OpenVPN. But I can't give you
any timeframe when these problems will be fixed. If it is a
critical I would suggest to use another type of tunnels.
In v5 we are adding SSTP protocol (PPP over STL). Which is
far more superior over OpenVPN.

Regards,
M
-------

I hope these things could be fixed soon, as i am not willing to pay for a closed source software with this kind of support.. and i hope that this thread won't be deleted (but i expect it somehow ).


Regards,
disappointed customer

it is known problem and was fixed in beta versions, however it is not so easy to backport it to v4

just... laughing with one eye and weeping with the other...