v4.9 is release now I see for local or online upgrade.
Filename:
mt6000-4.9.0_release1-1015-0605-1780626850.bin
I will try this myself later once I finish work.
Perhaps we can gather experiences here and save each other some pain?
1 Like
Release notes here:
I probably won’t need much of what this upgrade brings, but I’ll sit on this for awhile and let people who know (or maybe think they know) test this out. At some time my OCD will torment me enough to say “to heck with it” and throw caution to the wind…
1 Like
You’ll at least need the SQM.
My experience so far:
I upgraded from 4.8.3. I already had the wifi country code set to GB via LuCI (as that is my location). Post upgrade I do not have any notable degradation of wifi.
My Tailscale binding remained intact. My Firewall rules defined in LuCI remain all good and pretty much all other config I have checked all seems to have retained as expected (parental controls excluded as per release notes).
Network/wifi options are enhanced with it now possible to add more SSIDs without resorting to LuCI.
On 4.8.3 I had SQM installed and enabled (managed via LuCI). Now SQM is in the main settings under Flow Control. For me it was enabled but had no values set (which is not a possible combination via the GUI). Here there is a little bit of a draw back as unlike before, you have to enable for either both upload and download (which is generally not necessary, or not enabled at all. Also the values are in Mbps not kbps so it’s not as granular as I was used to. For now I have set my download value set to 10000 opposed to my actual download to prevent it throttling that when I don’t want it to.
I will enable a IoT SSID when I can be bothered to move my IoT devices over.
For me the upgrade from v4.8.4 → v4.9.0 instantly broke my main wifi SSID. None of my devices would connect to that SSID anymore. I already made an seperate IoT network, devices connecting to the IoT and Guest SSID’s had no issues at all and had internet access as well.
It seemed to be an authentication issue since devices wouldn’t even connect to the SSID.
There didn’t seem to be any (IP) conflicts either and i just couldn’t get it to work, even not after disabling other radio’s (SSID’s). Logging was inconclusive as it didn’t contain any logging containing the troubled SSID.
For now i reverted back to v4.8.4 and got my network up and running again. But i also had to restore my previous config via luCi, because the upgrade to v4.9.0 broke that as well.
I emailed support to see if they have more reports and maybe know whats causing this.