GL-AR300M in WDS mode "forgets" passkey

Router
1

Dear community,

I am using a GL-AR300M in WDS mode to extend the WIFI coverage in my basement. This is basically working fine. However, after a few weeks of running flawlessly, the GL-AR300M seems to “forget” the passkey of the WIFI network it connects to.

What I do in this case, is to connect the GL-AR300M to LAN and to specify the passkey again in the “network mode” page of the admin panel. After that it is working fine again for a few weeks. But then it starts all over again and it seems to “forget” the password again after a few weeks.

The latest firmware (4.3.27) is installed.

Has anyone an idea what I can do to prevent this? It is very annoying because the GL-AR300M is installed in a not very accessible spot in my basement and it is always a pain to remove it from there to connect it to LAN in order to specify the passkey again.

Any hints to resolve the issue are highly appreciated.

Thanks and best regards…

1 Like
2

Hi,

This seems a bit strange. If the AR300M is in WDS mode and fails to connect to the main network, there typically shouldn't be a way to access the Admin Panel without either resetting the network configuration or performing a factory reset.

Did you reset the network configuration or perform a factory reset after the problem occurred? If you reboot the device instead of resetting it, is the AR300M able to restore the connection?

4

Hi Will,

thanks for your reply.

No, I didn’t have to do a factory reset. All I had to do is to connect to the AR300M via LAN and specify the passkey of the “host” wifi network again. A reboot unfortunately did not solve the issue.

Any idea, how I could prevent this in the future?

Thanks and best regards…

5

At the moment, we don’t really have any clues about this issue.

Please do the following after the problem occurs again:

  1. Take a screenshot of Admin Panel → Network → Network Mode so we can confirm which mode it’s in.
  2. SSH into the router and run the following command to verify whether the upstream Wi-Fi configuration still exists:
uci show wireless.sta
# AND
uci show | grep {your_upstream_SSID}
  1. Export the device logs and send them to us via private message so we can investigate further.

How to export logs:

image
image1430×911 87 KB

How to send private messages:

image
image632×233 19.1 KB

6

Hi Will,

perfect, I will do so as soon as the problem occurs again. As written above, it runs stable for a few weeks or even months. I hope it’s okay to keep the topic open.

Best regards…

7

This thread will remain open.

If it closes automatically after three months, you may send me a private message to have it reopened.

8

Hello Will,

the problem occurred again. Therefore I send you the requested screenshots.

  1. Network Mode

network_mode
network_mode952×615 55.9 KB

  1. SSH (in the erroneous state)

ssh_before
ssh_before580×459 31.3 KB

2 b. SSH (after I typed in the password again in the WDS configuration)

ssh_after
ssh_after575×570 36.6 KB

  1. Logs - I will send them via private message as requested by you.

I hope you can find something useful.

Thanks in advance for your help.

1 Like
9

Do you have any idea already?

10

Our office is closed for the Spring Festival holiday. We will check it out with the team after we return on February 24th.

Thank you for your understanding.

11

Just to let you know that we’re back from the holiday and have already asked the R&D team to start looking into this.

12

Just wanted to check if there is an update already…

13

We were able to reproduce the issue once in our local environment, and based on that, the development team has implemented a fix.

It is currently still undergoing testing and validation to confirm whether it fully resolves the problem. However, progress has been slow, as the issue is difficult to reproduce in our test environment.

If you’re willing, we can provide a special firmware build based on the stable version v4.3.25 with this fix included, so you can help verify whether it resolves the issue in your environment.