I use both GL-ARM300M NOR and GL-ARM300M NAND with 3.211 software version as access points for my personal network. GL-ARM300M NAND is wired-connected to my internet router via an ethernet switch. The internet router handles a DHCP server.
While I see no issue with GL-ARM300M NOR access point, I’ve got a recurrent issue with GL-ARM300M NAND where I observe internet traffic on devices connected through the access point becomes very slow, and additionally wifi authentication systematically fails. This is solved after reboot but aims to reoccur after few times (I estimate after 2-3 weeks).
I’d like to investigate the issue to solve it for good. Can you please help me discriminate the problem and use the right tool into OpenWRT environment to find out the root cause?
If the issue is fixed after reboot and the issue repeats itself once every 2 weeks, then use a smart plug (schedule the smart plug to restart itself once per day)
The device runs in Access Point mode. It doesn’t manage IP addresses as DHCP server runs on my internet router. So devices wired-connected to the router (NAS, computer…) share the same subnet with those wireless-connected (laptop, mobile phone) through the access point.
AR300M and AR300M16 should not be different in these setup.
I’ve checked settings in Luci UI for both GL-AR300M NAND and GL-AR300M NOR. They have the same but on channel (I manually force channel 1 for NOR and channel 8 for NAND).
Both GL-AR300M NOR and NAND share the same Wifi SSID and password. So user automatically connects (and switches as needed) depending on connection quality between both the devices.
This February-17, the issue shows up once more on GL-AR300M NAND. I observe:
User can’t see anymore Wifi network provided by GL-AR300M NAND in the list of available wireless networks. I deduce the device doesn’t spread any info anymore over-the-air. (Even if SSID was hidden, I expect the user can still detect and connect as network details were priorly saved as favorite. But that’s not the case)
It seems remaining wireless connections weren’t abruptly shutdown. The device disconnected users based on the expected inactivity time out.
Please have below the links to System Log and Kernel Log:
I can’t find any issue there. You can see the device stopped receiving connection requests from users on February-17.
So I’m looking for a cause why GL-AR300M NAND doesn’t publish its wireless details over-the-air.
Thinking of the Wifi chip to be out of power, I’ve just tried to have the device scans wireless interfaces in Luci by clicking on Scan in front of radio0. It seems it powers up the radio chip again and wlan0 is now available again.
Can you change to wap2 and check in case this is the problem?
The “Status” page shows the signal. But I guess that it will only show one value if you have device connected to the wifi. Otherwise it will show as 0.
Can you change to wap2 and check in case this is the problem?
I’ve just changed encryption mode from WPA2/WPA3 to WPA2. I’ll check whether the issue reoccurs.
The “Status” page shows the signal. But I guess that it will only show one value if you have device connected to the wifi. Otherwise it will show as 0.
That makes sense. Because none of my phone was wireless-connected, then it showed 0.
Hi silkweb,
I can actually design a software solution in the access point (e.g. having a cron task to reboot the device).
My point in this thread is to understand the cause why the device is abruptly not accessible anymore for Wifi client.
Please let me know if you need additional setting details to reproduce a twin of my device.
Currently I only observe the issue from Client point of view. I.e. My laptop can’t see the wifi network any longer. As I check the access point, there is no alert saying there is something wrong. Can I have the possibility to get the modem status and statistics in the access point? By this way, we may figure out what the problem is.
Comparing to my GL-AR300M NOR, I’ve just removed extra packages I had in GL-AR300M NAND (such as ath10k-firmware-qca9887). I’ll see whether this change the issue.