Felix Baumann

Is this error still present in OpenWrt 23 rc2? Was it already present in OpenWrt 22?

Which Gluon version shall be used as reference for how broken a device is? (major vs minor release) Devices can be broken in different ways depending on the Gluon version....

ok, then it's clear what the stance is. nice to know :) I'm thinking about adding a sidebar to the firmware selector in another pr. Hamburger Button on the top-right...

The data structure @herbetom mentioned could also be used to improve handling of manifest aliases and allow us to remove stuff like this override https://github.com/freifunk-darmstadt/gluon-firmware-selector/blob/master/app.js#L452-L489

### From the gluon meetup Roughly where this code can be added: Once a sysupgrade test was successful, empty the keys folder (right before the actual sysupgrade is run) https://github.com/freifunk-gluon/packages/blob/master/admin/autoupdater/src/autoupdater.c#L385...

This is Qemu combined with mt7915e (looking at the logs)

the first thing was just fixed, I don't know about the second one https://github.com/openwrt/openwrt/commit/c909fdad1870361d5a6f0c0a2437d062e988f559 This is not part of any release, yet. But if you build the 23.05 release branch...

which commit?

did this answer your question or did you run into further issues? @MaxRF77

sounds like long-range dcm could be interesting to you https://forum.huawei.com/enterprise/en/huawei/m/ViewThread.html?tid=733129&lang=en Not sure if that's just supported by mt7915 or also by mt7905.