Repeater (STA) is disabled - can't enable

Hello, I don't understand why the repeater function is disabled. It was working this morning. Then I turned off the GLE and restarted it somewhere else, and since then it hasn't been working. I haven't changed anything.

I have restarted the router about 10 times and left it on for a longer period.

Nothing.. i was so happy about this function! a reason to buy this Router for business tris and hotels!

Hope somebody have an idea.

thanks for help!

System Log:
Mon Jun 10 20:05:18 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:19 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:20 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:21 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:22 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:23 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:24 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:25 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:26 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:27 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:28 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:29 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:30 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:31 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:32 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:33 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:34 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:35 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:36 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:37 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:38 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:39 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...
Mon Jun 10 20:05:40 2024 daemon.err lua: (...6e/ipkg-mips_24kc/gl-sdk4-repeater/usr/sbin/repeater:385) Wait phy ready...

Kernel Log:
[ 140.625373] br-guest: port 1(wlan0-1) entered blocking state
[ 140.625395] br-guest: port 1(wlan0-1) entered forwarding state
[ 163.117425] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
[ 163.166837] br-lan: port 3(wlan1) entered blocking state
[ 163.166859] br-lan: port 3(wlan1) entered disabled state
[ 163.167280] device wlan1 entered promiscuous mode
[ 164.613788] br-lan: port 3(wlan1) entered blocking state
[ 164.613810] br-lan: port 3(wlan1) entered forwarding state
[ 164.690130] br-guest: port 2(wlan1-1) entered blocking state
[ 164.690153] br-guest: port 2(wlan1-1) entered disabled state
[ 164.690626] device wlan1-1 entered promiscuous mode
[ 164.707490] br-guest: port 2(wlan1-1) entered blocking state
[ 164.707514] br-guest: port 2(wlan1-1) entered forwarding state
[ 356.512972] br-lan: port 3(wlan1) entered disabled state
[ 356.551146] device wlan1 left promiscuous mode
[ 356.551172] br-lan: port 3(wlan1) entered disabled state
[ 356.788286] br-guest: port 2(wlan1-1) entered disabled state
[ 356.871269] device wlan1-1 left promiscuous mode
[ 356.871295] br-guest: port 2(wlan1-1) entered disabled state
[ 366.196258] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
[ 374.526946] br-guest: port 1(wlan0-1) entered disabled state
[ 374.530258] device wlan0-1 left promiscuous mode
[ 374.530491] br-guest: port 1(wlan0-1) entered disabled state
[ 374.544057] tertf: br-guest changed, delete it
[ 377.047149] device wlan0 left promiscuous mode
[ 377.047314] br-lan: port 2(wlan0) entered disabled state
[ 385.195594] br-lan: port 2(wlan0) entered blocking state
[ 385.195615] br-lan: port 2(wlan0) entered disabled state
[ 385.196028] device wlan0 entered promiscuous mode
[ 385.869423] br-lan: port 2(wlan0) entered blocking state
[ 385.869446] br-lan: port 2(wlan0) entered forwarding state

Hi,

Could you please try to restore the router? SYSTEM-> Reset Firmware -> Find it.

Seems that the radio is locked for some reason.

What is your router model and firmware version?

Reset the firmware and upgrade the latest.

Hello @alzhao ,

I don't want to reset my router. I just finished setting it up, and the first thing I'm supposed to do is delete everything and reset it?

Then I would have to set up my WiFi, OpenVPN, and Wireguard connections all over again. I would like to solve the problem before I spend another 2 hours configuring and end up in the same problem.

Model GL.iNet GL-E750
Architecture
Qualcomm Atheros QCA9533 ver 2 rev 0
OpenWrt 22.03.4 r20123-38ccc47687
Kernel Version 5.10.176

Sure, try to reboot the router instead of reset first, and check one more time to see if does the repeater mode work ok, and does the syslog appear the 'Wait phy ready'?

Cause reviews the above syslog, its Wi-Fi chips have been occupied or locked.

Sure, here is the translation:

Hello,
as mentioned above, I have tried many reboots. I have now made a backup via the advanced interface, reset the router, and performed a restore.

Now it seems to be working again. But for how long? It worked in the morning, then I turned it off and later turned it back on, and it didn't work anymore.

I will test it now and report back. Thanks.

Hi, May I know when the repeater (STA) mode occur issue, if is the AP SSID of the E750 still connected or permit to connect with your phone?

I don't quite understand the question.

The router is supposed to connect as a repeater in the WLAN, but the option does not work. I didn't have a choice to find the WLAN. Currently, after the reset and restore, it works again everywhere.

I will restart it a few times later.

It just seems that repeater is not connected so the router just disabled that.

This happens, for example, you put a wrong wifi key or the wifi network has problems. After many tries the router will stop trying to connect. Looks like it disabled repeater.

But if you reboot it will try again.

Hello,

the Router was powered on since 4 day. i do nothing. no reboot, no config.

Tomorrow moring wireguard was down. after reboot an installing wireguard packing, wireguard was working.

but after this reboot repeter is disabled and i can't enable.

is this need for repeter?

after pressing restart -> nothing.

then i used scan .. just pressing scan and the repeater connected.
i don't choose a network there. before it show the networks the repeater was conntected

It seems the repeater has connected during in scanning, since the GL GUI repeater and Luci is not the same one program, and the GL repeater program is able to try re-connecting upstream Wi-Fi automatically after you restart the interface or reboot the router.

But what is the solution now? Always restart the router when it doesn't work? That's not a solution. Only restarting the interface in Luci made a difference. But that's not a solution I can give to my customers if I want to sell them the device. They shouldn't have to go into Luci.

May I know this issue still occur after you try to restore the router?

I have not very clear what third-party plugins you installed in the router, probably to occupy the Wi-Fi PHY (hardware), pls restore first and observe for a period of time to see.

Please attached the syslog if the situation occurs again without any others features enabled except the Wi-Fi and repeater.

Can you clarify:

When the repeater is disabled, can you use the default UI and search WiFi network and connect?

Seems you are saying that only luci works.

In your image, the wifi network "Pommesbude" is using channel 36, can you confirm? You can go to the router's admin panel->wifi and check the router's 5G wifi channel.

I don't understand this router. Everything was great for a few days. Now today I wanted to use it again.

Wireguard in LuCi wasn't working. Nothing, it didn't display the connections. The repeater was okay.
Then I did the firmware update to the new version.
Same problem.
Then, under the new version, I restored the last backup. Now Wireguard works again, but the repeater doesn't.

When it's disabled, it can't be activated. It then also doesn't find any other networks in the admin interface, even though there are definitely some there.
Today, there is a new network that it should be able to find.

GLI don't find the network!

20min later......
after restarting ... repeater will be work!
whats work there??

If you configure Wireguard in the default firmware it does not show the correct status in Luci.

So you have to configure everything separately in Luci. Whether it work or not depends on your configuration. Just remember don't config Wireguard in the default UI at the same time.

For the repeater, when it has problems, pls check the current wifi channel it is using.
The UI shows channel 40. Not sure if this is the channel it is using when you have problems.
The 2.4G wifi channel is using channel 8, which it should not. 2.4G wifi should just use channel 1, 6 and 11. Other channels only make more interference.

1 Like

Hello,
Of course, I configured Wireguard in LuCI.
This is just for your information. I'm not sure if LuCI is supported by GLI.

More importantly, the repeater function!

After the restore and restart of the interfaces as shown in the picture, it works again for a short time.
I cannot change the WLAN channel of the host in which I register as a client. But there is also a problem in the router that services do not start. You can see that LuCI finds WLANs and the GLI interface does not.

Can you give me the wifi channel that you are using when it has problems?

Just go to the Admin panel, WiFi settings and send me a screenshot. Both 2.4G and 5G.

Pls give the exact firmware version.

For the firmware version pls refer to GL.iNet download center

The kernel version etc does not tell the exact firmware version.

Can you send me the content of your full /etc/config/wireless file. You can mark your wifi key but I want to do a test using the exact config like yours.