Hello,
I’m a manager of a fairly large fleet of gl-inet routers. Currently in the 850+ range of units. The vast majority of them are AR300m.
The model is identical on nearly all of them - or rather the issue i’m having on many is for a particular common configuration set.
Here are the common elements for the issue that I’m able to track
Firmware v4.x (firmware 3.x unaffected)
Repeater mode
Our workflow is that we pre-setup the router with goodcloud templates and deploy them in the office. Our field team installs the unit inside the other hardware onsite. They login to the router’s interface and using repeater mode, attach it to the local Wi-Fi network. This part goes fine.
Part of our workflow is some of the sites we work on get shut down for days/weeks/month before being turned on again. We are finding that on occasion, but more than is normal - when the whole system gets turned back on, the repeater mode never reconnects. Even with no changes in the SSID of the connected endpoint.
Further - We’re getting very frequent disconnects and then no reconnection. We have to either go back onsite to reconnect the repeater or have the homeowner do the task. It’s gotten so bad, i’d say at least 25% or more of the sites are like this. I’m not sure if its an issue with the specific equipment settings on the other side, or if there is a bug in your reconnect logic. It just seems like it gives up after a time. Is the reconnect frequency to high and getting blocked? but if that were the case, we wouldn’t be able to manually reconnect either.
I’m surprised im not seeing more reports - other than it sounds like this issue here: AR300M (NOR) - repeater auto-reconnect
-Cory