MT3000, Firmware 4.6.4 and Starlink

Technical Support for Routers
1

I have my Starlink connected to my MT3000. I used to have an MT1300 but upgraded due to frequent disconnects of the Ethernet connection. Once I was using the MT3000, the issue went away.

However, I was away for 4 months and returned and upgraded the MT3000 to 4.6.4 (was previously on 4.5.16). Everything seemed OK, but I am seeing disconnects now on the Ethernet port again.

I will revert back to 4.5.16 and see if the issue disappears, but wondering if this is a known issue or I am a one-off with the problem and perhaps the issue is not on the MT3000....?

Thanks for any help.

2

Tue Oct 1 16:16:55 2024 kern.info kernel: [719273.867386] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Tue Oct 1 16:16:55 2024 daemon.notice netifd: Network device 'eth0' link is down
Tue Oct 1 16:16:55 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Oct 1 16:16:55 2024 daemon.notice netifd: wan (21234): udhcpc: received SIGTERM
Tue Oct 1 16:16:55 2024 daemon.notice netifd: wan (21234): udhcpc: unicasting a release of 100.105.221.10 to 100.64.0.1
Tue Oct 1 16:16:55 2024 daemon.notice netifd: wan (21234): udhcpc: sending release
Tue Oct 1 16:16:55 2024 daemon.notice netifd: wan (21234): udhcpc: entering released state
Tue Oct 1 16:16:55 2024 daemon.notice netifd: wan (21234): Command failed: Permission denied
Tue Oct 1 16:16:55 2024 daemon.notice netifd: Interface 'wan' is now down
Tue Oct 1 16:16:55 2024 daemon.info avahi-daemon[5138]: Withdrawing address record for 100.105.221.10 on eth0.
Tue Oct 1 16:16:55 2024 daemon.info avahi-daemon[5138]: Leaving mDNS multicast group on interface eth0.IPv4 with address 100.105.221.10.
Tue Oct 1 16:16:55 2024 daemon.notice netifd: Interface 'wan' is disabled
Tue Oct 1 16:16:55 2024 daemon.info avahi-daemon[5138]: Interface eth0.IPv4 no longer relevant for mDNS.
Tue Oct 1 16:16:55 2024 daemon.info avahi-daemon[5138]: Interface eth0.IPv6 no longer relevant for mDNS.
Tue Oct 1 16:16:55 2024 daemon.info avahi-daemon[5138]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe3a:a031.
Tue Oct 1 16:16:55 2024 daemon.info avahi-daemon[5138]: Withdrawing address record for fe80::9683:c4ff:fe3a:a031 on eth0.
Tue Oct 1 16:16:55 2024 kern.info kernel: [719273.957223] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Oct 1 16:16:55 2024 daemon.notice netifd: Interface 'wan' is enabled
Tue Oct 1 16:16:55 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Tue Oct 1 16:16:55 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Tue Oct 1 16:16:55 2024 kern.debug kernel: [719274.309376] kmwan: Delete node:wan
Tue Oct 1 16:17:15 2024 kern.info kernel: [719294.438160] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Oct 1 16:17:15 2024 kern.info kernel: [719294.446706] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Oct 1 16:17:15 2024 daemon.notice netifd: Network device 'eth0' link is up
Tue Oct 1 16:17:15 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Oct 1 16:17:15 2024 daemon.notice netifd: Interface 'wan' is setting up now
Tue Oct 1 16:17:15 2024 daemon.notice netifd: wan (30270): udhcpc: started, v1.33.2
Tue Oct 1 16:17:15 2024 daemon.notice netifd: wan (30270): udhcpc: sending discover
Tue Oct 1 16:17:16 2024 kern.info kernel: [719295.461904] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Tue Oct 1 16:17:16 2024 daemon.notice netifd: Network device 'eth0' link is down
Tue Oct 1 16:17:16 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Oct 1 16:17:16 2024 daemon.notice netifd: wan (30270): udhcpc: received SIGTERM
Tue Oct 1 16:17:16 2024 daemon.notice netifd: wan (30270): udhcpc: entering released state
Tue Oct 1 16:17:16 2024 daemon.notice netifd: wan (30270): Command failed: Permission denied
Tue Oct 1 16:17:16 2024 daemon.notice netifd: Interface 'wan' is now down
Tue Oct 1 16:17:16 2024 daemon.notice netifd: Interface 'wan' is disabled
Tue Oct 1 16:17:16 2024 daemon.notice netifd: Interface 'wan' is enabled
Tue Oct 1 16:17:16 2024 kern.info kernel: [719295.535203] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Oct 1 16:17:16 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Tue Oct 1 16:17:17 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Tue Oct 1 16:18:34 2024 kern.info kernel: [719373.330057] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Oct 1 16:18:34 2024 kern.info kernel: [719373.338602] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Oct 1 16:18:34 2024 daemon.notice netifd: Network device 'eth0' link is up
Tue Oct 1 16:18:34 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Oct 1 16:18:34 2024 daemon.notice netifd: Interface 'wan' is setting up now
Tue Oct 1 16:18:34 2024 daemon.notice netifd: wan (31026): udhcpc: started, v1.33.2
Tue Oct 1 16:18:34 2024 daemon.notice netifd: wan (31026): udhcpc: sending discover
Tue Oct 1 16:18:36 2024 daemon.info avahi-daemon[5138]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe3a:a031.
Tue Oct 1 16:18:36 2024 daemon.info avahi-daemon[5138]: New relevant interface eth0.IPv6 for mDNS.
Tue Oct 1 16:18:36 2024 daemon.info avahi-daemon[5138]: Registering new address record for fe80::9683:c4ff:fe3a:a031 on eth0.*.
Tue Oct 1 16:18:38 2024 daemon.notice netifd: wan (31026): udhcpc: sending discover
Tue Oct 1 16:18:38 2024 daemon.notice netifd: wan (31026): udhcpc: sending select for 100.105.221.10
Tue Oct 1 16:18:38 2024 daemon.notice netifd: wan (31026): udhcpc: lease of 100.105.221.10 obtained, lease time 300
Tue Oct 1 16:18:38 2024 daemon.info avahi-daemon[5138]: Joining mDNS multicast group on interface eth0.IPv4 with address 100.105.221.10.
Tue Oct 1 16:18:38 2024 daemon.info avahi-daemon[5138]: New relevant interface eth0.IPv4 for mDNS.
Tue Oct 1 16:18:38 2024 daemon.info avahi-daemon[5138]: Registering new address record for 100.105.221.10 on eth0.IPv4.
Tue Oct 1 16:18:38 2024 daemon.notice netifd: Interface 'wan' is now up
Tue Oct 1 16:18:38 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Tue Oct 1 16:18:38 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" } ] } ] } }
Tue Oct 1 16:18:38 2024 kern.debug kernel: [719377.583424] [add_dev_config 287]add node success. iface:wan, dev:eth0, ifindex:2

3

In the MT3000 admin panel->Network->Network Acceleration, can you check if it is on.

Pls turn off Network Acceleration to see if it helps.

1 Like
5

It was off already.

I installed 4.5.16 again last night and will let it run for a few days. If I do not have any disconnects then something changed to cause them in the new version of the firmware 4.6.4.

I will post an update in 2 days.

Thank you.

1 Like
6

After about 4 days on the older firmware I have seen no drops to Starlink.

This means to me that an issue was introduced in the lastest version causing these drops on the WAN port.

Hoping someone from GL is paying attention and can look into this. If there are any logs I can send, I am happy to do so.

There is another thread on here also with the same issue to some other equipment. GL-MT3000 ethernet connection drops & no reconnect - #19 by UserGermany

8

Let me ask what the developer changed about the Ethernet driver between 4.5.16 and 4.6.4.

1 Like
9

Please try this modified firmware.

10

I will try it.

Do you want to see logs if the issue continues on this version, or just let you know that the issue still happens?

If the issue does not happen obviously I will let you know.