@SOHO I would love to hear if you ever get a resolution to this problem. I am also curious to hear if others have been silently having these issues, and/or if support and engineering are already aware of these lockups and reboots, and working on a fix for the next release.
With 7.1 we’ve had occasional lockups exactly like yours, and since we went on to 7.1.1 the router has been going down like clockwork every 4d10h ±6h, it never misses its schedule.
When I say it goes down, it does one of three things:
- Reboots by itself (that is the best case scenario, because it self recovers),
- The AP fails, and all WIFI devices loose access to the internet but remain connected to the router, and wired devices stay connected to the internet,
- The AP fails, and all WIFI devices loose access to the internet but remain connected to the router, and wired devices also loose access to the internet.
In case 2, logging in via a wired device shows no traces in the event log, so no hints there. In case 3, can’t access the router from any device. For cases 2 and 3, a manual reboot is required (power cycle). With 7.1 only had case 3 randomly, sometimes within a day of a reboot and sometimes weeks after…
On 7.1.1 it looks awfully like a memory leak of some kind given how regular it is.
We have been able to get by with a daily reboot, but if this is ever understood it would be great so that we can get rid of those daily reboots.
We have tried many things such as removing the cell backup link, using less WIFI SSIDs, less VLANs, in case it was a memory leak of some sort or the SOHO was just doing too many things, but none of this solved the problem or changed the frequency of events… So the daily reboot is the only prevention at this point… sad and mysterious…
I am not opening a ticket because we have a workaround and I don’t have time to follow up these days. Also because the diagnostics report they will want includes the passwords for our networks, certs, machine names, etc… (see this topic), and this is against company policies and I really don’t have time to reset everything on our network (and get a new cert) after sharing this critical information.
Anyhow, I am curious to hear what others have experienced. And indeed, if there are some internal stats or logs we can access, to get a better understanding of these events on our own, it would be great.