10054

Cause your compat version is at 2.0 and upstream is starting from 1.0 like it should

10055

Tried the same. I activated the advanced mode and removed libufetch-wolfssl (i think it was called that way) and then the image was generated successfully.

Also removed the 2.0 version from the /etc/config/system before sysupgrade

Edit: don‘t do that. Now my build can‘t connect with https to the package feed, as it misses libustrea-.* and ca-bundle etc … very strange thats all not in the default.

10056

I have not noticed any problems. I just used luci and replaces the wpad-basic with wpad-wolffssl and reboot.

10057

Noob question... how to get luci to work on the snapshot?
I tried to migrate to the official build... set compat version to 1.0, sysupgrade through luci and everything went fine.
After reboot everything was working but I had no luci GUI... found a page saying snapshots builds had no web interface, but we could install it later. Only a full release has a web interface.
Tried installing luci through ssh, everything appeared to work ok, but still no web interface...
Gave up, sysupgraded through shh to the latest Robimarko build.
I will probably wait for the official release :slight_smile:

10058

I faced the same, but after running the following, it worked for me.

opkg remove libwolfsslcpu-crypto5.5.4.e624513f --force-depends
10059

Yes, removing this dependency works. If I try to install it later it gives the same error. So it's not problem of attended sysupgrade, is a problem of the package or the opkg.

EDIT: forcing the installation of the package seems to work and it seems not to break anything.

10060

I will remove the prebuilt images, they should not be used anymore.

The only difference between the snapshot and release builds is LuCI, which you can just install with opkg with:

opkg update
opkg install luci
2 Likes
10061

That's exactly what I did but still no web interface.
I think there was some info on some conflicts after installing luci, possibly dependencies and I did not know how to solve or if it was solvable.
I'll try again tomorrow.

10062

Did you start uhttpd service after installation?

10063

No, but rebooted

10064

Thanks for providing the prebuilt images all this time.

I've equivocated on going all out (you know, single root) because I'm lazy.

Will the old strategy (go to initramfs, on one "root" then upgrade with systemfs) work with vanilla OpenWRT builds for AX3600?

This time, I'm not asking for a friend :wink:

10065

Yes, its pretty much the last release but with further cleanups

1 Like
10066

I use wpad-mesh-wolfssl and 5 GHz on my mesh nodes.
I found out that my AX3600 doesn't like mt76 nodes with AC wifi: lot of packet loss, unstable network.

I changed to AX wifi (still mt76 driver) and all is good!
The send speeds isn't as good as the receive speeds. :person_shrugging:

10067

This very likely isn't ax3600 specific, but also try wpad-mesh-openssl.

10068

On every mesh node or just on AX3600?

10069

I'd start with the ax3600, better would be 'all' (at least ax3600 and one mt76/ac, all other switched off).

10070

I have completed the basic information:

The ToH and the wiki can be completed with more information, but at least we have the basic one. Is probably that I will add more infor in the next days, but if you think I'm missing something please send me a message.

8 Likes
10071

SSH access can also be obtained via create_exploit.js script: OpenWrt support for Xiaomi AX9000 - #179 by bruda
There is no need to downgrade the firmware.

2 Likes
10072

I'm still on a pre-interface-rename and pre-single-partition release. How should I updated to official snapshots? Should I still go through latest Robimarko's builds?

10073

I think robi was about to shut down his repo downloads (at least packages feed and kernel modules)
We could use images from https://downloads.openwrt.org/snapshots/targets/ipq807x/generic/ instead (and they should have working opkg install)