Can I avoid new configuration partially - Config cannot be migrated from swconfig to DSA

[linuxuser]

Model	Netgear EX6150v2
Architecture	ARMv7 Processor rev 5 (v7l)
Target Platform	ipq40xx/generic
Firmware Version	OpenWrt 22.03.0 r19685-512e76967f / LuCI openwrt-22.03 branch git-22.245.77528-487e58a

A few minutes ago I updated an Archer C7 from Openwrt 18 to 23 and it looks like it worked fine, And now I cannot update from 22.03.

Configuration as wireless bridge is a little bit tricky and i fear a new setup could make problems.

That is what I did:

root@EX6150v2:/tmp# sha256sum openwrt-23.05.2-ipq40xx-generic-netgear_ex6150v2-s
quashfs-sysupgrade.bin 
b612bafeff67322eb29565fe02bbe8da40de5b341caf954eebc481b9648a74ca  openwrt-23.05.2-ipq40xx-generic-netgear_ex6150v2-squashfs-sysupgrade.bin

root@EX6150v2:/tmp# free
              total        used        free      shared  buff/cache   available
Mem:         248192       50792      176892        7000       20508      159072
Swap:             0           0           0

root@EX6150v2:/tmp# sysupgrade -v /tmp/openwrt-23.05.2-ipq40xx-generic-netgear_e
x6150v2-squashfs-sysupgrade.bin 
Fri Nov 24 23:07:16 UTC 2023 upgrade: The device is supported, but the config is incompatible to the new image (1.0->1.1). Please upgrade without keeping config (sysupgrade -n).
Fri Nov 24 23:07:16 UTC 2023 upgrade: Config cannot be migrated from swconfig to DSA
Image check failed.

Of course I read "sysupgrade -n"

I saved /etc and so I can see what was configured earlier. But maybe you have a better way to migrate.

[psherman]

You should allow it to reset and start from scratch because this is a very significant change.

Sometimes you ca. “cherry-pick” certain files or sections of files to copy/paste, but generally this is not safe except for very specific details (like dhcp reservations or von configuration files)

[linuxuser]

@psherman

You should allow it to reset and start from scratch

Thanks there are postings in the web, which say you can force the installation somehow. But if you say configure new, I will do it. Wondering why this happens with a 22.03 version. AFAIR this was the 1st openwrt I installed.

[psherman]

Forcing the installation is fine (as long as you’ve got the correct firmware file and the checksum matches so that you know it’s not corrupt).

You use the -F argument. There will be no checks whatsoever, so the above comments apply.

@linuxuser

Wondering why this happens with a 22.03 version. AFAIR this was the 1st openwrt I installed.

The sysupgrade routines have gotten a bit more sophisticated and/or the image actually contains certain metadata to inform the user. I’m not sure what happens under the hood, but 22.03 is just one major version back from 23.05, so the developers may have been able to code some of this into the sysupgrade environment.

If you want to know the specific methods by which this works, some others on the forum who are either devs or closer to the source code may be able to answer.

[linuxuser]

So I start with

sysupgrade -n

as in the output

and then

firstboot -y && reboot

[psherman]

The -n argument causes the device to be defaulted. Therefore, no further reset is required unless you later restored the old config backup.

[linuxuser]

It was easy to setup the EX6150v2 as described here:

Is there a “newer” documention for creating a wireless backhaul?

Still got not work to setup a wireless bridge with the webinterface using openwrt 23.05. It took a few minutes with an editor to work, but naming is confusing. Here is what I did with a D-Link DAP-X1860 A1 Disabled in my linux box wifi and connected to the D-Link DAP-X1860 A1 via ethernet cable. My network is 192.168.178.x. The change of the network must be done before. If not mentioned, everything is kept default. /etc/config/network Added in the section config interface 'lan' ... option…

But as you see in the mentioned thread, it can get tricky, if you make a mistake. There are devices with radio0 for 2.4GHz while other have radio1 as default.