GL-MT3000 - problems with stability after upgrade to v4.5.16?

[raski]

Hi,
After upgrade to v4.5.16 I have a problem with videoconferences. During videoconference there are 3-4 sec pauses, where I do not send or receive any data. It’s very irritating. Didn’t happen before.

On Beryl:

64 bytes from 74.125.250.68: icmp_seq=1414 ttl=107 time=19.073 ms
64 bytes from 74.125.250.68: icmp_seq=1415 ttl=107 time=24.826 ms
64 bytes from 74.125.250.68: icmp_seq=1416 ttl=107 time=24.886 ms
64 bytes from 74.125.250.68: icmp_seq=1417 ttl=107 time=25.427 ms
Request timeout for icmp_seq 1418
Request timeout for icmp_seq 1419
Request timeout for icmp_seq 1420
Request timeout for icmp_seq 1421
Request timeout for icmp_seq 1422
64 bytes from 74.125.250.68: icmp_seq=1423 ttl=107 time=19.227 ms
64 bytes from 74.125.250.68: icmp_seq=1424 ttl=107 time=25.235 ms
64 bytes from 74.125.250.68: icmp_seq=2177 ttl=107 time=24.247 ms
64 bytes from 74.125.250.68: icmp_seq=2178 ttl=107 time=23.894 ms
64 bytes from 74.125.250.68: icmp_seq=2179 ttl=107 time=17.871 ms
64 bytes from 74.125.250.68: icmp_seq=2180 ttl=107 time=24.193 ms
92 bytes from 192.168.8.1: Destination Net Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 afe6   0 0000  40  01 bca0 192.168.8.184  74.125.250.68

Request timeout for icmp_seq 2181
64 bytes from 74.125.250.68: icmp_seq=2182 ttl=107 time=17.906 ms
64 bytes from 74.125.250.68: icmp_seq=2183 ttl=107 time=18.289 ms
64 bytes from 74.125.250.68: icmp_seq=2184 ttl=107 time=18.541 ms


--- lens.meet.l.google.com ping statistics ---
2199 packets transmitted, 2187 packets received, 0.5% packet loss
round-trip min/avg/max/stddev = 16.976/22.056/244.222/14.216 ms

On different router

64 bytes from 74.125.250.96: icmp_seq=2436 ttl=109 time=62.419 ms
64 bytes from 74.125.250.96: icmp_seq=2437 ttl=109 time=61.924 ms
64 bytes from 74.125.250.96: icmp_seq=2438 ttl=109 time=69.598 ms
64 bytes from 74.125.250.96: icmp_seq=2439 ttl=109 time=82.038 ms
^C
--- lens.meet.l.google.com ping statistics ---
2440 packets transmitted, 2440 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 17.373/74.695/461.413/30.106 ms

Both are connected to same modem using ETH cable, testing on the same device.
All connected devices (phone, pc) have the same problem.

What can I do?

It happens every ~20 minutes or so

Wed Apr 24 14:58:45 2024 kern.info kernel: [71933.479446] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Wed Apr 24 14:58:45 2024 daemon.notice netifd: Network device 'eth0' link is down
Wed Apr 24 14:58:45 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Wed Apr 24 14:58:45 2024 daemon.notice netifd: wan (15645): udhcpc: received SIGTERM
Wed Apr 24 14:58:45 2024 daemon.notice netifd: wan (15645): udhcpc: unicasting a release of 85.252.x.x to 195.204.x.x
Wed Apr 24 14:58:45 2024 daemon.notice netifd: wan (15645): udhcpc: sending release
Wed Apr 24 14:58:45 2024 daemon.notice netifd: wan (15645): udhcpc: entering released state
Wed Apr 24 14:58:45 2024 daemon.notice netifd: wan (15645): Command failed: Permission denied
Wed Apr 24 14:58:45 2024 daemon.notice netifd: Interface 'wan' is now down
Wed Apr 24 14:58:45 2024 daemon.info avahi-daemon[5125]: Withdrawing address record for 85.252.x.x on eth0.
Wed Apr 24 14:58:45 2024 daemon.info avahi-daemon[5125]: Leaving mDNS multicast group on interface eth0.IPv4 with address 85.252.x.x.
Wed Apr 24 14:58:45 2024 daemon.info avahi-daemon[5125]: Interface eth0.IPv4 no longer relevant for mDNS.
Wed Apr 24 14:58:45 2024 daemon.info avahi-daemon[5125]: Interface eth0.IPv6 no longer relevant for mDNS.
Wed Apr 24 14:58:45 2024 daemon.info avahi-daemon[5125]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:eeee:eeee.
Wed Apr 24 14:58:45 2024 daemon.info avahi-daemon[5125]: Withdrawing address record for fe80::9683:c4ff:fe3a:8ab5 on eth0.
Wed Apr 24 14:58:45 2024 daemon.notice netifd: Interface 'wan' is disabled
Wed Apr 24 14:58:45 2024 kern.info kernel: [71933.544917] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Wed Apr 24 14:58:45 2024 daemon.notice netifd: Interface 'wan' is enabled
Wed Apr 24 14:58:45 2024 daemon.warn dnsmasq[25613]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Apr 24 14:58:45 2024 kern.info kernel: [71933.564395] hook is going to be disabled !
Wed Apr 24 14:58:45 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Wed Apr 24 14:58:45 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Wed Apr 24 14:58:45 2024 kern.debug kernel: [71933.930397] kmwan: Delete node:wan
Wed Apr 24 14:58:49 2024 kern.info kernel: [71937.638398] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Wed Apr 24 14:58:49 2024 kern.info kernel: [71937.646957] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Wed Apr 24 14:58:49 2024 daemon.notice netifd: Network device 'eth0' link is up
Wed Apr 24 14:58:49 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Apr 24 14:58:49 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Apr 24 14:58:49 2024 daemon.notice netifd: wan (18078): udhcpc: started, v1.33.2
Wed Apr 24 14:58:49 2024 daemon.notice netifd: wan (18078): udhcpc: sending discover
Wed Apr 24 14:58:50 2024 daemon.notice netifd: wan (18078): udhcpc: sending select for 85.252.x.x
Wed Apr 24 14:58:50 2024 daemon.notice netifd: wan (18078): udhcpc: lease of 85.252.x.x obtained, lease time 3600
Wed Apr 24 14:58:50 2024 daemon.info avahi-daemon[5125]: Joining mDNS multicast group on interface eth0.IPv4 with address 85.252.x.x.
Wed Apr 24 14:58:50 2024 daemon.info avahi-daemon[5125]: New relevant interface eth0.IPv4 for mDNS.
Wed Apr 24 14:58:50 2024 daemon.info avahi-daemon[5125]: Registering new address record for 85.252.x.x on eth0.IPv4.
Wed Apr 24 14:58:50 2024 daemon.notice netifd: Interface 'wan' is now up
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain test
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain onion
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain localhost
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain local
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain invalid
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain bind
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using only locally-known addresses for domain lan
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using nameserver 62.63.0.10#53
Wed Apr 24 14:58:50 2024 daemon.info dnsmasq[25613]: using nameserver 62.63.63.10#53
Wed Apr 24 14:58:50 2024 kern.info kernel: [71938.463056] hook is going to be enabled !
Wed Apr 24 14:58:50 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Wed Apr 24 14:58:50 2024 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wan", "netdev": "eth0", "track_mode": "force", "addr_type": 4, "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Wed Apr 24 14:58:50 2024 kern.debug kernel: [71938.758675] [add_dev_config 288]add node success. iface:wan, dev:eth0, ifindex:2
Wed Apr 24 14:58:50 2024 daemon.info avahi-daemon[5125]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe3a:8ab5.
Wed Apr 24 14:58:50 2024 daemon.info avahi-daemon[5125]: New relevant interface eth0.IPv6 for mDNS.
Wed Apr 24 14:58:50 2024 daemon.info avahi-daemon[5125]: Registering new address record for fe80::9683:c4ff:fe3a:8ab5 on eth0.*.
Wed Apr 24 15:01:58 2024 daemon.info dnsmasq-dhcp[25613]: DHCPREQUEST(br-lan) 192.168.8.172 58:24:29:df:15:57
Wed Apr 24 15:01:58 2024 daemon.info dnsmasq-dhcp[25613]: DHCPACK(br-lan) 192.168.8.172 58:24:29:df:15:57 Pixel-6
Wed Apr 24 15:03:16 2024 kern.info kernel: [72204.835111] mtk_soc_eth 15100000.ethernet eth0: Link is Down

[steep01]

Just a thought. Check if the gl.inet router may be trying to ping an IP address from the WAN and not getting a reply back, so then it thinks wan is down and reloads interfaces.

[raski]

Multi-WAN checking on eth is disabled. Moreover as you can see in logs whole eth interface is going down.

[raski]

Looks like similar problem with:

GL-MT3000 WAN interface eth0 going up and down

I have a Netgear Nighthawk M6 (mr6150) connected to the Beryl AX / MT3000 WAN port. I was noticing the light blinking from time to time. I went into the Beryl and discovered the interface was going up and down about every 3 mins. Is this a negotiation issue? I have checked the cable of course. Any ideas? Log output - Sun May 28 17:01:36 2023 kern.info kernel: [ 1155.346129] mtk_soc_eth 15100000.ethernet eth0: Link is Down Sun May 28 17:01:36 2023 daemon.notice netifd: Network device ‘et…

Beryl AX eth0 negotiation issues - consistent up/down. How to specify interface/link speed?

The beryl does not have cellular radio in it.

IMO looks like Beryl AX has some generic problem with physically broken ports, IMO support should be aware if they replace units but they play dumb. Waste of time.

[glinetlvr]

I’m close to binning this thing. I’ve been having these same issues. My mango and Slate work fine (although slower)

[alzhao]

We will maintain a firmware based on lastest openwrt and using open source wifi driver and hopefully works better.

Slate does work better in repeater.