What if people places a external fan wrong and heat gets inside, or router is set to a place there is not much airflow intake like a cabinet.
Then it will be much hotter, I can see this happen.
I mean with my self build pcs I have learned quite alot of things, but also learned how it can break, some fans use static pressure for intake and some as output what comes in is more important than out, so airflow is crucial.
But do this without fresh air near the exhaust of a another hot machine and you make it worse.
These things are not always easy to see at first, but having this in the ui surely is handy even when the device is passive cooling , you need to debug it, even if there is faulty behaviour.
A heatsink is not a magic solution it can still conduct heat from outside sources.
Thats why I think they should keep this feature on heatsink only routers without fans too.
Thank you for the detailed report and for sharing the configuration. You were right — we confirmed there is an issue on our side.
The problem is in our backend API validation. Our length check for the I parameters was too conservative, and there is currently a 1 KB limit, which can incorrectly reject valid values such as your I1 entry.
We will fix this issue as soon as possible. Thanks again for helping us identify it.
Having installed beta 4, from what I’ve been able to test, there is still no connection for the 2.4GHz IoT Wi-Fi
For the installation, I had to perform a clean install because, when I tried to install it whilst retaining the existing configuration, the router crashed.
I then restored the settings I had configured using the file I’d saved via LUCI
I’m testing the 4.9 beta1 firmware on my Beryl AX, mainly the new VPN configuration.
So far it seems I can’t replicate the configuration I had in version 4.8 where I had a VPN rule to actually bypass VPN and allow access to the administration interface of the device providing internet access via tethering (tested with SimPoyo and another GL-iNet router).
With the VPN dashboard in the version 4.9 there is no option to create a group that bypass the VPN when accessing certain IP ranges. And from my tests the only way to get something similar, is to add the excluded IP for each group, and also to disable the “Enhanced Kill Switch”, whereas in the previous version, I could add this exception and still use the equivalent of the “Enhanced Kill Switch”
Flint 2. FW 4.9 Beta.
When i choose Quad9 as DNS over TLS resolver router looses connectivity.
I have to choose another DNS to restore it.
Keep in mind that once in a while it does work but most of the time doesn’t.
Dear GL.iNet staff could you please consider adding Beacon Interval and DTIM settings to the Wi‑Fi UI? These parameters are supported at system level, but they are not exposed in the MTK OpenWrt 21 LuCI interface. Adding them would help advanced users fine‑tune wireless performance. Thanks!
TLDR: IoT network is working great! Everything else I use is stable just as it was in 4.8.4.
Longer:
I setup a IoT Network with client isolation on both 2G and 5G and have all IoT devices (Cameras, Sensors, Garage Door etc…) on that network now.
Added ACL rule to allow LAN to IoT traffic as suggested a little further up.
Checks:
Verified on a couple of devices that both AP/Client isolation and traffic from IoT to LAN is blocked.
Verified that traffic from LAN to IoT is working when ACL rule is active and blocked when not active (Wyzecam traffic looking at cameras from my iPad flowing directly when active and going over the Wyze Cloud when blocked).
I will report back if I run into any issues - otherwise this version is a keeper!
Yes — these parameters are supported at the driver level, but sorry, I think they cannot display them in the web UI.
This is likely for two reasons:
LuCI is maintained by the OpenWrt project; GL.iNet is not responsible for maintaining LuCI.
These are advanced wireless parameters; we worry about that users might misconfigure them and cause some wireless clients to be unable to connect, so the GL GUI does not support them.
I upgraded my Beryl AX to the 4.9 beta, keeping settings. Could someone check this: when I went into Luci to verify my SSH settings, the interface was set to "unspecified" rather than LAN. I always change it to LAN to avoid it being open to WAN, so perhaps it was changed back? I set a non-standard port, which was retained, so it is possible this was my error.
Thank you for the pointer. It does work. In my case during the migration from 4.8 to 4.9 my existing rule was ported, but I wanted to add another address to the exclusion list. However this is not possible from the GUI, because the `novpn` fails to satisfy the validity check of step 1.
However with your pointer, I was able to add the new IP address to the list containing the exclusion list for this rule
Testing 4.9 beta on Flint 2, upgrade OK all working so far, however when I attempted to setup the Windscribe VPN provider I entered my username and password in the supplied fields and when saved got an error. I then noticed there was no field to supply the two factor authenticator code. I logged into my account in a browser and disabled the two factor authenticator requirement. Once this was done I was able to proceed on the Flint 2 and acquire the wireguard configuration files.
Is this something that has been missed in the beta and will a field be added for MFA in the wireguard VPN setup ?
, you need to debug it, even if there is faulty behaviour.
