Question about log entry that appears every 1 second on GL-X3000

[silvercreek]

My router log is filled with these entries… are they normal/expected? Or sign of an issue?

Fri Jun 23 08:58:00 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:01 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:01 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:02 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:02 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:03 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:03 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:04 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:04 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:05 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:05 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:06 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:06 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:07 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:07 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:08 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:08 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:09 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:09 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Jun 23 08:58:10 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Jun 23 08:58:10 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…

[Dipin]

How long does this REPEATER error log continue to report? Is it reported every second? Or does it break after a period of time?

[silvercreek]

I have been watching it for a while now and it is continuous. Every 1 second “forever.”

I also noticed this a few times:

Tue Jun 27 11:45:00 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:01 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:01 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:02 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:02 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:03 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:03 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.517871] 7981@C08L3,ap_peer_auth_req_at_idle_action() 717: AUTH - MBSS(0), Rcv AUTH seq#1, Alg=0, Status=0 from [wcid=1023]fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:03 2023 kern.debug kernel: [756492.531608] entrytb_aid_aquire(): found non-occupied aid:9, allocated from:4
Tue Jun 27 11:45:03 2023 kern.warn kernel: [756492.538786] 7981@C13L2,MacTableInsertEntry() 1537: New Sta:fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.578820] 7981@C08L3,ap_cmm_peer_assoc_req_action() 1647: Recv Assoc from STA - fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.588420] 7981@C08L3,ap_cmm_peer_assoc_req_action() 2170: ASSOC Send ASSOC response (Status=0)…
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.597756] 7981@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.603899] 7981@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.724532] 7981@C15L3,WPABuildPairMsg1() 5280: <=== send Msg1 of 4-way
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.732870] 7981@C15L3,PeerPairMsg2Action() 6199: ===>Receive msg 2
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.739907] 7981@C15L3,WPABuildPairMsg3() 5557: <=== send Msg3 of 4-way
Tue Jun 27 11:45:03 2023 kern.notice kernel: [756492.746771] 7981@C15L3,PeerPairMsg4Action() 6629: ===>Receive msg 4
Tue Jun 27 11:45:03 2023 kern.warn kernel: [756492.758776] 7981@C15L2,PeerPairMsg4Action() 6991: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=6 from fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:03 2023 kern.warn kernel: [756492.758776]
Tue Jun 27 11:45:04 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:04 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:05 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:05 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:06 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:06 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:06 2023 daemon.info dnsmasq-dhcp[4971]: DHCPDISCOVER(br-lan) fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:06 2023 daemon.info dnsmasq-dhcp[4971]: DHCPOFFER(br-lan) 192.168.8.209 fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:06 2023 daemon.info dnsmasq-dhcp[4971]: DHCPDISCOVER(br-lan) fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:06 2023 daemon.info dnsmasq-dhcp[4971]: DHCPOFFER(br-lan) 192.168.8.209 fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:07 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:07 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:07 2023 daemon.info dnsmasq-dhcp[4971]: DHCPREQUEST(br-lan) 192.168.8.209 fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:07 2023 daemon.info dnsmasq-dhcp[4971]: DHCPACK(br-lan) 192.168.8.209 fa:ea:fe:cc:e4:af
Tue Jun 27 11:45:08 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:08 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:09 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:09 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Tue Jun 27 11:45:10 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Tue Jun 27 11:45:10 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…

[silvercreek]

Following up on this. Any ideas here?

Thanks!

[bring.fringe18]

Wow. That’s wild. Have you tried resetting to factory defaults &, should that fail to resolve it, reflash via Uboot?

I’d pull a backup regardless even if you don’t.

HOW-TO: Script: List My OPKGs (to a file for backup)

Keywords: backup, opkg, plugins, list, howto, script, shell, luci, restore, ipk, tarball, conf Description List user’s (your) installed packages, writing them to a text file that can be used to reinstall the binaries of what a user manually installed. The resulting .list file will be use to opkg install to pull from the feeds. That is done with two commands in one execution. The GL GUI doesn’t feature a backup function. Creating & restoring a backup achieve (.tar.gz, aka tarball) of all your…

[alzhao]

Seems a problem related to repeater. Try
remove all saved ssids and disable repeater
reset firmware
upgrade firmware

[silvercreek]

So here is the thing… repeater mode is DISABLED. I don’t use it or need it.

I updated to the latest firmware today and the issue is still appearing…

Thoughts?

Fri Aug 4 09:33:34 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Aug 4 09:33:34 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Aug 4 09:33:35 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Aug 4 09:33:35 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Aug 4 09:33:36 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Aug 4 09:33:36 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…
Fri Aug 4 09:33:37 2023 daemon.info repeater: (/usr/sbin/repeater:374) found device: mt798111 mtk ra0 2g
Fri Aug 4 09:33:37 2023 daemon.err repeater: (/usr/sbin/repeater:355) rax0: Wait phy ready…

[silvercreek]

Hello,

Any suggestions?

Thanks

[ScottD]

Ok, I had the same thing happening. This specific error only seems to happen with me when I have the GL EX3000 Wi-Fi turned off and just using the modem and router functions.
I tried to resolve this looking at the scripts and processes being used without much success being a persistent resolution. But the work around would be to turn either the 5Ghz or 2.4Ghz Wi-Fi on, wait a minute and turn it off again then the message will stop being logged.
But if you reboot the device the message will start populating again every one second until you turn on and off the Wi-Fi again.
Attempting to fix this with a fresh install or downgrading of the firmware starting fresh (no restore from backup) did not fix this.

[silvercreek]

Great tips, thanks Scott! I did indeed disable my 5G WiFi radio and wonder if perhaps the bug is related to that. I will test it out later today and report back.

[silvercreek]

Confirmed that enabling the 5G Wi-Fi radio, then disabling it again stops the messages until the next reboot. Really frustrating bug.

[Dominion7574]

Pretty sure mine quit on the latest beta. But now I have tailroom or whatever full errors all the time.

[alzhao]

Today’s (2023-09-07) beta should have already fixed it.
https://dl.gl-inet.com/?model=x3000&type=beta

[cjt20]

Interesting thread this. I’ve just bought a Spitz AX and been suffering loss of connection.
I have a separate mesh WiFi, so the Spitz takes care of the modem and router side of things - the repeater is off.

Several times a day the modem would drop connection and WiFi connection would also disappear.

I initially upgraded to firmware 4.0-release50402 in the hope of solving it but no joy. Also tried beta 4.0-release10403 and previous stable releases.

After reading another thread with others having similar issues, they’d had success with 4.0-release20300.
I’ve tried the same today and so far so good in terms of connection dropping, but I do see the same “daemon.info repeater” entries in the system log.
I’ve turned WiFi on the Spitz AX on and off again and the entries in system have stopped.
Let’s just hope the connection remains stable from now on.