This is a BIG mistake for your company. I get that adapting your closed source SW and MTK drivers is a challenge. But, basing the success of your flagship product, the GL-MT6000, on an old firmware base is just dumb. You are risking the success of your most advanced product on a very, very old firmware base 21.02. Many problems are fixed in the current base 23.05 or later. You should move onto the newer base no matter how challenging as it will save you money and please your customers.
9 Likes
Come on. Get over it. The software base is an important issue.
1 Like
GL-iNET would do much better by working with the OpenWrt community and just building their own UI as an OpenWrt package. Open source OpenWrt snapshot is in a very good shape and stable.
1 Like
Thanks for your effort in resolving that issues team, but according to this page OpenWrt | endoflife.date the 21.02 Version is already EOL without receiving any new security patches.
2 Likes
while I understand where you are comming from, the dillema is that OpenWrt devs might consider this platform stable at OpenWrt release 24.x.
the filogic mediatek 7981/7986 is very experimental and still under goes alot of backporting, the 2.5gb ethernet driver wasn’t official supported in linux kernel yet but got merged recently.
this means it is a really experimental device which requires alot of time and testing by OpenWrt team aswell, this might also give a insight of all the crashing and other issues.
so with that in mind I can understand GL’s reasoning too, do you want a experimental platform not being stable enough, or a platform being stable and then with a few regressions which are easier to fix than backporting drivers?
then I understand why they would go for mediatek sdk route, though I don’t like it too, but there is also not really a replacement.
compared to OpenWrt’s work, backporting is very difficult while with mediatek SDK you can overbridge that issue and hold off until OpenWrt got more stable.
^ I only hope they either make two versions of the gl sdk either the mediatek one and the openwrt one, to avoid further regressions or making them more polymorphic in code base so it can speak through programmable interfaces/or by if else checks in their scripts, it will take them more work out of their hands 
the only issue is its older kernel and there are some luci/wireless limitations and older packages and maybe some regressions due the driver change.
hi,
the first time deletes the packages from the selector and then adds only the packages recommended by me https://firmware-selector.openwrt.org
6in4
adblock
auc
banip
base-files
bcp38
block-mount
bridger
busybox
ca-certificates
ccrypt
cgi-io
collectd
collectd-mod-conntrack
collectd-mod-cpu
collectd-mod-cpufreq
collectd-mod-exec
collectd-mod-interface
collectd-mod-iwinfo
collectd-mod-load
collectd-mod-memory
collectd-mod-network
collectd-mod-ping
collectd-mod-rrdtool
collectd-mod-sqm
collectd-mod-thermal
collectd-mod-uptime
dejavu-fonts-ttf-DejaVuSansMono
diffutils
dnsmasq-full
dropbear
e2fsprogs
eip197-mini-firmware
f2fsck
fontconfig
gdbserver
getrandom
glib2
hostapd-common
hostapd-utils
htop
ip6tables-nft
ipset
iptables-mod-ipopt
iptables-nft
irqbalance
iw
iwinfo
kernel
kmod-asn1-decoder
kmod-cfg80211
kmod-crypto-aead
kmod-crypto-authenc
kmod-crypto-ccm
kmod-crypto-cmac
kmod-crypto-des
kmod-crypto-ecb
kmod-crypto-gcm
kmod-crypto-hw-safexcel
kmod-crypto-kpp
kmod-crypto-lib-chacha20
kmod-crypto-lib-chacha20poly1305
kmod-crypto-lib-curve25519
kmod-dnsresolver
kmod-fs-cifs
kmod-fs-exfat
kmod-fs-ext4
kmod-fs-msdos
kmod-fs-ntfs3
kmod-gpio-button-hotplug
kmod-hwmon-core
kmod-ifb
kmod-leds-gpio
kmod-lib-crc-ccitt
kmod-mac80211
kmod-mt76-connac
kmod-mt7915e
kmod-mt7986-firmware
kmod-phy-aquantia
kmod-ppp
kmod-pppoe
kmod-sched-cake
kmod-scsi-core
kmod-tun
kmod-udptunnel4
kmod-udptunnel6
kmod-usb-core
kmod-usb-storage
kmod-usb-xhci-hcd
kmod-usb-xhci-mtk
kmod-usb2
kmod-usb3
kmod-wireguard
libc
libjson-script
liblucihttp
liblucihttp-ucode
libopenssl
libopenssl-conf
libopenssl-legacy
libpcap
libustream-mbedtls
libxml2
logd
luci
luci-app-adblock
luci-app-attendedsysupgrade
luci-app-banip
luci-app-bcp38
luci-app-commands
luci-app-irqbalance
luci-app-nlbwmon
luci-app-sqm
luci-app-statistics
luci-app-uhttpd
luci-app-wifischedule
luci-proto-unet
luci-proto-wireguard
luci-theme-openwrt-2020
mkf2fs
mt7986-wo-firmware
mtd
mtr-nojson
nano
odhcp6c
odhcpd-ipv6only
openssh-sftp-server
openssl-util
patch
pixman
ppp
ppp-mod-pppoe
procd
procd-seccomp
procd-ujail
qosify
qrencode
tcpdump-mini
tree
uboot-envtools
uci
ucode-mod-rtnl
ucode-mod-uloop
urandom-seed
urngd
wget-ssl
wpad-openssl
@alex_zheng I believe that the main problem involving the router would be the low speed on the 2.4 GHz network, as it is not simply low, but there is a lot of packet loss as well, preventing video calls or playing games.
Are there any suspicions about the problem that could be causing this? Depending on the case, we can ask the MT76 driver developers for help.
1 Like
I’m having the same issue, I already talked about it, I thought it might be a DNS connection lost. It happens a lot of my laptop, (connected via 5GHz WiFi 6, full signal). And most important, when I disconnect from the network and reconnect again, it works instantly. I need to do that or wait a few seconds/minutes until the internet works again. It doesn’t happen on every device simultaneously. (v4.5.6)
I wasn’t even able to load the glinet web GUI today, and once I reconnected it worked instantly. @alex_zheng
2 Likes
What is the obsession with having version 23.05 on the router? Most people here use the router at home and not in a company, having the latest security patches is valid, but I prefer a stable router with simple functions working than an updated version full of bugs, 23.05 is not like that everyone says no… it may be stable but it still has several problems, such as vlan
3 Likes
For some things you rather want a newer OpenWrt.
One of them could be easily as:
- multi psk (better support from upstream OpenWrt source)
- some packages are up to date, or introduced in a later version.
For me it is because i want to be in sync with a few tunneling protocols like vxlan or gre some people can run very advanced networks or even home labs, my own network is also one, i sent more than 6 networks over one 25 meter cable and then split route everything, and on my beryl ax i basicly glue my location to my own house via layer 2 tunnel like vxlan or gre through a vpn.
Its harder to diagnose a problem once you get kinda forced into a eco system which is older but also run gl scripts which may conflict, trust me you dont want that as the full backbone of your network 
, even with DSA, as for now i did not checked if the mediatek sdk uses swconfig, but that can also complicate things.
Currently i run one MT6000 as main backbone on a OpenWrt snapshot with wireless off, and another one as dumbap on gl-inets mediatek oem firmware, this is currently how im able to work around it, but when i wanted to play with vxlan i got issues on my Beryl Ax which also uses mediatek sdk, and i returned back to gre, it might was a mtu problem, but i noticed my interfaces did got a dhcp client ip, but wireless could not connect, the log said something about there was no dhcp address, so i assumed it was broken.
1 Like
Yes that’s the issue I’m having exactly. So far 4.5.7 seems better but still testing
Well, the adapter on my laptop is Intel and supports 160MHz, my router is on 80MHz, I’ve never used 160MHz
I’m now using 2.4GHz on my laptop, but I think I will try 4.5.7, @alex_zheng please take notes 
this is the new beta that is currently published on the site 4.5.7?
4.5.7 leaks IPv6 address 
This is after disabling / enabling ethernet adapter…
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : lan
IPv6 Address. . . . . . . . . . . : fdad:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Temporary IPv6 Address. . . . . . : fdad:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Link-local IPv6 Address . . . . . : fe80::xxxx:xxxx:xxx:xxxx%xx
IPv4 Address. . . . . . . . . . . : 192.168.50.197
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.50.1```I am seriously considering going back to my Asus AX86U…
Wireguard w/ Port forwarding is great, but this router has way too many software issues.
3 Likes
While enabling IPv6 the settings page will tell you that there are issues like VPN f.e.
Are you sure that the IPv6 isn’t the VPN one?
When I enable 160 Mhz, why does it need to force me to use a DFS channel?
Can it not provide 160 Mhz without DFS?
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