RouterOS version 6.49.14 has been released in the "v6 stable" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.49.14 (2024-Apr-03 17:26):

*) defconf - do not override default DHCP server lease time;
*) smb - improved service stability when receiving bogus packets;
*) timezone - updated timezone information from "tzdata2024a" release;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while a router is not working as suspected or after some problem has appeared on the device

Please keep this forum topic strictly related to this particular RouterOS release.

Nice to see New Updated in V6

Will it become Long-Term?

Yes, but not immediately, we will make sure this release doesn't introduce new issues, and then promote it to long term in time.

On two separate occasions, including this one and another, I've experienced my MikroTik hAP ac3 dying after updating RouterOS and Routerboard.

My usual process is to update RouterOS first, then restart, and then install Routerboard if there's an update available. However, on both occasions, my router has died after updating Routerboard. The update is applied and then the system restarts, but afterward, everything stops working. The LAN symbol blinks faintly, but nothing else happens.

The solution has been to reset the router, then I can access it to update Routerboard again, restart, and finally restore the backup.Am I doing something wrong, or what could be the issue? How can I troubleshoot if it happens again?

On two separate occasions, including this one and another, I've experienced my MikroTik hAP ac3 dying after updating RouterOS and Routerboard.

My usual process is to update RouterOS first, then restart, and then install Routerboard if there's an update available. However, on both occasions, my router has died after updating Routerboard. The update is applied and then the system restarts, but afterward, everything stops working. The LAN symbol blinks faintly, but nothing else happens.

The solution has been to reset the router, then I can access it to update Routerboard again, restart, and finally restore the backup.Am I doing something wrong, or what could be the issue? How can I troubleshoot if it happens again?

Wrong topic?

What is now the default DHCP lease time? Before the defconf change it was 10 minutes, I changed it to 1 day as that seems more reasonable, Winbox doesn't let me leave it empty.

On two separate occasions, including this one and another, I've experienced my MikroTik hAP ac3 dying after updating RouterOS and Routerboard.

My usual process is to update RouterOS first, then restart, and then install Routerboard if there's an update available. However, on both occasions, my router has died after updating Routerboard. The update is applied and then the system restarts, but afterward, everything stops working. The LAN symbol blinks faintly, but nothing else happens.

The solution has been to reset the router, then I can access it to update Routerboard again, restart, and finally restore the backup.Am I doing something wrong, or what could be the issue? How can I troubleshoot if it happens again?

Wrong topic?

Don’t know where to put it. I got the issue after installing this update

30m according to docs.

I've just checked on a spare RB750UP and it is actually 10 minutes (yes I have reset to defaults after upgrade to 6.49.14, even twice) even if that value was removed from the defconf script.
Just curious why this fix was considered so important to be backported to 6.49.14 - doesn't really look like a security fix (correct me if I am wrong, perhaps I'm missing something and there is more to it than it looks on the surface).
My bug #[SUP-126246] comes to mind, reported a few months ago in 6.49.10, still not fixed in 6.49.14 - it was about "Winbox IPv6 ND reachable-time units" which are wrongly shown in Winbox as "ms" while the value itself is actually in seconds (yes a trivial change of Winbox units label only, should be "s" instead of "ms", value itself is fine and the CLI not affected either), bug introduced between 6.47.9 and 6.47.10 (a long-term release!), yet support replied: "This has been fixed in RouterOS V7, in RouterOS V6 branches this won't be fixed as V6 updates will only include security fixes."

at least this problem exists:

viewtopic.php?p=1064954#p1064954

I`ve just installed this version on my RB4011.
I`ve got a problem with my ipv6.
DHCPv6 client is getting prefix normal, but all my clients were unable to get to get IPv6 address anymore.
Updated from 6.49.13 also routerboard firmware was updated.
Downgraded to 6.49.13 again, all is working normal.
i really think something is wrong with Version 6.49.14 ...

New version v6.49.15 has been released:
viewtopic.php?t=207049