WAX610 needs reboot daily, before clients can connect

[dhda]

Approaching the WAX610 AP, WIFI Analyzer shows the strong  signal (-40dB) but Android as well as Windows clients do not connect, not even after switching OFF/ON WIFI. They remain on an AP, too far away or even switch to 4G data.

Netgear insight shows 0 Clients on that AP.

Only after rebooting the AP (through Insight) all clients connect perfectly to the AP (switching OFF/ON WIFI preferable).

Next day, the same procedure seems required.

AP's are connected by unmanaged PoE+ switches to the (TELENET) Modem/Router  of the provider.

Sincere thanks for any suggestions.

[RaghuHR]

Hi @dhda  Could you please go to monitoring page and download the detailed logs before you reboot the AP? Send me the link to download the logs via PM. We will check the logs and update you.

Thanks,

Raghu.

[dhda]

Hi RaghuHR,

Many thanks for your reply.

Around 12:45, went from AP IP ...101 to AP IP ...249 with phone MAC ...56:00:58.

0 Clients on AP 249, (5) clients are connected to AP 101.

Phone does not connect to closest AP (according WiFi Analyzer ddistance <1m / -45dB), not even after WIFI OFF (4G takes over) and back to WIFI ON.

If we would reboot AP 249, it will.

Downloaded Detailed Log or AP 249.

What do you mean with send link via PM (to provide you the log) ?

Best Regards,

Danny

[schumaku]

---

@dhda wrote:

What do you mean with send link via PM (to provide you the log) ?

---

Put the log file(s) on any kind of cloud storage which allows to share files using a simple link.

[dhda]

Should be available in OneDrive : https://1drv.ms/u/s!Ai4PEQfZRtEfgpBb10dZLi8Ir3aB5g?e=xZx00f

[dhda]

In the meanwhile, here's a link of the logfile, after the AP had been restarted : https://1drv.ms/u/s!Ai4PEQfZRtEfgpBcD7nbTJ_G7V_I-w?e=1kuqJY

About 7 clients have been connected since, before this remained 0 clients.

Hope the logfiles can clear something out.

[RaghuHR]

Hi @dhda 

I think you are roaming between two APs...P IP ...101 to AP IP ...249  Could you please provide the detailed logs of both the APs? AP IP ...101 and  AP IP ...249?

Thanks,

Raghu

[dhda]

Just realised, the logging of the other AP (IP 101) covers the whole period, cause it hasn't been rebooted since the morning.

This means the test around 12:45, trying to connect, moving from 101 to 249 is in the log, as well as the test and the reboot of 249 later on, after which everything connected to it.

Link to the log of 101 : https://1drv.ms/u/s!Ai4PEQfZRtEfgpBdw2aFW_R60PkPcg?e=wOqrp1

In the meanwhile, AP with IP 101 seems getting  IP 154.

Best Regards (and enjoy the long weekend ?)

[dhda]

May I ask if the latest log maybe could clarify a little more ?

In the meanwhile, there was one day the AP didn't has to be rebooted (!?), but all other times, number of clients remained 0 (according to insight and also the weak connection on the client), untill the AP had been rebooted.

Thanks in advance.

[RaghuHR]

Hi @dhda 

Could you please share me the logs of both APs at the of the issue?That will really help us to pin point where the issue is. We have the logs from one of the APs,

Thanks,

Raghu

[dhda]

Hi Raghu,

Thanks for the very fast response.

https://1drv.ms/u/s!Ai4PEQfZRtEfgpBdw2aFW_R60PkPcg?e=wOqrp1 should have been the log of the other AP, from the same day as the other logfiles ?

Best Regards

[dhda]

Good morning, Raghu,

Could it be that the log files are not usefull to detect the issue (or the link to the logfiles doesn't work ?) ?

We can add the info, that the android and windows equipment connects smoothly to any AP (but both our WAX610).

Issue has to be found in the Netgear AP's themselves or should we also think about the modem/router from the provider ?

Maybe the issue, remaining at 0 clients untill rebooted, occurs a little more on the AP with IP 249.

Was wondering, why is there a scheduled reboot option !? Perhaps we are not the only ones, having this issue ?

Thanks for your response.

Best Regards,

Danny

[RaghuHR]

Hi @dhda 

While checking the logs that you sent  you have taken  the logs on may 26th with other AP and  and previous logs shared with may 25th. Because of this date mis match we can not find any clue. Could you please send the both APs logs at the time of the issue so that we can match with timestamps?

Thanks,

Raghu

[dhda]

I apologize, Raghu,

Since the other AP kept running, thought same time would still have been available in the logfile from may 26th but it seems limited in length.

Hope to get back to you soon, with fresh logfiles before reboot AP1/after reboot AP1/same period before and after reboot of AP2.

Best Regards,

Danny

[dhda]

Hi again Raghu,

Here's a link to a folder containing logfiles from AP.249 and AP.154 before rebooted AP.249 and the logfiles again afterwards.

There's a ReadMe.txt where the actions in time can be found.

Rebooted AP.249 around 16:21, mobile testequip was Android Phone MA 56:00:58 IP .101.

https://1drv.ms/u/s!Ai4PEQfZRtEfgpBgkgYJHFFuzhYpOQ?e=qjnkgy

PS. While finishing all this, 56:00:58 still remains at the poor AP.249, also after WiFi OFF/ON, although AP.154 is next to the phone.

So added the logs of both AP's once more.

Hope you can retrieve the logfiles in the shared folder.

I'm curious now...

Goodluck and thanks in advance.

Best Regards,

Danny

[dhda]

Hi Raghu,

Just wanted to listen if anything could be derived from the latest logfiles.

As everyday, today again the AP remained at 0 clients until rebooted and soon after the reboot, noticed 7 clients...

Best Regards,

Danny

[RaghuHR]

Hi @dhda 

We are reviewing your logs. We will update you soon our findings. Thanks for your patience.

Raghu.

[RaghuHR]

Hi @dhda  We need to have a live debug call. Please respond to my private message.

Thanks,

Raghu