Just curious, what were the additional fixes for bgp instances?
Those were WinBox related fixes regarding AS number setting/displaying.
Will there ever be WinBox fixes to properly handle Templates vs Connections (and similarly Profiles in the WiFi driver)?
I.e. when something is set in a Template and not configured in a Connection, will the Template setting remain inherited instead of copied to the Connection when some other parameter is modified?
This situation seems to be leading to a lot of confusion when working with Templates and Profiles.
Yes, I've confirmed that the bug has been resolved. The issue that occurred was that the routing selection didn't respond to the correct active routing when there were two or more routes advertised using BGP VPN from CE to two different PEs.
Hi,
it happend again.............
Hap AC3 as wireguard client has been disconected from wireguard server after upgrade from RC3 to RC4. I had to pouse and unpouse in the IP/route subnet of the wireguard server to get it back conected.....
What's new in 7.20rc5 (2025-Sep-26 11:44):
- bridge - fixed incorrect port STP state after bridge MAC address change (introduced in v7.20beta3);
- container - fixed setting custom dns-servers (introduced in v7.20beta2);
- snmp - fixed issue where OID could be returned more than requested in SNMP GET/GETNEXT queries (introduced in v7.20rc1);
SUP-196466
if your box has more then 92 Cores (all platforms x86 and arm64), only the first 92 are used about interface queue's irq.
This limit the x86 dual cores and Ampere 128 core boxes!
Hi. Will we soon have a solution for E50UG PPPoE limitation that affects all interfaces?
It's a great catch. But, really, I must say I envy whoever gets to put his hands on this kind of hardware... ![]()
think about those one have the hardware and don't get the benefit! ![]()
No mentions to CVEs?
https://youtu.be/lwQHRtrmmK8?si=qMNJgPXZDEOVZl8x
What is that at 17:00
as it appears to be a flat case its probably the CRS812 DDQ
wow, I mean whow, 98DX7335, the first chip in CRS, which support HW forwarding capability based on MPLS-SR and SRv6, are these on the roadmap? ![]()
...and MACsec (;
If the layers and separations between data plane and control plane are respected, what the hardware offload will forward does not depend on which protocol generates the FEC. It could be MPLS-SR, BGP-LU, RSVP, or LDP.
You can even do hardware-based forwarding of static label routes, if you want and the NOS permit.
The problem is that, from what I can see, this separation is a long way off.
Hardware-based MACSEC, on the other hand, depends directly on switchchip support.
Combining my Spidey-sense and the acceleration of the release cadence, I feel that we will have another rushed version resulting from the launch of a physical product.
After installing 7.20rc5 i noted something strange on the IP Service list, a new Dynamic service ww2. Every 10 sec it appears for 2 sec each time with a different port number. Can someone explain this behavior to me.
There is still the issue that after upgrading a CHR a lot of disk space is lost that comes back on the next reboot.
This time I upgraded from rc3 to rc5 without doing the extra reboot, and after rc5 started it displayed a couple of "no space" errors and could not save configuration changes.
After another reboot there still is space, but I hope this issue is resolved at some time. It affects only CHR, not the MikroTIk hardware devices.
Version 7.19.5 seems to have been created for these new products.