Flint 2 (GL-MT6000 ) - bug reports - collective thread

I agree this device should work with the stock firmware just fine, at least within the confines of the nice GL-inet UI. It’s annoying that this seems like an unfinished alpha product. I’d recommend for anybody frustrated with how things stand now to go ahead and try vanilla OpenWRT snapshot. You don’t risk anything if you do a sysupgrade – you can go back anytime to the stock firmware. From my experience vanilla OpenWRT is now stable and works reliably*, as a router or a dumb access point.

*I only have 80 MHz capable devices though, so can’t comment on 160 MHz channel width issues.

1 Like

Yep. I’ve recommended it before too.

When using OpenWrt snapshots I think the only issues are with the 2.4GHz range and speed. So if that can be fixed via firmware updates then it’ll be perfect.

I can confirm that 160 MHz works great with OpenWrt snapshots. No issues at all.

1_5ghz

2_5ghz

1 Like

Could the Devs post a detailed changelog between all releases (similar to github) so that everyone can keep track of what is changing? I want to test a new beta, but these posts put me off… If I recall, they did say there was no difference between this new Beta and the one released pre (Alpha)…

Can more information be provided in the posts for the Dev’s to check these new issues?
Would people be able to advise what OpenWrt snapshot they are using so the Devs can review and test?

@blackbox - what app produced those WiFi stats in your last post? Thanks.

1 Like

The first pic is from inSSIDer and the second one is just the network properties area of a Windows 10 PC.

Don’t keep inSSIDer open while trying to browse the web though, since it’ll probably impact your speeds. It’s just good for channel analysis.

1 Like

I had to go back to 4.5.4 too :unamused:

1 Like

Can you tell me if 23.05-snapshot is also good?

I haven’t used 23.05-snapshot, so I can’t confirm if it’s any good. I think it should be relatively stable though, at least with it’s default settings? But I know that none of the recent WiFi or WED fixes have been backported to 23.05 yet.

A day of testing 4.5.6 so far. I’ve not done any WG download/upload tests per say but it has been up all day. I turned on 160mhz and no crash. Adguard is working fine and I also enabled IPv6 passthrough. Pretty stable so far. I have not been able to crash Wi-Fi via speed test like I used to do on 2.4. Though I am using different ssid names as it seems to be more stable that way.

Feature Request : Could you look into adding support for unbound or something similar in future releases ?

3 Likes

4.5.6 DDNS is broken, it doesn’t work. I already changed dns and still the same error occurs.

follow print below.

and I’m also experiencing excessive logs from Android devices…

This version is not good and far from being a stable version like you released…

I tested with unbound and cloudflare, I was having problems with pages that weren’t opening… I thought it was a problem with Cloudflare’s DNS along with DuckDNS’s DDNS, I went back to 4.5.6 “Stable” and the DDNS with my DNS internet provider doesn’t work either…

Then again they launch a temporary version that was working, then they launch a beta version and a stable version that doesn’t work, so it’s not the same as the alpha version that they provided us for testing…

1 Like

Is impossible to manage so many different releases in parallel.
They should organize everything on the official channel (snapshot → beta → RC → stable) and stop sharing on the forum.

The snapshot should be changed to “alpha - install only if explicited requested by support”

1 Like

Nah.
Snapshot is called snapshot because it’s exactly what it is: An automatic generated snapshot of the current code base. Nightly would be the same.

Which firmware flavor for what?

Firmware flavor Usage
Stable Latest version that has been released for operation and has been sufficiently tested.
RC “Release Candidate” - A beta firmware that will soon be labeled as “stable”. As a rule, no major problems are to be expected.
Beta Newer version that has not yet been fully tested. Use at your own risk!
Snapshot Also called “nightly” or “testing”: Is generated every night from the current source code and therefore contains the latest changes (but also a lot of bugs). Use at your own risk and generally not recommended!
Clean Firmware without GL.iNet addons - corresponds more to an original OpenWrt firmware
Tor This firmware has Tor installed by default, this feature is in beta. Use at your own risk!

See How to get support quickly

I know what snapshot means.

Select the “snapshot” and check if there is something there:
https://dl.gl-inet.com/?model=mt6000&type=snapshot

By the way, they should stop sharing here and use only the official channels (on the link above). Otherwise will be impossible to manage.

1 Like

unfortunately this doesn’t change the fact that the alpha version that they sent us for an alpha test was better than the beta and stable… it was just a matter of releasing the version that they sent us… without any type of modification to it. more…

ModelGL.iNet GL-MT6000 4.5.6
Architecture ARMv8 Processor rev 4
OpenWrt Version OpenWrt 23.05-SNAPSHOT r23001+721-38c150612c
Kernel Version 5.15.139

ue Jan 23 19:19:00 2024 cron.err crond[4212]: USER root pid 8876 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:19:00 2024 cron.err crond[4212]: USER root pid 8877 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Tue Jan 23 19:20:00 2024 cron.err crond[4212]: USER root pid 9102 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:20:00 2024 cron.err crond[4212]: USER root pid 9103 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Tue Jan 23 19:20:00 2024 cron.err crond[4212]: USER root pid 9104 cmd . /lib/functions/modem.sh;modem_net_monitor
Tue Jan 23 19:21:00 2024 cron.err crond[4212]: USER root pid 9331 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:21:00 2024 cron.err crond[4212]: USER root pid 9332 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Tue Jan 23 19:22:00 2024 cron.err crond[4212]: USER root pid 9557 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:22:00 2024 cron.err crond[4212]: USER root pid 9558 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Tue Jan 23 19:22:00 2024 cron.err crond[4212]: USER root pid 9559 cmd . /lib/functions/modem.sh;modem_net_monitor
Tue Jan 23 19:23:00 2024 cron.err crond[4212]: USER root pid 9784 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:23:00 2024 cron.err crond[4212]: USER root pid 9785 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Tue Jan 23 19:24:00 2024 cron.err crond[4212]: USER root pid 10078 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:24:00 2024 cron.err crond[4212]: USER root pid 10079 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Tue Jan 23 19:24:00 2024 cron.err crond[4212]: USER root pid 10080 cmd . /lib/functions/modem.sh;modem_net_monitor
Tue Jan 23 19:25:00 2024 cron.err crond[4212]: USER root pid 10277 cmd . /lib/functions/modem.sh;check_ip
Tue Jan 23 19:25:00 2024 cron.err crond[4212]: USER root pid 10278 cmd sleep 30;. /lib/functions/modem.sh;check_ip

2024/01/23 19:15:01 [alert] 4522#0: lua_code_cache is off; this will hurt performance in /etc/nginx/conf.d/gl.conf:6
cat: can't open '/var/log/nginx/access.log': No such file or directory
2024/01/23 19:15:01 [alert] 4522#0: lua_code_cache is off; this will hurt performance in /etc/nginx/conf.d/gl.conf:6
cat: can't open '/var/log/nginx/access.log': No such file or directory
cat: can't open '/var/log/nginx/access.log': No such file or directory
2024/01/23 19:34:19 [error] 4629#0: *424 "/www/ubus/gl_home.html" is not found (2: No such file or directory), client: 192.168.8.153, server: , request: "POST /ubus/?1706031222655 HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci"
2024/01/23 19:34:20 [error] 4629#0: *424 "/www/ubus/gl_home.html" is not found (2: No such file or directory), client: 192.168.8.153, server: , request: "POST /ubus/?1706031224005 HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4629#0: *450 open() "/www/luci-static/resources/protocol/3g.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/3g.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4629#0: *424 open() "/www/luci-static/resources/protocol/callip.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/callip.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4629#0: *448 open() "/www/luci-static/resources/protocol/directip.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/directip.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4629#0: *450 open() "/www/luci-static/resources/protocol/ovpnserver.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/ovpnserver.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4629#0: *424 open() "/www/luci-static/resources/protocol/qmi.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/qmi.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4629#0: *448 open() "/www/luci-static/resources/protocol/wwan.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/wwan.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:20 [error] 4630#0: *454 open() "/www/luci-static/resources/protocol/ncm.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/ncm.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:21 [error] 4630#0: *455 open() "/www/luci-static/resources/protocol/ovpnclient.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/ovpnclient.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:21 [error] 4630#0: *456 open() "/www/luci-static/resources/protocol/qcm.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/qcm.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:21 [error] 4628#0: *458 open() "/www/luci-static/resources/protocol/wgclient.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/wgclient.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:21 [error] 4628#0: *457 open() "/www/luci-static/resources/protocol/wgserver.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/wgserver.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:21 [error] 4628#0: *459 open() "/www/luci-static/resources/protocol/wireguard.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/wireguard.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
2024/01/23 19:34:21 [error] 4628#0: *460 open() "/www/luci-static/resources/protocol/relay.js" failed (2: No such file or directory), client: 192.168.8.153, server: , request: "GET /luci-static/resources/protocol/relay.js?v=git-23.357.58018-024e7ab HTTP/1.1", host: "192.168.8.1", referrer: "https://192.168.8.1/cgi-bin/luci/"
cat: can't open '/var/log/nginx/access.log': No such file or directory
cat: can't open '/var/log/nginx/access.log': No such file or directory
cat: can't open '/var/log/nginx/access.log': No such file or directory
cat: can't open '/var/log/nginx/access.log': No such file or directory

@oly Please don’t spam random log message without any context here.
The log message could be the result of you trying this GL-MT6000 Use USB for log

I tried to install that USB but I factory reset the router!
why am i still getting these logs?

These are alpha/beta versions still… and they are fine.

I actually would like a changelist between versions, so we know what we are testing.

Edit: never mind I see what you’re saying I didn’t realize there was a website with different releases… I also see the changelist there.

Factory reset will not always revert everything. If you really want to wipe all the things, you should reinstall the firmware without keeping the settings.