1

Let's continue the discussion about the known bugs in OP24 4.7.5 for the MT3000 and MT6000 here. Or we rename the current post to 4.7.5.

2 Likes
2

I'm running the 4.7.5-op24 from 16/4.
What changed on the 18/4 version?
(When I tried 18/4 yesterday, I could not get packages from Luci)

1 Like
3

We need luci-app-upnp asap :slight_smile: + the rest of the Software that is missing

1 Like
4

After upgrading my Flint2 router to OP24 version 4.7.5, I am no longer able to connect to my router using the Astrowarp IP address. I am currently using the Astrowarp application, as I only have a GL.iNet router available.

It says "ERR_CONNECTION_TIMED_OUT" from the browser.

5

I noticed that 4.7.5-op24 has been released now.

1 Like
6

I keep refreshing the download page from time to time today to see if any newer OP24 available to download and finally get it. ... LOL

7

Do not update.
My internet just stopped to work.
I'm on mobile data now while I try to understand what is happening :pensive:

3 Likes
8

I just upgraded it and it works fine for me.
Let me keep watching it for a while. (the memory usage is kind of high though)

image
image671×401 22.4 KB

9

I can ping when targeting an IP but not when targeting a domain.

I tried to disable the Adguard Home, but the problem persist.

If I connect to the router (ssh), I can ping the domains. But the clients cannot ping any domain.

10

Your situation is kind of deja vu for me, I had been there before.
Do you enable IPv6 ? if not try to enable it to see what will happen.

11

Enabling the IPv6 fixed the problem. Thanks!
Disabling it, stop all clients to connect to internet.

How can I have it working as before (IPv4 only)? @bruce

1 Like
12

Problems on 4.7.5-op24
Previous version was 4.7.0-op24 installed not keeping the settings.
On the update to 4.7.5-op24 I kept the settings.

  1. Internet stoped to work for all clients.
    Disabling Adguard Home didn't change anything.
    image
    image1057×459 17.6 KB

Connecting via ssh to the router, it can ping the domain.
Clients cannot ping the domain but can ping any IP

Router:

root@GL-MT6000:~# ping www.google.com
PING www.google.com (216.58.204.68): 56 data bytes
64 bytes from 216.58.204.68: seq=0 ttl=116 time=8.230 ms
64 bytes from 216.58.204.68: seq=1 ttl=116 time=8.226 ms
64 bytes from 216.58.204.68: seq=2 ttl=116 time=8.058 ms

Clients:

C:\Users\Renato>ping www.google.com
Ping request could not find host www.google.com. Please check the name and try again.

C:\Users\Renato>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116

As an workaround, I enabled the IPv6 as suggested by cafebug

  1. The flashdrive is not recognized doesn't matter how many times I reboot the router.
    image
    image1268×1292 103 KB

    image
    image1297×678 55.3 KB
root@GL-MT6000:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.69 xhci-hcd xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux 6.6.69 xhci-hcd xHCI Host Controller

root@GL-MT6000:~# lsblk
-ash: lsblk: not found

root@GL-MT6000:~# fdisk -l
-ash: fdisk: not found

root@GL-MT6000:~# mount
/dev/root on /rom type squashfs (ro,relatime,errors=continue)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelega                                                            te)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/loop0 on /overlay type f2fs (rw,lazytime,noatime,background_gc=on,nogc_merg                                                            e,discard,discard_unit=block,user_xattr,inline_xattr,acl,inline_data,inline_dent                                                            ry,flush_merge,barrier,extent_cache,mode=adaptive,active_logs=6,alloc_mode=reuse                                                            ,checkpoint_merge,fsync_mode=posix,memory=normal,errors=continue)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/up                                                            per,workdir=/overlay/work,xino=off)
tmpfs on /dev type tmpfs (rw,nosuid,noexec,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,noatime)
bpffs on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,noatime)

To see it again I needed to re-insert it to the USB Port.

root@GL-MT6000:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.69 xhci-hcd xHCI Host Controller
Bus 001 Device 003: ID 0781:55b1 SanDisk SanDisk 3.2 Gen1
Bus 002 Device 001: ID 1d6b:0003 Linux 6.6.69 xhci-hcd xHCI Host Controller

root@GL-MT6000:~# mount
/dev/root on /rom type squashfs (ro,relatime,errors=continue)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/loop0 on /overlay type f2fs (rw,lazytime,noatime,background_gc=on,nogc_merge,discard,discard_unit=block,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,barrier,extent_cache,mode=adaptive,active_logs=6,alloc_mode=reuse,checkpoint_merge,fsync_mode=posix,memory=normal,errors=continue)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work,xino=off)
tmpfs on /dev type tmpfs (rw,nosuid,noexec,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,noatime)
bpffs on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,noatime)
/dev/sda1 on /tmp/mountd/disk1_part1 type ext2 (rw,relatime)
  1. I saw this on LuCi:

image
image1166×176 23.4 KB

  1. Very disapointed to see that GL-iNet is still using an OpenWRT RELEASE CANDIDATE version.
    While OpenWRT is 24.10.1 (Stable), GL-iNet is still on 24.10.0-rc5

image
image882×286 13.9 KB

13

Works perfect here. Upgraded.
Flint2

1 Like
14

This is because gl still uses iptables which is associated with firewall 3 when OpenWrt is moved to firewall4 on nfttables.

Basicly the warning tells these deprecated firewall rules bypass nfttables because nfttables/fw4 is not aware.

iptables is still prefered for ipsets on domains for the vpn policies, there was a time nftables was not able to wild card a domain via dnsmasq for ipsets, however that is now possible but to how I don't know banip and luci-app-pbr can, nfttables is imo a whole different language to me :sweat_smile:

4 Likes
15

This will become a maintenance nightmare.
Eventually, they'll have to start from scratch to avoid layering patches that create more bugs than they fix

6 Likes
16

Hello :wave:t2:
Is it advisable to install this version? (4.7.5-op24) with what the latest discussion here I read , I’m not sure if It is wise to install it.

My goal is too use banip, AdGuard , crowdsec.
But si don’t want to enable ipv6 in my lan.

I use the stable 4.7.4 op21 .
I need the best throughput 2500M from the internet and the lan. And of course the best wifi it can provide.

17

For me, this is the worst version I've ever seen.
I was quite happy with 4.7.0-op24, then I installed this one and now I'm taking a medicine to headache.

2 Likes
18

I've upgraded both of my MT-6000 to OP24 4.7.5, and they are running smooth and fine, without any issues, after the upgrade for several hours already. :innocent:

19

Everything is working fine here. Upgraded from 4.7.

20

I'm starting to think their code is just a bunch of workarounds and patches that don't always work when moving from one version to another, which is causing these new issues.

I updated to 4.7.0-op24 without keeping settings and it was working fine... Then I updated to 4.7.5-op24 (keeping settings, because it's the same 4.7.x) and now I have many weird issues as I wrote above.

I guess they could have more sucess if they focus on the hardware and help this guy here on the software.

It seems they are creating a Frankenstein that is impossible to be stable due to the weakness of how they apply the changes.

4 Likes