*) routerboard - added RouterBOOT "auto-upgrade" after RouterOS upgrade (extra reboot required) (CLI only);

As many other features, also this one is only in rc state and is still work on progress. At the moment it only executes "/system routerboad upgrade" feature after RouterOS upgrade if "auto-upgrade=yes". After reboot latest firmware is applied.

I don't mind to wait for 2 reboot instead of one, if it'll go automatically.

As many other features, also this one is only in rc state and is still work on progress. At the moment it only executes "/system routerboad upgrade" feature after RouterOS upgrade if "auto-upgrade=yes". After reboot latest firmware is applied.

I don't mind to wait for 2 reboot instead of one, if it'll go automatically. Really, it'll save me another login and issuinfg the same command and then run another reboot.

BTW, will PoE port(s) firmware be upgraded as well?

:log info "Checking firmware...";
/system routerboard
:if ([get current-firmware] != [get upgrade-firmware]) do={
     :log info "Updating firmware";
     upgrade;
     } else={
     :log info "No update."
     }

As many other features, also this one is only in rc state and is still work on progress. At the moment it only executes "/system routerboad upgrade" feature after RouterOS upgrade if "auto-upgrade=yes". After reboot latest firmware is applied.

I don't mind to wait for 2 reboot instead of one, if it'll go automatically. Really, it'll save me another login and issuinfg the same command and then run another reboot.

BTW, will PoE port(s) firmware be upgraded as well?

Maybe I'm reading like a lawyer, but I don't see anywhere that says the second reboot will happen automatically. "After reboot the latest firmware is applied" doesn't actually say the new feature actually issues the reboot. I just see a commitment that the upgrade will be scheduled if there is an upgrade outstanding, meaning somebody still has to intervene to reboot the router to apply it. I've had that functionality for years -- an eight-line script, triggered every startup by /system schedule:

Code: Select all

:log info "Checking firmware...";
/system routerboard
:if ([get current-firmware] != [get upgrade-firmware]) do={
     :log info "Updating firmware";
     upgrade;
     #  Automatic restart
     :delay 2s
     /system reboot
     } else={
     :log info "No update."
     }

The same script, just set to restart automatically, so I do not have to click manually.

The same script, just set to restart automatically, so I do not have to click manually.

Yeah, I'm extremely wary of automatically scheduling anything that may result in a boot loop that I can't interrupt.

For example, just this week or so a change in 6.41 renumbered firmware to match the RouterOS release number. Except on older devices the upgrade firmware field showed up blank! This script would have looped forever, because the current firmware would never have matched the ("blank") upgrade firmware.

This is an eventuality that RouterOS would have to address if this procedure were ever made automatic without requiring a script. It would require some sort of stateful execution cross-reboot.

Sorry for the dump question, but where i find this command, on terminal ?
i cant find it
thanks

Sorry for the dump question, but where i find this command, on terminal ?
i cant find it
thanks

The command to update firmware is /system routerboard upgrade

If you are asking about some other command, please be more specific what command you are asking about.

For example, just this week or so a change in 6.41 renumbered firmware to match the RouterOS release number. Except on older devices the upgrade firmware field showed up blank! This script would have looped forever, because the current firmware would never have matched the ("blank") upgrade firmware.

I don't mind to wait for 2 reboot instead of one, if it'll go automatically.

If the second reboot happens automatically before any network connectivity is up, then I don't mind that either. ROS boots rather fast (compared to the likes of Cisco for example).

For example, just this week or so a change in 6.41 renumbered firmware to match the RouterOS release number. Except on older devices the upgrade firmware field showed up blank! This script would have looped forever, because the current firmware would never have matched the ("blank") upgrade firmware.