Nope.
(Source)
Not only valid, but mandatory
21.02 version ended the development support 2 years ago, so if do you have any hardware released after 2022, it probably will have a lot of bugs (it you are luck and it work).
The security support ended 1 year ago. So, everybody is vulnerable using this version.
4 Likes
This to be honest is one reason why my main backbone isp router is still using the OpenWrt snapshot with wireless off 
, but realisticly if you look to most isp routers these days then alot branch off from even more older forks, there was one isp in my country and on a other site a user published his modem firmware and it was from even before chaos calmer.
Still its not good that it is old 
, but it can be much worse like the example of the isp and my country is not the worst in technology innovations for fiber.
1 Like
There is a problem with the VPN. No matter whether Wireguard or OpenVPN.
If the VPN is on, all assigned clients receive VPN and also the DNS address of the provider. That’s good so far.
But at the same time, all other clients that are not assigned a VPN receive the DNS addresses from the VPN provider.
I then have e.g. the problem that some websites cannot be opened (because VPN DNS is blocked) or my WiFi sockets no longer want to respond. Although the devices just mentioned have not been assigned a VPN.
Tested with Nordvpn and Surfshark
1 Like
exactly, xiaomi uses openwrt based on version 18
2 Likes
It’s not because it’s in version 21 that the gl team doesn’t put the fixes on their own… you’re thinking of openwrt as pure and not with gl modifications… that’s why I say that this type of thinking is wrong, I still maintain my opinion of having a STABLE router with an older version rather than a completely shitty router with an updated version…
3 Likes
The new beta version was not released, was there a serious problem or something that prevented them from releasing the new version?
3 Likes
No it’s not VPN, I did a IPlocation and it was the ISP. Also I double checked with wireshark…
ditched all my glinet products: too many outdated packages, too many buggy firmwares, support near to zero…
replaced with mikrotik rb5009 plus grandstream APs. very happy with it 
1 Like
Even if I like MikroTik (and LANCOM) you have to admit that this is a complete different level of administration.
Would I recommend MikroTik? Yep, definitely.
Would I recommend it for someone who is using an GL device with mostly the GL GUI? No, never!
well… of course it is a learning curve for somebody without a min level of networking knowledge but MK is cheap and rock solid. WinBox is quite intuitive though also their courses are quite well structured. Grandstream… i was a bit neah… but once deployed (one of my friend gave me one gwn7664 to trial it), i love it! way better than omada or ubiquiti. It can be used even in enterprise environment. it might be a bit overkill for home use but why not?
ps. after one week of playing with MikroTiK (RouterOS), i don’t think i’ll look back to openwrt ever. I even like it more than OpnSense or PfSense
1 Like
The procedure for opening a ticket? I’m tired of these mistakes and errors…
days like this… that’s enough.
Wed Feb 28 19:43:00 2024 cron.err crond[4466]: file root:
Wed Feb 28 19:43:00 2024 cron.err crond[4586]: child running /bin/ash
Wed Feb 28 19:43:00 2024 cron.err crond[4466]: USER root pid 4586 cmd . /lib/functions/modem.sh;check_ip
Wed Feb 28 19:43:00 2024 cron.err crond[4587]: child running /bin/ash
Wed Feb 28 19:43:00 2024 cron.err crond[4466]: USER root pid 4587 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Wed Feb 28 19:43:10 2024 cron.err crond[4466]: wakeup dt=10
Wed Feb 28 19:43:20 2024 cron.err crond[4466]: wakeup dt=10
Wed Feb 28 19:43:30 2024 cron.err crond[4466]: wakeup dt=10
Wed Feb 28 19:43:40 2024 cron.err crond[4466]: wakeup dt=10
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: wakeup dt=20
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: file root:
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: line . /lib/functions/modem.sh;check_ip
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: job: 0 . /lib/functions/modem.sh;check_ip
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: line sleep 30;. /lib/functions/modem.sh;check_ip
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: job: 0 sleep 30;. /lib/functions/modem.sh;check_ip
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: line . /lib/functions/modem.sh;modem_net_monitor
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: job: 0 . /lib/functions/modem.sh;modem_net_monitor
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: file root:
Wed Feb 28 19:44:00 2024 cron.err crond[4826]: child running /bin/ash
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: USER root pid 4826 cmd . /lib/functions/modem.sh;check_ip
Wed Feb 28 19:44:00 2024 cron.err crond[4827]: child running /bin/ash
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: USER root pid 4827 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Wed Feb 28 19:44:00 2024 cron.err crond[4829]: child running /bin/ash
Wed Feb 28 19:44:00 2024 cron.err crond[4466]: USER root pid 4829 cmd . /lib/functions/modem.sh;modem_net_monitor
Wed Feb 28 19:44:10 2024 cron.err crond[4466]: wakeup dt=10
I try’d to use the “Scheduled Tasks” → 2.4GHz Wi-Fi Status Schedule/5GHz Wi-Fi Status Schedule and set it up with “switch TX power” to medium at midtnight when i hit apply i am losing my internet connection… when i remove it again i get the internet back…?? am i the only one?
“Schedule Reboot” seems to work or i will see this friday ;-).
What’s the point here?
That log looks pretty normal.
Hello,
Following this thread since a while.
got a Sony smartphone, Xperia 1 IV, and i had WiFi connectivity issues, like connected but not surfing for few seconds…
just wondering, is there any latest openwrt firmware with proprietary drivers + a dumb proof guide to install it?
cheers!
Even on 2.4GHz it keeps happening but not as often compared to 5GHz. But yeah it happens on both bands and also on my phone, not only windows (I think I’ll try 4.5.7)
The same issue we were talking about, I’ve seen like 2-3 people with the same issue, so I’m hoping GL Staff can take notes 
1 Like
Factory reset did the trick. After re-configuring, the router is up and running. Thanks much for the suggestion.
gonna try this one later today👍, experience with oem snapshot from 2024-02-27 wasn’t smooth on my dumbap dhcp clients with tagged wan devices failed to work in a bridge + no success getting access it was only deauthing, instead i compiled a newer OpenWrt r25345-c6319de48b and test wifi on my main backbone, this one seem to be alot more stable but i need more testing to confirm.
Gonna test both😁
1 Like