Hi,
We are a telecommunications operator using Mikrotik as OOB device, and use massively RB4011 + Wireguard + BGP to deploy our OOB.
Since 7.15 upgrade, we notice a memory leak progressively growing on ALL our RB4011, but not CCR2116 nor CCR1072. Have you experienced this kind of incident with the new release?
Regards,
Seems you’re right - running rb4011 with wifi. basic firewall and routing, bgp, wireguard, … and ever since the upgrade memory utilization is slowly but surely going up.
Nice to state here but better to send supouts and report to MT directly.
Yep, ok i’m not alone, bug report opened.
Thank you!
I observed that on the devices I have that are memory leaking too, clicking the “Stop” button on BGP sessions frees up to 400MB RAM.
I am making supouts before and after stopping BGP session to open a bug report.
Could it be related to the one of these recent changes to bgp or routing ?
*) bgp - added initial vpnv6 support;
*) bgp - correctly synchronize input.accept-nlri address list;
*) bgp - fixed prefix count when BGP sessions run with multiple AFIs;
*) bgp - fixed selecting local.default-address from wrong VRF;
*) bgp - use IPv6 as default address-family for IPv6 sessions;
*) bgp-vpn - use VRF interface as gateway for leaked connected routes;
*) route - do not allow routes with empty “dst-address”;
*) route - do not redistribute loopback address as connected route;
*) route - fixed bgp-vpn prefix import with the same route distinguisher (RD);
*) route - improved system stability;
*) route - rework of route attributes;
Guess it’s gonna be fixed in the next release…
SUP-154936
RB4011 RouterOS 7.15 memory leak
MikroTik Support
Yesterday 3:56 PM
This is an automated message. Our bug tracker reports, that your issue has been fixed. This means that in the upcoming days, we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out soon. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release.If you’d like more details about the version release date, please answer to this message and one of our support engineers will contact you.
Best regards,