Skip to content

Helper scripts to upgrade routeros to the latest version#121

Open
mbonastre wants to merge 1 commit intoeworm-de:mainfrom
guillen-eu:guillen
Open

Helper scripts to upgrade routeros to the latest version#121
mbonastre wants to merge 1 commit intoeworm-de:mainfrom
guillen-eu:guillen

Conversation

@mbonastre
Copy link
Copy Markdown
Contributor

The RouterOS scripts from https://github.com/eworm-de/routeros-scripts require a recent routeros version (7.19 as of 2026-03-11).

It is not rare to have an older version when reinstalling a Mikrotik router that has not been updated for a while.

So, the first step I do when configuring a new or old router is to upgrade the RouterOS to the latest stable version.

This usually requires multiple reboots because the upgrade process not always goes directly to the last version.

Also, upgrading the firmware requires an extra boot.

The simple-routeros-update.rsc doesn't use any functionality the requires a specific RouterOS version, so it should work with almost any router. (I have upgraded routers from v6 using this method).

The shell script is just a wrapper around ssh/scp to launch the rsc script.

The RouterOS scripts from https://github.com/eworm-de/routeros-scripts require a recent routeros version (7.19 as of 2026-03-11).

It is not rare to have an older version when reinstalling a Mikrotik router that has not been updated for a while.

So, the first step I do when configuring a new or old router is to upgrade the RouterOS to the latest stable version.

This usually requires multiple reboots because the upgrade process not always goes directly to the last version.

Also, upgrading the firmware requires an extra boot.

The simple-routeros-update.rsc doesn't use any functionality the requires a specific RouterOS version, so it should work with almost any router. (I have upgraded routers from v6 using this method).

The shell script is just a wrapper around ssh/scp to launch the rsc script.
@mbonastre
Copy link
Copy Markdown
Contributor Author

Duplicated PR because I closed the other PR by error.

As I said: I hope you find this useful. But do not hesitate to turn down the PR if you think this doesn't fit in your repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant