I can say from my personal experience of doing the same ... that is it.
You'll need to make a new backup for 6.6.63
Gotcha. Thought so. I will do a full reset and then I will redo the config.
@matrix200 @bluewavenet @MiguelOlmos @belodetek .. and to any others running the B3000,
I've uploaded new bins for 6.6.63 (24.10) with the reo-status patch by @georgem83. I have been testing for 8 days now, all 3 units have been running rock solid ... both radios. The occasional flush status warning has been observed once, on 1 of the 3 units so far. The warning can be ignored and considered an annoyance for now.
For those runinning 6.6.63 already, use the sysupgrade file ..settings can be retained ..or not.
For those running 6.6.54, use the ubi file, do not keep settings and select force. Also note that a backup from 6.6.54 will not work with 6.6.63.
Please update to the stable 6.6.63 version and post your findings after 7-14 days.
new bin are posted on the repo here --> https://github.com/TheRootED24/GL.iNET-B3000-MARBLE-fit-images
3 Likes
There only seems to be a .ubi, no .bin.....
use the sysupgrade .tar if you're already on 6.6.63 version ...
Hey, I believe that I am on a version that supports sysupgrade.tar
Does it mean, I can upgrade and keep the settings, or do I still need to do a full reset?
EDIT: I see now, that you meant it depends on the version, not on the ability to use sysupgrade per se.
So ubi it is I guess?
yes, use the ubi, don't keep settings, and select force option. Thereafter you can just use sysupgrade moving forward.
Done and like you mentioned earlier, blinking leds on wifi activity works, but s/n is still not showing.
I guess this bug will be fixed after the device is officially added to openwrt repository, huh?
yes, I'll create a br once the target is official. I think we're getting close to that point now.
I've have noticed different results using different versions of wpad ..ie wpad-wolfssl .. wpad-mbedtls ..etc. They all seem to yield different results, some better than others. My s/n values come and go at this point. Regardless, we'll get to the bottom of it once ipq50xx is official
1 Like
Just installed the sysupgrade retaining my previous config. Working great thus far!
1 Like
It has been awfully quiet for a while.
Has there been any progress towards going official?
I've been really busy and haven't had time to prep the pr. I think ipq50xx has now been officially merged. @georgem83 Can you confirm this ?
Very easy answer to this aspect,
https://git.openwrt.org/?p=openwrt/openwrt.git;a=tree;f=target/linux/qualcommax;hb=HEAD
no.
Ok, so no need to prepare a pr at this point. Thank you, as I mentioned, I am very busy and don't really have the time to look at it tonight. I thought i read it was accepted and referenced the author because I figured he would know best about the status of his pr.
Thanks
I will push the latest changes and add new bins this weekend, after i have a chance to test.
1 Like
not yet, still being reviewed after a number of changes were requested and implemented.
Can those of you testing the latest b3000 ow port please provide some feedback. All my units running the latest 6.6.63 have been running rock solid for weeks now. Both radios working great, no crashes or log pollution. Has anyone had any issues to report ? Feedback may help to get the ipq50xx target supported officially.
Good or bad lets discuss it
I can report on my use case, which is using the router as a WDS client.
Its stable.
2 Likes
Hello,
Could someone share results of iperf3/openspeed-go test for 5GHz + 160MHz wireless network please?
I'm considering to buy the router for a dumb ap, but before I buy it, I need to know if it will work in this role.
The codebase is currently being updated, see the main development thread for more info --> IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro - #533 by georgem83
@georgem83 has done some initial iperf testing and had pretty good results as i recall. I would expect very similar results being that the mx2000 and b3000 are pretty well identical hardware.
1 Like