YazFi YazFi - All Clients Disconnect

[Gary_Dexter]

I have a recurring issue whereby clients connected to YazFi all disconnect and have no internet access.

Devices are not listed as connected on the YazFi status page, shows no clients connected - the SSID is still broadcasting but new (or existing) devices cannot connect to it.

The only way to get devices to connect again is to either reboot the router in its entirety, or, on the YazFi page, click the Apply button at the bottom of the page to “reload” it again and devices then auto-connect back.

These are IOT devices so only the 2.4Ghz band is being used on Slot 2.

Is there anything to look for in the logs or any commands to run when this happens to see what the issue is?

Worth noting - devices connected to the “normal” Wi-Fi on either band continue to work and are not affected, likewise Ethernet connected devices are also OK.

 

[bennor]

What is "slot 2"? Is that Guest Network #2?
What firmware are you running?
What other scripts are you running?
Are you using AiMesh?
What do the system logs show around the time you start experiencing the issue?
One can generate a YazFi Diagnostic file via the YazFi CLI, option "d". See Jack Yaz's post at the following link for how to decrypt that log file so you can read it:
https://www.snbforums.com/threads/how-do-you-access-a-yazfi-diagnostic-file.78279/#post-755294

 

[Gary_Dexter]

What is "slot 2"? Is that Guest Network #2?
What firmware are you running?
What other scripts are you running?
Are you using AiMesh?
What do the system logs show around the time you start experiencing the issue?
One can generate a YazFi Diagnostic file via the YazFi CLI, option "d". See Jack Yaz's post at the following link for how to decrypt that log file so you can read it:
https://www.snbforums.com/threads/how-do-you-access-a-yazfi-diagnostic-file.78279/#post-755294

Yes, Guest Network #2.

Firmware is 386.11 running on a GT-AC2900.

Only other scripts are Skynet and scMerlin.

No AiMesh.

I don’t recall seeing anything in the System Logs other than the devices being disconnected (the normal wlceventd device disassociated message).

I’ll run a diagnostic the next time it happens - it’s not consistent and could go for days/weeks before happening again.