Mikrotik Support analyzed my supouts and says that my problem is still hardware and wants me to RMA again. RMA roulette is not a very fun game to play. It is even more painful because I made the mistake of buying from a random Amazon Marketplace seller who had a great purchase price but who has pret...

I have a hunch this might be caused by the L2TP client. Are any of you seeing this issue not running an L2TP server or client?

Sigh, the new RB4011 that I received as a replacement for this problem started doing this today, too. The profiler gives no clue as to which process is actually pegging a core. It hadn't fully hung yet when I caught it, so I actually got some decent supouts as it was happening this time, so hopefull...

*) fixed problem where switch locked up after a while and only small packets could be sent;

Hooray! I've been waiting for this fix for a long time.

The default in RouterOS for L2TP is 1450. I was confused about this too because I can enable IPSec over L2TP with the same default MTU, and it still works without dropping packets. My IPSec configuration has been negotiating cbc(aes) + hmac(sha512) encoding. I have MRRU off, and the ESP packets are ...

This just happened to my CSS326-24G-2S+ running 2.10. It started balking after 17 days of uptime. Pings were fine, but any serious traffic would hang after a packet or two. Now that I think about it, it seems like maybe the ping packets were small, and larger packets would hang, maybe? I don't know ...

After opening a ticket with Mikrotik Support, they determined that the cause was faulty hardware. They are aware that some RB4011 hardware has flaws that can cause this and the warranty should cover a replacement.

I believe this bug has also bitten me. CPU goes to the extreme, and eventually, the system grinds to unresponsiveness. It doesn't reboot; it just sits there constipated. Maybe it could be a thread leak? It is syslogging to a remote server and there aren't any errors. Instead, it goes silent without ...

TL;DR: Please: add a reverse-resolution option to monitoring tools let the DNS-update tool submit PTR records let the IPv6 DHCPv6 server provide the RFC4704 FQDN field to the binding-script. I believe that both forward and reverse naming every device brings order and humanity to a well-designed netw...

It has been a year since this post. I wonder if anyone at Mikrotik has ever noticed it? Why are they so silent on this?

How about simply adding a dns-update parameter to let us specify the record type instead of always updating an A record? One would think this would be a relatively simple change.

Please add my +1 vote for ECMP, too.

I do require more IPv6 functionality (like policy routing, hopefully also NAT66) somewhat urgently for a production environment, not really the place to run early beta versions. Best would be when that appeared in v6 but as I understood, no more work is being done on IPv6 in RouterOS v6. That is no...

There is a real need for RFC6296 IPv6-to-IPv6 Network Prefix Translation. No, this is not Port Address Translation or Masquerading. It is straight, simple, 1:1 prefix swapping. It takes simple bitwise operations to swap prefixes. No connection tracking is required. No state is required. No, this isn...