GL-AXT1800 Slate AX WAN ethernet issues

Firmware: 4.6.4

Good morning running the router above and have been traveling a bit with no issues with the router (repeater and ethernet WAN). I am currently in a location ill be hang around for a bit and the wireless is a bit iffy so the repeater mode isnt gonna work. I have an ethernet cable in my room and if I plug my USB network into my mac into the wall port I get a stable wired connection. I will note the ethernet cable does link up as 100TX full on MacOS

However for whatever reason I cannot get the WAN port on this device to get a stable ethernet connection.

root@GL-AXT1800:~# logread -e link
Thu Sep 5 02:14:45 2024 kern.err kernel: [ 0.293335] qcom_glink_rpm soc:qcom,rpmsg-rpm@60000: RPM TOC has invalid magic
Thu Sep 5 02:14:45 2024 kern.warn kernel: [ 0.293356] qcom_glink_rpm: probe of soc:qcom,rpmsg-rpm@60000 failed with error -22
Thu Sep 5 02:14:45 2024 kern.warn kernel: [ 13.060955] qca_link_polling_select[1315]:INFO:link-polling-required node does not exist
Thu Sep 5 02:14:45 2024 kern.info kernel: [ 13.722626] ctnetlink v0.93: registering with nfnetlink.
Thu Sep 5 02:14:55 2024 kern.info kernel: [ 38.274272] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Thu Sep 5 02:14:55 2024 kern.info kernel: [ 38.274699] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Thu Sep 5 02:14:55 2024 kern.info kernel: [ 38.279324] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Sep 5 02:14:55 2024 kern.info kernel: [ 38.285312] IPv6: ADDRCONF(NETDEV_UP): lo: link is not ready
Thu Sep 5 02:14:55 2024 daemon.notice netifd: bridge 'br-lan' link is up
Thu Sep 5 02:14:55 2024 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Sep 5 02:14:55 2024 kern.info kernel: [ 38.323747] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Sep 5 02:14:55 2024 daemon.notice netifd: Network device 'lo' link is up
Thu Sep 5 02:14:55 2024 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Sep 5 02:14:57 2024 daemon.notice netifd: bridge 'br-lan' link is down
Thu Sep 5 02:14:57 2024 daemon.notice netifd: Interface 'lan' has link connectivity loss
Thu Sep 5 02:15:03 2024 daemon.notice netifd: Network device 'wlan1' link is up
Thu Sep 5 02:15:03 2024 daemon.notice netifd: bridge 'br-lan' link is up
Thu Sep 5 02:15:03 2024 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Sep 5 02:15:07 2024 daemon.notice netifd: Network device 'wlan0' link is up
Sun Oct 6 12:13:20 2024 daemon.notice netifd: Network device 'eth0' link is up
Sun Oct 6 12:13:20 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Oct 6 12:13:20 2024 kern.info kernel: [ 918.164846] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@GL-AXT1800:~#

root@GL-AXT1800:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 10Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Link detected: yes

It looks like its only negotiation at 10 full on the router but im dropping a lot of packets to the Internet (pinging 4.2.2.2 so its getting out) and no websites ever load

If I move the cable back to my MacBook usb network card it syncs at 100 full and I get stable internet and can reach the internet.

I have also tried a different network cable with the same results

Any suggestions for next steps? Thanks!

I was reading around some other similar posts and some people had luck with placing a dumb switch between their gl inet router WAN port and the wall.

It cleared up my issue up and now everything is stable, but this is not an optimal solution

This may be a compatibility issue with the phy on the opposite terminal
There's no better way

Weird every other device I plug in that port links up just fine (pi and Windows box).

Guess ill have to keep that in mind down the road for other environments that have 100 mbps ports