[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-list
Subject:    OT: Ways to figure what causing High Ping Loss that require power cycling cable modem??
From:       "Michael D. Setzer II via users" <users () lists ! fedoraproject ! org>
Date:       2023-07-09 11:50:13
Message-ID: 64AA9EF5.26252.70F8A7E () mikes ! guam ! net
[Download RAW message or body]

Island got hit with a Typhoon Cat 3/Cat 4 that caused lots of 
damage to all internet providers. Power at house was out for a 
week. They are still working on lots of issues.

Can figure when issue happens, and power cycle on cable modem 
fixes it. Wonder if there might be some process to find way to 
prevent it from happening or way to have script software reset 
modem. Years ago had way to reboot Surfboard modem, but now 
ISP using Arriss cable modems. Web access has no reboot option?
Thanks.


Usually would only need to reboot cable modem about once a 
month, but over last 6 days, have required reboots average of 7.5 
times a day? 45 total. Similar patterns for prior weeks.

Have script that does 50 pings to local name server, and most of 
time is 0, with some values from 1% to 10%, but often jumps to 
high rates over 80% to 100%. At which point the internet is 
useless. All lights on modem are fine, TV, phone, and 4 Linux 
machines all will report no internet. Traceroute to 8.8.8.8 still 
works, but when no loss takes total of 1.3 seconds

While getting high loss using -n the time goes to 5.6 seconds, and 
without -n takes 2 minutes 13 seconds?
Hops change of three test changes from 10, 14, and 13.

Summary of time.
Up Time		Hours		Days	
129:29:28		129.4911		5.40	90.76%
Down Time	Hours		Days	
13:15:54		13.2650		0.55	9.24%

Script plays sound when ping rate over 10%, and reset brings 
everything back to normal. But for how long before it returns has 
no pattern that I can find. On some cases if not around to power 
cycle it, it will start working again, but rare. Usually, only power 
cycle fixes it.

ARRIS DOCSIS 3.1 / PacketCable 1.5 Touchstone Telephony 
Modem
HW_REV: 8
VENDOR: ARRIS Group, Inc.
BOOTR: 2.2.23.635901
SW_REV: 11.02.032.09.03.NCS
MODEL: TM3402A

Haven't found a way to send software reboot to modem, so only 
physical power cycle works. Seems company was bought by 
another and info from web site has been useless. 

Looked at netstat and nstat info before and after outages, but don't 
see anything from the linux side that shows what issue is.

Get the 50+M speedtest results when working.
Example of a cycle.
Time and percentage of ping loss
2023-07-09 06:27:00	88
2023-07-09 06:30:00	76
2023-07-09 06:33:00	84
2023-07-09 06:36:00	84
2023-07-09 06:39:00	82
2023-07-09 06:42:00	78
2023-07-09 06:44:00	78
2023-07-09 06:47:00	84
2023-07-09 06:50:00	90
2023-07-09 06:53:00	82
2023-07-09 06:56:00	82
2023-07-09 06:59:00	92
2023-07-09 07:01:00	72
2023-07-09 07:04:00	82
2023-07-09 07:07:00	82
2023-07-09 07:10:00	80
Power Cycle modem makes access to 192.168.100.1 fail till about 
3 to 4  minute reboot time.
2023-07-09 07:12:00	100	Cable Modem not accessible
Reports when ping rate goes back to normal.
2023-07-09 07:16:00	0	UP


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:mikes@guam.net                            
 mailto:msetzerii@gmail.com
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+


_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[prev in list] [next in list] [prev in thread] [next in thread]