Update from 3.0 to 4.0


can somebody please tell me ho i can update from Version 3.x to 4.x ? I want to do it over cli or luci. Please tell me what i must do.


You can do even better: since at the moment it is not possible to update directly from 3.x to 4.x you will have to use the 4 led mode with USB key. Go to http://repo.turris.cz/ and download the medikit from your hbs folder to your device (currently Turris OS 4.x only supports Omnia and MOX). Follow the procedure at https://docs.turris.cz/hw/omnia/rescue_modes/ (for Omnia) or https://docs.turris.cz/hw/mox/rescue_modes/ (for MOX) and the game it’s done. The previous configuration in any case will not be preserved.

Thanks a lot. About the config of the turris. If i make a backup from the config will it work that i install the backup file from version 3.x to 4.x

Good question. I’d advise to better not doing that. I’m quite used to upgrades on native openwrt and it sometimes broke severely when keeping the configuration (that’s similiar to trying to restore it on upgraded Turris).
But you can use the backup config to easily copy and paste code from the backup files to the new files on your router via SSH.

The configuration is not compatible, because different things change between the two versions, being based on two different bases (OpenWRT 15.05 and OpenWRT 18.06.5). You’d better do it again, but it’s worth it.

1 Like

ok thanks a lot for info

I no longer have a working EEPROM so use an internal SSD, are there any specifics I should be aware of if I want to update to 4 ?

I understand broken compatibility 3.x to 4.x, but could anyone competent describe how to move OpenVPN keys from old to new firmware? Thanks!

Just export your latest schnapps backup before doing the update and you will be able to restore any file you want.

Really? Schnapps backup? Isn’t that dangerous? Wouldn’t it overwrite back the files that were created during the reflash?

Either just download the concerned keys/certs via ssh file browser to a client for safekeeping and upload back to the router after the move to 4.x
Or, create a snapshot of TOS3.x prior the upgrade to TOS4.x, export the snapshot to the /temp directory on the router - download it from there to a client. After the move to 4.x extract the keys/certs from the snapshot at the client (it is just a compressed archive) and upload it back to the router.

If you use different partitions for 3.x and 4.x just copy (cp on the ssh shell) from the 3.x partition (has to be mounted) to the 4.x partition.

Obviously the backup should not be restored but mounted elsewhere to allow easy file copy or diff.