Thanks for the reply! That depends on which storefront did you buy it from. AFAIK, if we bought it from Aliex, we will get Global version. Otherwise, if we bought from Taobao or others, we will get CN version which have it's VPN feature somewhat "firmware" disabled.
I would like to ask several questions:
I bought it from the GL.iNet store page, the non EU one. Mine came with an Australian power supply adapter, and the box said Australian version, but I assumed that was only the power adapter.
I think it had the VPN stuff, but can't verify as I'm on proper OpenWRT now.
I can't see why they would have different hardware. I think you could easily try loading the firmware from the OEM site.
Does thi ssuggest that it is preferrable to have SW and HW offloadinge kept "on" by default for in case of usual functioning....
Did anyone manage to open the case ?
There are 4 screws underneath the rubber feet, but I guess I'm missing at least another one.
While the u-boot with webserver is quiet comfortable, I would feel much better with serial console.
hello all,
I received this router two days ago, can someone tell me the correct procedure to switch to openwrt with the possibility of returning to the original software?
second question, are these packages compatible with this router, or what packages you would complete with?
base-files busybox ca-bundle dropbear e2fsprogs f2fsck firewall4 fstools kmod-crypto-hw-safexcel kmod-gpio-button-hotplug kmod-leds-gpio kmod-mt7915e kmod-mt7986-firmware kmod-nft-offload kmod-usb3 libc libgcc libustream-mbedtls logd luci mkf2fs mt7986-wo-firmware mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd wpad-basic-mbedtls 6in4
adblock
attendedsysupgrade-common
auc
banip
base-files
block-mount
busybox
ca-bundle
cgi-io
collectd
collectd-mod-conntrack
collectd-mod-contextswitch
collectd-mod-cpu
collectd-mod-cpufreq
collectd-mod-df
collectd-mod-disk
collectd-mod-dns
collectd-mod-filecount
collectd-mod-interface
collectd-mod-iptables
collectd-mod-irq
collectd-mod-iwinfo
collectd-mod-load
collectd-mod-memory
collectd-mod-netlink
collectd-mod-network
collectd-mod-openvpn
collectd-mod-ping
collectd-mod-processes
collectd-mod-protocols
collectd-mod-rrdtool
collectd-mod-tcpconns
collectd-mod-thermal
collectd-mod-uptime
collectd-mod-vmem
collectd-mod-wireless
curl
ddns-scripts
ddns-scripts-services
dnsmasq-full
drill
dropbear
firewall4
fstools
fwtool
getrandom
hostapd-common
htop
ip-tiny
iperf3
ipset
iptables-mod-conntrack-extra
iptables-mod-ipopt
irqbalance
iw
iwinfo
jshn
jsonfilter
kernel
kmod-cfg80211
kmod-fs-ext4
kmod-gpio-button-hotplug
kmod-ip6tables
kmod-ipt-conntrack
kmod-ipt-conntrack-extra
kmod-ipt-core
kmod-ipt-ipopt
kmod-ipt-ipset
kmod-ipt-nat
kmod-ipt-offload
kmod-ipt-raw
kmod-lib-crc-ccitt
kmod-mac80211
kmod-mii
kmod-mwl8k
kmod-nf-conntrack
kmod-nf-conntrack6
kmod-nf-flow
kmod-nf-ipt
kmod-nf-ipt6
kmod-nf-nat
kmod-nf-reject
kmod-nf-reject6
kmod-nfnetlink
kmod-nft-offload
kmod-nls-base
kmod-ppp
kmod-pppoe
kmod-pppox
kmod-slhc
kmod-usb-core
kmod-usb-net
kmod-usb-storage
kmod-usb2
kmod-usb3
kmod-wireguard
libblobmsg-json
libc
libcurl
libip4tc
libip6tc
libipset
libiwinfo
libiwinfo-data
libiwinfo-lua
libjson-c
libjson-script
libldns
liblua
liblucihttp
liblucihttp-lua
libmnl
libncurses
libnl-tiny
libopenssl
libpcre
libpthread
libqrencode
librt
libubox
libubus
libubus-lua
libuci
libuci-lua
libuclient
libustream-mbedtls
libuuid
libuv
libwolfssl
libxtables
logd
lua
luci
luci-app-adblock
luci-app-attendedsysupgrade
luci-app-banip
luci-app-ddns
luci-app-firewall
luci-app-nlbwmon
luci-app-openvpn
luci-app-opkg
luci-app-statistics
luci-app-upnp
luci-app-wifischedule
luci-base
luci-compat
luci-lib-base
luci-lib-ip
luci-lib-ipkg
luci-lib-json
luci-lib-jsonc
luci-lib-nixio
luci-mod-admin-full
luci-mod-network
luci-mod-rpc
luci-mod-status
luci-mod-system
luci-proto-ipv6
luci-proto-ppp
luci-proto-wireguard
luci-ssl
luci-theme-bootstrap
luci-theme-material
luci-theme-openwrt-2020
mtd
mtr-json
netifd
nftables-json
odhcp6c
odhcpd-ipv6only
openvpn-mbedtls
openwrt-keyring
opkg
ppp
ppp-mod-pppoe
ppp-mod-pptp
procd
procd-seccomp
procd-ujail
qrencode
rpcd
rpcd-mod-file
rpcd-mod-iwinfo
rpcd-mod-luci
rpcd-mod-rpcsys
rpcd-mod-rrdns
screen
tcpdump
terminfo
ubi-utils
uboot-envtools
ubox
ubus
ubusd
ucert
uci
uclient-fetch
uhttpd
uhttpd-mod-ubus
urandom-seed
urngd
usign
wget-ssl
wifischedule
wireguard-tools
wireless-regdb
zlib
I don't know for all the packages. I'm running
luci
uci-app-attendedsysupgrade
auc
luci-app-statistics
collectd-mod-cpufreq
collectd-mod-thermal
htop
irqbalance
luci-app-https-dns-proxy
luci-app-banip
and they seem to work fine, with the exception of
collectd-mod-cpufreq
For some reason this one is not shown in the statistics.
Fri Dec 15 19:07:40 2023 daemon.err collectd[3174]: cpufreq plugin: Found 0 CPUs
this may improve overall performance
I noticed this as well - No settings I changed for cake, or hardware / software offloading seemed to change my bufferbloat score, at least not consistently.
What ISP do you have?
Download and Upload Speed?
Connection type (Fiber, DSL, DOCSIS cable, 4G LTE or 5G etc.)?
Can you post the contents of your /etc/config/sqm file?
With 1gb FTTH, over wifi im getting A rating (without cake + hwo running) and thats with some iptv streams running in background. All of my data is streams / browsing and gaming, there is no point to use sqm for me.
+1
I havent tested yet, but, based on previous comments and someone correct if im wrong, you can sysupgrade directly from ssh, not sure about webpanel.
Can someone confirm if the restore of factory firmware is also working with sysupgrade ?
Thanks!
I havent tested yet, but, based on previous comments and
someone correct if im wrong, you can sysupgrade directly from
ssh, not sure about webpanel.Can someone confirm if the restore of factory firmware is also
working with sysupgrade ?
I received this router two days ago, can someone tell me the correct procedure to switch to openwrt with the possibility of returning to the original software?
I can confirm that I have personally upgraded my own MT6000 from GLiNet (stock/OEM) firmware using the GLiNet stock WebUI's upgrade function and by loading a vanilla OpenWrt sysupgrade image.
Other people in this thread have confirmed that they have done the same thing. Stock WebUI and sysupgrade image.
Different people on this thread have confirmed that they have used a sysupgrade image from the GLiNet stock uboot WebUI by using the recovery procedure. Simply hold the reset button while removing and reapplying power, navigate to 192.168.8.1 and follow the on screen instructions in the WebUI to upload the sysupgrade image.
I believe the same would work from an ssh shell, but you would have to copy the file to the temp directory or similar and use the standard shell/CLI commands as described on the wiki. I have not done this with this router as there was no need. I have, however, done it with other routers, and have no reason to doubt it would work with this particular router model, in fact every reason to believe it would, I just have not done it with this particular model and do not recall anybody else saying they have used that method either.
I have also not gone back/reverted from vanilla OpenWrt to the stock GLiNet firmware, but in this thread @daniel stated that it is possible to revert through the OpenWrt WebUI. He is probably one of the most knowledgeable people to contribute to this thread, and an OpenWrt dev, and iirc helped write the Filogic driver code, so I think he would know. I defer to others like him on reverting.
I also know that if you only use the sysupgrade image then your stock GLiNet uboot WebUI will remain in place, and you can upload the stock firmware from there using the recovery procedure described above and in videos on the GLiNet web site. (search for unbrick GLiNet)
second question, are these packages compatible with this router, or what packages you would complete with?
I would use the firmware selector and click " Customize installed packages and/or first boot script", then leave all the standard packages unless you know what you are doing (especially since this device has decent storage).
The firmware-selector adds almost the same as a regular snapshot, with the addition of luci, which will get you a Web GUI.
I would add things as needed from there.
I personally use tailscale for external access to my home network with good success (good enough to stream movies from Jellyfin, windows rdp), and adding that to the firmware builder list will add tailscaled as a dependency. On some routers tailscale won't work due to low storage and tailscale takes about 15Mb, but the MT6000 should be fine.
After that, I would research apps on the wiki and forums before installing them, because it's not just about whether something is compatible, but whether it does what you want, whether it works in your setup, and also about how you configure it (like apps or add-ins on any operating system).
Whatever you do, don't just keep upgrading packages, as this can get you into dependency hell, especially with snapshots, and it is also not great for router storage. There are discussions on this on the forums and I recommend this video from onemarcfifty - https://www.youtube.com/watch?v=FFTPA6GkJjg
No need to watch videos with ad monetization for this: https://openwrt.org/meta/infobox/upgrade_packages_warning
Upgrading packages may cause serious problems, including soft-bricking your device!
Blindly upgrading packages (manually or via script) can lead you into all sorts of trouble.
…
Generally speaking, the use ofopkg upgradeis very highly discouraged . It should be avoided in almost all circumstances. In particular, bulk upgrading is very likely to result in major problems, but even upgrading individual packages may cause issues. It is also important to stress that this is distinctly different from thesysupgradepath for upgrading OpenWrt releases (major versions as well as maintenance upgrades).opkg upgradewill not update the OpenWrt version. Onlysysupgradecan do that. The two are not equivalent.
Does attendsysupgrade works in different way in comparison to upgrading from opkg update?.
opkg update: update list of available packages
opkg upgrade: upgrade packages
Attended sysupgrade is optional. sysupgrade without attended is the default upgrade mechanism for updating OpenWrt installations. Yes, sysupgrade is different from running opkg upgrade.
sysupgrade is used for installing a new Openwrt image version. opkg install and opkg upgrade can be used to install or upgrade single packages, if necessary.
No need to watch videos with ad monetization for this: https://openwrt.org/meta/infobox/upgrade_packages_warning
I pointed to the video because onemarcfifty explains the situation very well. Sure there are ads, but there are also ad-blockers. I gain nothing from anyone watching that video except that I get to help someone.
But I also agree with the articles on the OpenWrt web site, which is why I pointed to them.
@di_Niko Thanks for the recommendation, I managed to switch to OpenWrt with the first example @solidus1983, the easier way is to only use sysupgrade
1) Remove Power from the router
2) Press and Hold the reset button
3) Apply power whilst still holding the reset button
4) After 5 seconds head to http://192.168.1.1
5) Flash OpenWRT openwrt-96f0ce2c89c5-mediatek-filogic-glinet_gl-mt6000-squashfs-sysupgrade.bin
Here I want to specify only if you are connected to the LAN port 2,3,4,5, you can use this instruction!
From my tests, everything works well with the packages proposed by me above, I noticed some problems on the Wi-Fi side, disconnections on
SNAPSHOT (r24665-8815a3114f)
Status
System
Hostname OpenWrt
Model GL.iNet GL-MT6000
Architecture ARMv8 Processor rev 4
Target Platform mediatek/filogic
Firmware Version OpenWrt SNAPSHOT r24665-8815a3114f / LuCI Master git-23.292.78363-ee6a4da
Kernel Version 5.15.142
Local Time 2023-12-17 21:04:48
Uptime 0h 41m 52s
Packet Steering -on
Software flow offloading-on
Hardware flow offloading-on
1Gbps connection
In the speed test on ipv6, it does not perform as well as wrt1900acs v2, which gives a score of 870Mps both download and upload, the result with GL-MT6000
try for test https://www.ziggo.nl/speedtest#
the load on the processor is insignificant, but it does not work on IPv6!
I see this device is now supported in 23.05-Snapshot?
I'm currently following main/master. Should I stay on the bleeding edge and wait for 24.XX or move backwards to 23.05? Seems like the last few major releases were done once a year (more or less).. 21.02, 22.03, 23.05, 24.06??
There has been some talk of this being supported by 23.05.3, whenever that comes as, if you look back in this thread, you'll see some mention that commits were recently made, but most of us here don't control that process at all.
