I am permanently connecting in repeater mode to a hotspot which has low signal quality and considerable noise. I cannot get closer to it unfortunately. Sometimes the connection is stable and works very well for hours, sometimes it disconnects every few minutes. gl_health seems to be doing a good job at reconnecting, but it takes a long time to do so - about 1 or 2 minutes. At times where the hotspot disconnects every other minute that means a lot of downtime. Is there any way I can increase the gl_health reconnect frequency?
@alzhao thank you for your answer. I have tried turning gl_health off before by renaming the binary. This resulted in the router not reconnecting at all when temporarily loosing connection to the hotspot.
Not reconnecting at all sounds worse than reconnecting slowly. Am I missing something?
ok, I disabled gl_health, commented out the BSSID line in the config config wifi-iface 'sta' section, which also mentioned the ssid of the hotspot I am connecting to. Then I rebooted the router. After the reboot, the ar750s reconnected automatically to the hotspot, so that’s very promising. I am now waiting for the first connection loss to see if automatic reconnecting works as desired.
Thank you so far. I appreciate the quick responses! Thank you alzhao! I will report back when I saw a disconnect or reconnect.
Btw, have you guys considered open sourcing gl_health? Might allow the community to help make it bullet proof and even give your company more exposure i.e. more customers in the openwrt space. I have been a software engineer at for-profit companies for many years and have only had good experiences with open sourcing non-mission-critical code, especially when it can be useful to others.
so funny thing. I did /etc/init.d/gl_health disable but after a reboot, it is running anyways. I checked ls /etc/rc.d/ but gl_health is not linked there. still it is running and the parent process id is 1. Will try again with renaming the gl_health binary to prevent it from running
ok, so I renamed /usr/bin/gl_health to /usr/bin/gl_health_ and rebooted. The AR750S connected to the hotspot at startup. But when it lost connection at some point it would not reconnect. So it looks like your recommendation did not help.
Maybe if you explain what the idea was it would help? Why disable gl_health and why would it automatically reconnect without a bssid?
actually, nevermind, something had re-written the /etc/config/wireless without commenting out the bssid. I commented it out again and now it looks like the connection survives the ap not being available. Will observe and report back
in the background, which seems to make it survive most longer outages. There are still some other problems with the hotspot de-authenticating me occasionally. I am running a re-auth script as well, but sometimes the captive login page of the hotspot seems broken, however rebooting the AR750S fixes it, which is confusing. But it’s hard to pinpoint what’s happening exactly.