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! |
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.
For real ? reset firmware doesn’t delete everything ? do you have any examples ?
If you broke the system and tried some “advanced” things inside the OS, reinstalling might be the only way to revert to a stable system state.
You sure you don’t work for GL.iNet?
You starting to sound like a talking head…
1 Like
It depends on what you did.
Resetting the settings will install some preformatted image to the root partition. In most cases this is sufficient. But if you worked “under the hood” it might be a problem.
Note that this “soft reset” is performed with file system actions, so in some cases it is not enough.
Basically, I would recommend the following steps:
If you just changed stuff using the GL GUI → Revert using the “Reset” button
If you did something using SSH which was more complicated than you thought before → Reflash
Since reflashing is as fast as resetting, I recommend reflashing because you can be sure that the device is completly “new” then and there are no problems from the last firmware.
1 Like
one of the problems I encountered… gl updated the DDNS packages in this version 4.5.6 and caused their ddns to break… installing luci-app-ddns and configuring the Duckdns ddns that I have came back to Wireguard access works normally… but there is another thing that doesn’t seem to be gl’s fault, Duckdns is having problems with cloudflare, yesterday I was testing 23.05-snapshot and there were websites that wouldn’t open, just disable the cell phone’s wifi that started working again…
So cloudflare has problems there too…
the same guy always… it’s unbelievable that he’s still on the forum… he can help with anything in other topics, being arrogant like that, let’s really flag it…
must be a staff member, or a friend of someone from gl, it is not possible
1 Like