Assuming you’ve got fast internet access, while using the Redmi AX6000 would you be able to perform a speed test from a device (e.g. an older laptop or Android phone) that’ll use 802.11n over 2.4GHz at 40MHz? And ideally you should be just a few meters away from the router.
I forgot to mention this, but it turns out the reason I didn’t experience crashes might of been because a different commit was merged and backported to 23.05. So the issue has already been fixed in OpenWrt.
I don’t know if the next GL.iNet firmware will fix the issue though, since even their test firmware isn’t fully in sync with OpenWrt.
I believe 4.5.4 had a bug with usb-eth driver (I may be wrong), I was hitting that every so often when stressing the eth ports.
I can hit the same ssid bug on 4.5.5 release 3, just go on a facetime call and move away until the phone switches between bands, it doesn’t happen all the time but can repro.
I guess GL.iNet applied a different fix then, since the one from the OpenWrt repository is only 2 weeks old.
The current GL.iNet test firmware reports it’s version as r23001+722-38c150612c, which would mean that it’s 8 months old and predates the release version of OpenWrt 23.05.0-rc1. However, there’s also the “+722”, which could mean they’ve cherry picked some changes and made some changes of their own Either way, it makes it difficult to know exactly how in sync they are with the official OpenWrt release.
I’m really interested to see if GL-inet can branch off a newer version of OpenWrt to see if it fixes some of these issues.
The only thing i can’t figure out is why yours times out and mine not , i see alot of people using the same ssid for 2.4ghz and 5ghz some people said in this forum that it can result in some of the issues.
Not sure, I just have a ton of devices/PCs connected. I try to use Ethernet as much as I can, but a few devices are still on WiFi. This is a great router @ $150 tbh even being kinda buggy
My Asus AX86U couldn’t do wireguard with port forwarding and I spend 2x for those (2 of them), GlInet saved me for the time being until I find a better solution (probably PfSense)
While I may not be as advanced in using technology as some in this discussion, my recent router purchase (awaiting shipment) is primarily driven by the need to support a 2.5gb WAN, Wireguard, a user-friendly interface (I plan to assess the app as well), competitive 5GHz and 2.4GHz speeds. Given the concrete jungle scenario in Singapore with multiple households, I’m eager to see its performance.
In essence, I’m not overly concerned about peripheral features. Let’s acknowledge that, fundamentally, it’s a router designed to fulfill its intended purpose.
One issue I have experienced, is how slow the Adguard Home on Flint 2 loads block filter lists, in some cases, I actually got the adguard home to be unresponsive I had to reboot the router.
What is connected to your eth0 port? Flow control is clearly enabled. I had also problems with a crashing eth port, and disabling flow control (on my switch) helped.
That is a plain lie. It isunusable. I did abandon 160MHz. I did everything that was suggested. The Flint 2 just does not work.
Again, I am not a beta tester and I believe that expecting from a 200€ router to have a working wifi is not an extravagant request. Or at least getting an ETA about when the problem is going to be solved.
Now you won, I will stop coming here because this is obviously a waste of your time and mine.
Either way, it makes it difficult to know exactly how in sync they are with the official OpenWrt release.
