For real?
Agree 100%. GL is on the wrong track. They need to support open source, which was their think from the beginning. 23.05 or later snapshot.
A few issues with 4.5.8:
- channel scan does not work on either band (previously worked on 2.4GHz band in 4.5.6).
- max transmit power is 20dBm (100mW) when it should be 30dBm (1W).
Speeds are good for me on my Apple devices, I get 400ish for the 2.4GHz band at 40MHz, and 1550ish for the 5GHz band at 160MHz, no deauths or packet loss so far, slightly higher bufferbloat than the 4.5.6 firmware but only on uploads.
collectd / luci-app-statistics combination is working fine on my Flint 2 with stable FW 4.5.8.
How did you set yours up? I used the same SSH commands as I did in 4.5.6 but it’s telling me there is no RRD data and I need to setup collectd, which I have already done in Luci.
Edit: removed the packages and dependencies and deleted the files, reinstalled with the exact same commands and it’s working fine now…must have been my mistake first time around.
I have experienced the same regarding with tx power output. I am glad it is not just my device that is experiencing this, and I don’t have a bad unit (although I am in a different regulatory area (getting 20dbm but should have 23dbm)).
I believe the 20 dBm shown in Luci is a bug. On 4.5.8, and when my MT6000 wireless driver is set to a jurisdiction and band that allows 30 dBm, signal strength on WiFi Explorer is equivalent to devices transmitting at 30 dBm.
Actually the power is still broken, device still broadcasting 30 db in countries where this is not allowed.
Having reloaded 4.5.8 you are correct - Luci does report incorrect values though (lower) but the signal strength disproves that.
Am I the only one who thinks the signal and noise value are not right? And the encryption info does not appear .
It happens both in 2.4 and 5Ghz.
No, you are not alone . I think Luci interface is bugged. I found the below in a thread from December
alzhaoGL.iNet Staff
The hardware cannot transimit that high power actually. Luci sometimes is not so compatible so will not display the real value.
We discussed this at length previously.
However, since the issue hasn’t been resolved, they might be prioritizing showing compliance (by falsely labeling as 20dBm) while still maintaining a stronger signal (broadcasting at 30dBm) to outperform competitors which are following the rules.
Just upgraded to 4.5.8 and the GliNet UI just disappeared (only Luci available). Any solution to bring it back ? Thanks.
What is your solution to this problem?
Clear browser cache.
I guess that’s a good thing right?
Just looks like an wrong information, because “free” command is showing a totally different result.
I abandoned the stock firmware and used an excellent snap with kernel 6.6.27. Let’s say the compiler updates the build almost in real time.
The display of memory usage is buggy. Will fix.