search

hdholm / ModemCheck

Simple python scripts to monitor a Netgear CM1150V Cable Modem. They may or may not work for other Netgear Cable Modems.
MIT License
4 stars 2 forks source link

Great fun #4

Open DrStephenCW opened 2 years ago

DrStephenCW commented 2 years ago

I have the exact same modem. I downloaded a copy and I have it working on Windows. There are a couple of "use before assignment" bugs - one of which I fixed.

The graph is beautiful!

Did you ever get your issues with Comcast fixed? I'll get regular 4 minute 20 second outages while the modem resync's. Usually these happen in the morning, but they can happen anytime.

hdholm commented 2 years ago

I haven't had routine outages that last that long. They've been doing work locally lately and I see the modem drop for a minute or two in the very early morning a lot of nights lately. Unfortunately the code I have here doesn't recognize (or always deal well with) outages that don't cause a modem reset. At some point I need to update the code to recognize when all errors have been reset to zero and/or the modem error log is reporting seeing "critical' errors. As for the windows errors, I obviously use it primarily from Unix. If I get a chance I might look into running it from windows, but work on this code is not high on my priority list. I'm happy to accept pull requests if you have fixes for problems.

DrStephenCW commented 1 year ago

Hello! Thank you for getting back to me and sorry for going dark. I got super busy!

Here is how things worked out with Comcast and me: once again, they sent out a person to check all the connectors. This time I watched him like a hawk. He simplified some things which was good. My internal MOCA started working again (not that I use it anymore but still...). I walked with the Comcast dude along the outside path of the wiring from their splitter to my home. I poked at a wire in the bushes and we found another connector nobody had seen before that was not waterproof and when the Comcast dude looked inside it he said "eew". After replacing that my system has been great. One effing connector caused years of outages.

As for the pull request, I've never done one, so I have to figure that out.

Finally, your information about how the modem resets after too many errors explains a lot. I think the Comcast modem does the same. It would explain why I would have a five minute outage while the modem reset and the timing would be pretty random. All those tiny errors add up to a modem reset. Not sure how that reset helps to be honest, since it was working decently, albeit with errors before that.

Anywho, thanks for the code and the information. I really appreciate it.

On Sun, Jun 26, 2022 at 3:15 PM Howard Holm @.***> wrote:

I haven't had routine outages that last that long. They've been doing work locally lately and I see the modem drop for a minute or two in the very early morning a lot of nights lately. Unfortunately the code I have here doesn't recognize (or always deal well with) outages that don't cause a modem reset. At some point I need to update the code to recognize when all errors have been reset to zero and/or the modem error log is reporting seeing "critical' errors. As for the windows errors, I obviously use it primarily from Unix. If I get a chance I might look into running it from windows, but work on this code is not high on my priority list. I'm happy to accept pull requests if you have fixes for problems.

— Reply to this email directly, view it on GitHub https://github.com/hdholm/ModemCheck/issues/4#issuecomment-1166660347, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCBF2GRYJWU2JXGJ3Z2HNTVRDI6LANCNFSM5ZOT7FQA . You are receiving this because you authored the thread.Message ID: @.***>