[4.6.3-op24] Known bugs

In regards to the firmware release candidate 4.6.3-op24 (OpenWrt 24) from 15th of August for MT6000 (Flint2), please report if you have any issue:

  • PPPoE
  • Wireless transfer speed - 2.4GHz
  • Wireless transfer speed - 5GHz / DFS
  • WPA3 Authentication
  • DNS over HTTPS / TLS
  • Ethernet transfer speed
  • Adguard Home
  • VPN (OpenVPN) client/server
  • VPN (Wireguard) client/server
  • Network storage
  • Tailscale
  • Abnormal log entries

P.S. it's available also for MT3000 (Beryl AX) and for MT2500 (Brume 2)

1 Like

I hope the developers will include the latest M76 driver updates (mt76: update to Git HEAD (2024-08-25) · openwrt/openwrt@ecfb095 · GitHub). Mediatek has fixed important bugs from the Filogic line as well (0fdbc0e6d84bbc0216da2842a494bdf01f745c6c - openwrt/feeds/mtk-openwrt-feeds - Gitiles)

9 Likes

I don't think bug for adguard home. It is 3rd party.

Hi @bruce, is there any chance to have these updates added before releasing it as stable?

3 Likes

Yup i'd recommend updating them, it fixed the multicast crash for me on my ayaneo :+1:, played twice about 4 hours without the wifi crashing, that was one of the only reasons to not recommend it for certain cases.

4 Likes

Yep, but they are using 0.107.46 (from 20th of March).
On the 4th of April was released the 0.107.47 due to the security issue;
One day after (5th of April) was released another version due to a critical bug;
And 0.107.48 and 0.107.49 were released in 3 days apart

I guess 0.107.52 is very stable (it was released on the 4th of July) and there is no relevant issue by now.

I am on 4.6.3 release 2 on Flint 2.
Unfortunately, I cannot install luci-app-sqm after the latest update. The UI shows an error with dependencies, and via SSH and running opkg update && opkg install luci-app-sqm it shows the following:

root@GL-MT6000:~# opkg update && opkg install luci-app-sqm
Downloading https://fw.gl-inet.com/releases/v24.x/v4.6/aarch64_cortex-a53/filogic/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_target
Downloading https://fw.gl-inet.com/releases/v24.x/v4.6/aarch64_cortex-a53/glinet/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_pub
Downloading https://fw.gl-inet.com/releases/v24.x/v4.6/aarch64_cortex-a53/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/glinet_openwrt
Updating database.
Database update completed.
Multiple packages (libgcc1 and libgcc1) providing same name marked HOLD or PREFER. Using latest.
Installing luci-app-sqm (24.124.22943~208333b) to root...
Downloading https://fw.gl-inet.com/releases/v24.x/v4.6/aarch64_cortex-a53/packages/luci-app-sqm_24.124.22943~208333b_all_2.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-sched-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-sched-cake
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-sched-cake found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-ifb
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-reject
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-ipt
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-log
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-nf-log found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-ipt-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nfnetlink
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-reject6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-conntrack
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-conntrack6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-nat
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nf-log6
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-nf-log6 found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-crypto-hash
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-crypto-crc32c
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-lib-crc32c
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-lib-crc32c found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nft-core
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-nft-core found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-nft-compat
 * pkg_hash_fetch_best_installation_candidate: Packages for kmod-nft-compat found, but incompatible with the architectures configured
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1) for kmod-ipt-ipopt
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-sqm:
 * 	kernel (= 6.6.36~20067883eb53777b4242dfcf8a842848-r1)
 * opkg_install_cmd: Cannot install package luci-app-sqm.
2 Likes

4.6.3-op24 has not been merged, but our codes have been updated.
To merge in the next version firmware.

2 Likes

Please install the OPENWRT 24 labeled firmware. there was a problem with the BETA version of the firmware source and we have removed it.

1 Like

Next version means 4.6.4 or do you have plans to release a 4.6.3-ReleaseCandidate2?

Perhaps in 4.6.4.

4.6.3-op24 is in RC. :wink:

Realese from who? GL inet or adguard home?

Without those merges, the users will find multicast crashes as reported by @xize11

Is much better to delay the 4.6.3-op24 with this bug fixed instead of releasing it soon with a known bug.

3 Likes

Its this commit mt76: update to Git HEAD (2024-08-25) · openwrt/openwrt@ecfb095 · GitHub with the mediatek firmware updated: 0fdbc0e6d84bbc0216da2842a494bdf01f745c6c - openwrt/feeds/mtk-openwrt-feeds - Gitiles

It has alot of fixes :+1:, but the mt76 did had a massive update but i think most is fixed now in the openwrt commit i linked.

5 Likes

From Adguard Home right? So it is not known bug with GL inet! Remove list adguard home in 1st post. :face_with_raised_eyebrow:

If there is a bug, it's another reason to use 0.107.52 instead of 0.107.46 that GL-iNet is insisting to use.

Why keep using a version of AGH with known issues where there is a newer version available wihtout issues?

Because someone modified config.yaml in adguard home then usually problems but not fault by gl inet staff.
Default was not auto update adguard home.

Also your issue is adguard home, not GL inet side and not bug.
However, your issue is syntax error upstream or isp/vpn blocked quic protocols?

Let me write once again:

The 0.107.47 was released to fix a security issue on the 0.107.46 (which is the standard version on GL-iNet firmware.

So, 0.107.46 is not a good option.

One day after was released another version due to a critical bug.

So, 0.107.48 is not a good option.

0.107.48 and 0.107.49 were released in 3 days apart to fix some bugs.

Etc, etc, etc...

The most stable version is 0.107.52 (this is the best option to choose)

If you cannot understand this, then read once again, check the Release Notes and release dates.

And... Let's be more collaborative:

  • Are you testing the Firmware 4.6.3-op24 RC?
  • If so, did you notice any bug?