Create an upgrade path from the legacy firmwares to Gluon about gluon

[sargon]

One of the problems with upgrading from old firmware is the failing ssh login afterwards.
So when a root password is set in the system the upgrade path should enable ssh login.

[neocturne]

I'd also expect the network configuration to be completely broken? There is absolutely nothing of a sane upgrade path in place yet, so reporting issues about it doesn't really help ;)

[sargon]

Yes, Network is broken also, just checked that.
Just wanted to help to sum up possible problems.

[neocturne]

Might work now... please test with as many old firmware versions as possible, on different hardware.

[tcatm]

Seems to fail when upgrading for nightly experimental upgrades:

• fastd is not running, uci fastd.mesh_vpn.enabled is missing
• mesh-vpn is missing in /etc/config/network

[neocturne]

I don't really see how mesh-vpn might even get missing in /etc/config/network as it is created in an invariant script...

[neocturne]

Most problems should be fixed now. Upgrades from 0.3.2.1 to Gluon seem to work fine, I haven't tested upgrades from older versions so far.

[tcatm]

• 0.3.1
• 0.3.2
• 0.3.2.2
• WDR3600/4300

[tcatm]

Updating a WDR4300 from 0.3.2.1 to Gluon was succesful. Both WLAN interfaces were configured correctly.

[neocturne]

All tested.