While the above deals with both WAN and LAN WiFi dropping due to WAN signal problems (and how to rectify the LAN WiFi dropping when the issue should be isolated to the WAN WiFi connection), I have since discovered an issue with LAN WiFi dropping out while using Wired WAN with no Wireless WAN connection.
This issue was occurring because of a repeating script triggered on boot and running every 15 seconds that appears to re-scan for wireless connections. I can’t recall if this was added by stock firmware or something that I added from a forum recommendation because of my unit being one with a 5Ghz radio. To resolve the problem I did the following:
- Log in to Advanced / LuCI Interface.
- Go to System > Startup and scroll to bottom where the “Local Startup” section is.
- Comment out this line which is near the bottom of the Local Startup textarea (add a # to the start of the line):
(sleep 15;/usr/bin/gl_health) &
I see this fix can also be found here.
After commenting it out, the issue went away and I’m able to keep my wired WAN connection and WiFi LAN going continuously. I haven’t tested using a WiFi WAN connection in client mode since making this change, so I suppose it’s possible that turning off the gl_health script could break WiFi WAN connections. We shall find out.
Note that when I was previously using WiFi WAN in client mode, the gl_health script seemingly created no issues. There were occasional disconnects, but not nearly as frequent as when using wired WAN.
Is there, perhaps, a need to have the gl_health script updated to detect if actually using wireless WAN before doing its usual scan?