Dirty Upgrade - GT-AX11000 & RT-AX58U - Successful no apparent issues. Did notice under AIMESH I can finally see PHY rate on my node. Haven't seen the info populated since stock fw.
It's enabled for radio 1. The problem is in Canada theirs only 1 160MHz compatible spectrum, and my AIMesh node can't be the one to use it unless I want to do some UI glitch workaround. Would LOVE to have the other radio on 160MHz also, but alas regulations. That's why the GT-AXE11000 came into existence likely to cover the lack of spectrum @ 160MHz as it has the 6GHz radio.
That's weird! I downloaded GT-AX6000, RT-AX86U, RT-AX68U, and other Beta 1 images earlier today — they all appear to still be available in Onedrive Mirror 1.
Sourceforge had a scheduled maintenance tonight, which ended an hour ago, so some mirrors might not be fully up to date on their end during that period. All files still remain available on the Onedrive mirror however.
86U-Pro here.
Dirty flashed over alpha and everything working perfectly.
Using VPN Director to send things over OVPN and Wireguard and everything reconnected flawlessly.
All my mesh nodes working as expected.
Nightmare - but I'm over it.
Dirty flash over the alpha and so much went wrong. "httpd -i br0" running 100% on one core with multiple other processes including "/jffs/scmerlin.d/tailtaintdns" running the other cores up to 80%. No GUI access at all. Same after reboot and an electrical reset.
The good news is I could hard reset and get it back in working order. Even better news is restoring a backup from the previous alpha got all my scripts back and working fine. Thank you again @Viktor Jaep
If anyone else with more than a few scripts has a similar issue tag me and I'll help out if needed (start a new thread)
Did a dirty update to 3004.388.6 Beta1 from 3004.388.5. Had a minor issue that in the DDNS settings the lets encrypt certificate was shown as unkown or processing. The solution was to switch to auto and then to lets encrypt again, after that everthing was showing properly. Besides that no noticable issues.
Will not find it... too far away.
In the Alpha thread they talked about it, someone there mentioned to disable SSL and DDNS (which I did), submit obviously,
And Enable again.
It was something with new directory/place that the certificates are stored there.
Did that , and it works like a magic.