msw
September 3, 2024, 8:17am
1
I have a GL-MT3000 working with a Yaosheng POE and V2 Starlink Dishy running on 12v DC.
Its been working okay for about 8 months, but has always randomly dropped internet connection over wifi and requiring rebooting router a few times a day.. but the speed was always 50 to 100+ mbps.
Recently the speeds have been below 1mbps, when the starlink test to the dish is showing above 150mbps. Testing with the original AC starlink shows speeds above 200mbps when getting obly 500kbps when using the MT-3000.
I have searched and followed advice to disable network acceleration which has not helped.
Another thread advised to cap speed at 100mbps. But I am not sure how you do this. Can someone breakdown the steps on luci so i can try this please?
msw
September 4, 2024, 1:15am
2
Exame of dropping internet connect at 09:10
Wed Sep 4 09:06:48 2024 daemon.info avahi-daemon[4211]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe3a:a745.
Wed Sep 4 09:06:48 2024 daemon.info avahi-daemon[4211]: Withdrawing address record for fe80::9683:c4ff:fe3a:a745 on eth0.
Wed Sep 4 09:06:48 2024 daemon.notice netifd: Interface 'wan' is disabled
Wed Sep 4 09:06:48 2024 daemon.notice netifd: Interface 'wan' is enabled
Wed Sep 4 09:06:48 2024 kern.info kernel: [ 245.894010] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Wed Sep 4 09:06:48 2024 daemon.warn dnsmasq[7542]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Wed Sep 4 09:06:48 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Wed Sep 4 09:06:48 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Wed Sep 4 09:06:48 2024 kern.debug kernel: [ 246.185858] kmwan: Delete node:wan
Wed Sep 4 09:06:52 2024 kern.info kernel: [ 249.983847] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Wed Sep 4 09:06:52 2024 kern.info kernel: [ 249.992307] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Wed Sep 4 09:06:52 2024 daemon.notice netifd: Network device 'eth0' link is up
Wed Sep 4 09:06:52 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Sep 4 09:06:52 2024 daemon.notice netifd: Interface 'wan' is setting up now
Wed Sep 4 09:06:52 2024 daemon.notice netifd: wan (10610): udhcpc: started, v1.33.2
Wed Sep 4 09:06:52 2024 daemon.notice netifd: wan (10610): udhcpc: sending discover
Wed Sep 4 09:06:52 2024 daemon.notice netifd: wan (10610): udhcpc: sending select for 100.84.53.198
Wed Sep 4 09:06:52 2024 daemon.notice netifd: wan (10610): udhcpc: lease of 100.84.53.198 obtained, lease time 300
Wed Sep 4 09:06:52 2024 daemon.info avahi-daemon[4211]: Joining mDNS multicast group on interface eth0.IPv4 with address 100.84.53.198.
Wed Sep 4 09:06:52 2024 daemon.info avahi-daemon[4211]: New relevant interface eth0.IPv4 for mDNS.
Wed Sep 4 09:06:52 2024 daemon.info avahi-daemon[4211]: Registering new address record for 100.84.53.198 on eth0.IPv4.
Wed Sep 4 09:06:52 2024 daemon.notice netifd: Interface 'wan' is now up
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain test
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain onion
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain localhost
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain local
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain invalid
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain bind
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using only locally-known addresses for domain lan
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using nameserver 1.1.1.1#53
Wed Sep 4 09:06:52 2024 daemon.info dnsmasq[7542]: using nameserver 8.8.8.8#53
Wed Sep 4 09:06:52 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Wed Sep 4 09:06:52 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 Sep 4 09:06:52 2024 kern.debug kernel: [ 250.423260] [add_dev_config 287]add node success. iface:wan, dev:eth0, ifindex:2
Wed Sep 4 09:06:53 2024 daemon.info avahi-daemon[4211]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe3a:a745.
Wed Sep 4 09:06:53 2024 daemon.info avahi-daemon[4211]: New relevant interface eth0.IPv6 for mDNS.
Wed Sep 4 09:06:53 2024 daemon.info avahi-daemon[4211]: Registering new address record for fe80::9683:c4ff:fe3a:a745 on eth0.*.
Wed Sep 4 09:09:22 2024 daemon.notice netifd: wan (10610): udhcpc: sending renew to 100.64.0.1
Wed Sep 4 09:10:37 2024 daemon.notice netifd: wan (10610): udhcpc: sending renew to 100.64.0.1
Copyright © 2024 GL.iNet. All Right
bruce
September 4, 2024, 10:20am
3
This issue probably is related to the compatibility of the POE adapter, some people have tried to change new one, and found the WAN link works well.
Thanks, Tim and GL.iNet Staff. In response to your suggestion, I contacted the folks who make the Dual midspan injector, and they sent me a replacement board. It turns out that was the bottleneck. Everything is negotiating correctly, and I am back in business.
I appreciate your support while I eliminated the various failure points to figure out a solution.
[Ethtool Screenshot]
If not change the POE adapter, can manually mandatory static the WAN negotiate rate in the SSH:
#Check what the WAN port name is
ifconfig
#If the WAN is eth1, and static to negotiate rate in 1000Mbps
ethtool -s eth1 speed 1000 duplex full