01-04-2021 06:39 PM
Oh I’m sure normally that would be the case, but I doubt there’s too much normal about the original issue at least.
As for the new router, it’s been fine as far as I can tell after that reboot. Only potential for interference near the router would be the roku streaming device, and that’s sitting a couple feet away on a lower level of the entertainment console.
The new router is in the same spot the old one was. Like I’ve said before, I’ve had long stretches of time where the old router operated perfectly fine (seemingly including right now with the new one post reboot), so I’m not inclined to believe it’s from interference. The signal strength on the neighbors wifi from our home is very low anyway.
Not to mention the fact that all devices, regardless of location, were unable to connect to the 2.4 ghz wifi network in the case of both router issues in the moments they occurred.
I can’t speak much for the new router just yet, but I assure you the issue with the old one was not caused by something with a normal solution. My gut says it was a hardware issue potentially solved with the new revision.
With the old router, when the issue occurred, it was as if the 2.4 ghz network no longer existed. When I had an issue with the new router today, the 2.4 ghz network existed, but devices couldn’t connect to it.
I’m inclined to believe these were two different issues, and that hopefully that problem with the new router was just a fluke. But we’ll see how it performs from here.
01-11-2021 12:16 PM
Lo and behold, the issue has returned. Just 15 minutes ago or so, I received a notification that my security cameras were not responding to remote requests. I check the router status, and once again, the 2.4 ghz wifi access point was the only one stated to be “Disconnected”. I checked to see if the roku was connected to wifi - it was not.
Our amazingly frustrating problem is back ladies and gents. Unfortunately, seeing as new hardware did not solve the problem, I can only assume this is being caused by a firmware bug that only Verizon can fix. And who knows how long that’ll take. None of the representatives I spoke with before seemed to have a clue what was going on anyway.
The old router went several months before this issue cropped up. This new router lasted what, a week? The only information I can glean from this is that this likely firmware bug is relatively new.
Hopefully someone at Verizon that works on the firmware ends up reading this. Until then, I’m heavily debating switching to a provider that doesn’t force me to deal with this headache on my own.
01-14-2021 10:56 PM
Just curious. Have you tried playing around with channels and moving the router off of automatic channel selection? Noisy or dense environments may have the router hopping all over the place, getting interference, and making devices unhappy. Start with channels 1, 6 and 11 first. Use the other channels only as a last resort, since they are overlapping. See if any of them have a positive effect on your network stability.
I would also start ruling out certain devices from your network. If the problem happens frequently enough to take note of which devices are chatting or connecting when the radio fails, that will be useful info. Could be a bad device, could be a driver issue in the FiOS router. Could be anything.
02-07-2021 02:20 PM
We have been struggling with the same issue for two months now. Even after 1.) replacing the router 2.) replacing the ONT 3.) disabling SON 4.) setting the router's 2.4 GHz to "compatibility mode" and allowing it to select whatever channel it wants, the 2.4 network will disconnect whenever. 5 GHz just keeps trucking along as if everything's fine, but of course, you have to reboot the router to get 2.4 GHz back.
I believe it's a firmware issue, too, because your problem sounds like my problem exactly. In short, it's madness, and we need this solved.
02-08-2021 02:37 PM
I think the best way to explain that it is most certainly a firmware issue lies in the fact that I have changed literally nothing in the time since my last post. I do not have the energy to exhaust any further needless hours diagnosing an issue I cannot solve anyway nor am being paid to solve.
The results? The issue occurred maybe once or twice a few days later, and then never again up to current day. For everyone else having this issue, I am sorry to say I have absolutely no clue why any of it is happening (or as of right now for some reason, not happening.)
But for the love of god, can someone at Verizon at least try to look for some bug in the software that could cause this behavior?