05-31-2020 12:27 PM
We are suffering from a similar issue. Could be the same root cause. Quantum gateway firmware version 02.02.00.16, hardware version 1.03.
Symptoms: router internet connection indicator light goes red at random. It then blinks white before going steady. No specific time of day AFAIK. While this happens, all internet connections drop. This is especially painful during group/meeting calls and you start talking. Everyone loses you for ~15 seconds.
I've been on the phone with FIOS support for about a month now. They first reconfigured the router. Then they suggested speed upgrade from 100Mbps to 1G. Does not make sense to me because the problem happens even in the dead of night when there is no usage at all.
Moved the router across the house to be close to ONT now going through ~20ft coax. Same issue.
Suspected the ONT power adapter. Removed the surge protect sitting between power outlet and the power adapter. No dice.
Now sitting in front of the router and trying to correlate the connection drop with logs.
Looked at System Logs. Saw frequent DHCP process reboots sometimes even within 15 seconds of each other. Called support again and they said it is normal and is done to "prevent hackers". Hmm. Really?
Now looking at Advanced Log. Seeing a repeated pattern right around the connection drop. Pasted the logs here if someone wants to take a look: https://pastebin.com/Rx1GKtAq
The connection loss log cycle starts with the following message which is followed by two address lookup failures. It looks like something is calling removeDefaultGateway(). Why would default gateway be removed? Upstream connection loss? Customer support doesn't see any core alarms in ONT.
May 31 17:40:10 2020 user.err<11> bhr4: System: virtual void GreenWave::NlUtils::removeDefaultGateway(const string&, const GreenWave::IPv4&) const - ioctl failure - 3: No such process
Did the uPnP change fix this problem?
06-30-2020 09:42 AM
for what it's worth, I've posted a couple of things in DSLreports forum that may be helpful as I've been chasing this too. I see some of the same error messages I was seeing, and I figured out a fix for at least one of them:
You may want to check and see if you have the same symptoms before reboot too.