NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear C7000 Nighthawk Modem/Router Combo losing connection
I recently looked into logs and event logs and maybe have found the issue but I don't know how to resolve them. I'm in need of help and what i can do to fix it. My product is out of warranty a...
Logs: (goes on and on but had to resize due to restrictions
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:51:15 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Tue Nov 15 17:51:12 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 3 | Tue Nov 15 17:51:08 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:50:37 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 2 | Tue Nov 15 17:50:36 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Tue Nov 15 17:49:49 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 2 | Tue Nov 15 17:49:02 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 17:47:49 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:33:46 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 2 | Tue Nov 15 17:32:57 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:31:41 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:26:00 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Tue Nov 15 17:25:30 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:24:55 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 17:09:39 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 7 | Tue Nov 15 17:07:10 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 2 | Tue Nov 15 16:57:04 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 5 | Tue Nov 15 16:55:53 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:49:15 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 8 | Tue Nov 15 16:49:08 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:46:34 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 3 | Tue Nov 15 16:46:34 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:45:43 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:45:43 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:45:43 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:45:43 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:45:42 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 5 | Tue Nov 15 16:45:42 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 2 | Tue Nov 15 16:45:41 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 2 | Tue Nov 15 16:45:41 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 16:45:02 2016 | 73.75.242.34:0 | 130.0.3.176:0 |
| [DHCP IP: 192.168.0.14] to MAC address a4:b8:05:67:73:12 | 1 | Tue Nov 15 16:39:41 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DHCP IP: 192.168.0.17] to MAC address 88:71:e5:a6:e5:63 | 1 | Tue Nov 15 07:56:03 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:43 | 1 | Tue Nov 15 05:26:14 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 3 | Tue Nov 15 05:25:10 2016 | 120.234.61.162:0 | 130.0.3.176:0 |
| [DHCP IP: 192.168.0.15] to MAC address 5c:dc:96:ba:7d:46 | 1 | Tue Nov 15 04:19:57 2016 | 0.0.0.0:0 | 0.0.0.0:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 1 | Tue Nov 15 01:21:45 2016 | 120.234.61.162:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 1 | Tue Nov 15 00:51:59 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Tue Nov 15 00:09:04 2016 | 120.234.61.162:0 | 130.0.3.176:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Mon Nov 14 22:02:44 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Mon Nov 14 22:02:43 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 2 | Mon Nov 14 22:02:43 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
| [DoS attack: Illegal Fragments] from 130.0.3.176, port 0 | 1 | Mon Nov 14 22:02:43 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
| [DoS attack: Teardrop or derivative] from 130.0.3.176, port 0 | 1 | Mon Nov 14 22:02:43 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
| [DoS attack: Ping Of Death] from 130.0.3.176, port 0 | 1 | Mon Nov 14 22:02:43 2016 | 64.48.155.244:0 | 130.0.3.176:0 |
Hello BossinSauce
Sometimes DOS attacks are not always a DOS attack it could be some site you use or program you use that looks like a DOS attack you would have to look up the 130.0.3.176 address and find where it is coming from to see if its bad or not.
DarrenM