Occasional internet loss on GL-AX1800

Technical Support for Routers
1
  • GL-AX1800 (Flint)
  • firmware version 4.6.2 type release2
  • via cable to my ISP
  • dns server next dns
  • DHCP

Here some logs
Sun Aug 25 03:34:59 2024 kern.warn kernel: [ 4780.620222] [add_dev_config 287]add node success. iface:wan, dev:eth0, ifindex:2
Sun Aug 25 03:35:00 2024 daemon.info avahi-daemon[5095]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe16:fef0.
Sun Aug 25 03:35:00 2024 daemon.info avahi-daemon[5095]: New relevant interface eth0.IPv6 for mDNS.
Sun Aug 25 03:35:00 2024 daemon.info avahi-daemon[5095]: Registering new address record for fe80::9683:c4ff:fe16:fef0 on eth0.*.
Sun Aug 25 03:40:07 2024 daemon.notice netifd: Network device 'eth0' link is down
Sun Aug 25 03:40:07 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Aug 25 03:40:07 2024 kern.info kernel: [ 5088.445715] nss-dp 3a001000.dp1 eth0: PHY Link is down
Sun Aug 25 03:40:07 2024 daemon.notice netifd: wan (17323): udhcpc: received SIGTERM
Sun Aug 25 03:40:07 2024 daemon.notice netifd: wan (17323): udhcpc: unicasting a release of 10.35.220.45 to 10.37.126.50
Sun Aug 25 03:40:07 2024 daemon.notice netifd: wan (17323): udhcpc: sending release
Sun Aug 25 03:40:07 2024 daemon.notice netifd: wan (17323): udhcpc: entering released state
Sun Aug 25 03:40:07 2024 daemon.notice netifd: wan (17323): Command failed: Permission denied
Sun Aug 25 03:40:07 2024 daemon.notice netifd: Interface 'wan' is now down
Sun Aug 25 03:40:07 2024 daemon.info avahi-daemon[5095]: Withdrawing address record for 10.35.220.45 on eth0.
Sun Aug 25 03:40:07 2024 daemon.info avahi-daemon[5095]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.35.220.45.
Sun Aug 25 03:40:07 2024 daemon.info avahi-daemon[5095]: Interface eth0.IPv4 no longer relevant for mDNS.
Sun Aug 25 03:40:07 2024 daemon.info avahi-daemon[5095]: Interface eth0.IPv6 no longer relevant for mDNS.
Sun Aug 25 03:40:07 2024 daemon.info avahi-daemon[5095]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe16:fef0.
Sun Aug 25 03:40:07 2024 daemon.info avahi-daemon[5095]: Withdrawing address record for fe80::9683:c4ff:fe16:fef0 on eth0.
Sun Aug 25 03:40:07 2024 daemon.notice netifd: Interface 'wan' is disabled
Sun Aug 25 03:40:07 2024 daemon.notice netifd: Interface 'wan' is enabled
Sun Aug 25 03:40:07 2024 kern.info kernel: [ 5088.507665] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sun Aug 25 03:40:07 2024 user.notice firewall: Reloading firewall due to ifdown of wan ()
Sun Aug 25 03:40:08 2024 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wan" ] } }
Sun Aug 25 03:40:08 2024 kern.warn kernel: [ 5089.321079] kmwan: Delete node:wan
Sun Aug 25 03:40:08 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:08 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:08 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:08 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:08 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:10 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:10 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:10 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:10 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:10 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:10 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:13 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:13 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:13 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:13 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:13 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:13 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:15 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:15 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:15 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:15 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:15 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:15 2024 daemon.err stubby[16171]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Sun Aug 25 03:40:16 2024 daemon.notice netifd: Network device 'eth0' link is up
Sun Aug 25 03:40:16 2024 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Aug 25 03:40:16 2024 daemon.notice netifd: Interface 'wan' is setting up now
Sun Aug 25 03:40:16 2024 kern.info kernel: [ 5097.445427] nss-dp 3a001000.dp1 eth0: PHY Link up speed: 100
Sun Aug 25 03:40:16 2024 kern.info kernel: [ 5097.445491] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sun Aug 25 03:40:16 2024 daemon.notice netifd: wan (19846): udhcpc: started, v1.33.2
Sun Aug 25 03:40:16 2024 daemon.notice netifd: wan (19846): udhcpc: sending discover
Sun Aug 25 03:40:16 2024 daemon.notice netifd: wan (19846): udhcpc: sending select for 10.35.220.45
Sun Aug 25 03:40:16 2024 daemon.notice netifd: wan (19846): udhcpc: lease of 10.35.220.45 obtained, lease time 86400
Sun Aug 25 03:40:16 2024 daemon.info avahi-daemon[5095]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.35.220.45.
Sun Aug 25 03:40:16 2024 daemon.info avahi-daemon[5095]: New relevant interface eth0.IPv4 for mDNS.
Sun Aug 25 03:40:16 2024 daemon.info avahi-daemon[5095]: Registering new address record for 10.35.220.45 on eth0.IPv4.
Sun Aug 25 03:40:16 2024 daemon.notice netifd: Interface 'wan' is now up
Sun Aug 25 03:40:16 2024 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Sun Aug 25 03:40:17 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" } ] } ] } }

2

May I know does the Ethernet port of another side device 100Mbps which connected with the AX1800?

If not, please check your network cable or the wall socket (if have), change better one

3

Yes, it works fine with different router.

4

What the WAN device is?

Is it the starlink?

May try fixed the WAN negotiation rate for the interface in SSH:

#Check the router WAN interface:
ifconfig

#Fixed the negotiation rate for the WAN, example, the WAN is eth1, and fixed 100Mbps
​ethtool -s eth1 speed 100 duplex full
5

I’m having a similar problem with my beryl ax. I’m using a development board with rm520 5G module. It connects and works good for a few mins then it drops for 30 seconds or so and connects right back. I’m new to all this stuff so I’m pretty confused

6

ISP Network switch, not starlink.

7

Disconnect for 30 seconds every few minutes?
Or a few hours?

1 Like
8

Every few minutes. I’m using a US Mobile dark star SIM card, which is ATT network

9

Can you show me the log?
Direct message to me

image
image927×276 19.4 KB

10

Please try to change a better one network cable.

Or manually set-up the negotiate rate: