- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Does Router Return "Unavailable" to sender with each "DoS attack" log?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I turned on my PC and immediately got a series of DoS attack log entries.
Does each entry in the log mean that the router has returned a message for each log entry that the network is unavailable for some message similar?
[DoS attack: ACK Scan] from source 34.149.211.227,port 443 Wednesday, Feb 23, 2022 07:33:43
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 07:31:36
[DoS attack: snmpQueryDrop] from source 34.77.162.13,port 57789 Wednesday, Feb 23, 2022 07:22:00
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 07:18:15
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 07:11:14
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 06:57:14
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 06:46:31
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 06:35:14
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 06:22:31
[DoS attack: ACK Scan] from source 205.185.216.42,port 443 Wednesday, Feb 23, 2022 06:08:58
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 06:06:34
[DoS attack: RST Scan] from source 168.90.208.68,port 37168 Wednesday, Feb 23, 2022 05:59:46
[DoS attack: RST Scan] from source 44.241.40.79,port 443 Wednesday, Feb 23, 2022 05:54:56
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 05:53:51
[DoS attack: ACK Scan] from source 34.149.211.227,port 443 Wednesday, Feb 23, 2022 05:48:32
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 05:37:54
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 05:25:11
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 05:09:15
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:05:05
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:05:04
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:05:03
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:59
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:58
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:54
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:53
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:52
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:51
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:50
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:49
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:45
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:44
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:43
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:42
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:41
[DoS attack: TCP SYN Flood] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:40
[DoS attack: snmpQueryDrop] from source 104.152.52.180,port 41471 Wednesday, Feb 23, 2022 05:04:32
[DoS attack: snmpQueryDrop] from source 192.241.206.177,port 37819 Wednesday, Feb 23, 2022 05:00:54
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 04:56:32
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 04:40:36
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 04:30:35
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 04:18:19
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 04:06:34
[DoS attack: ACK Scan] from source 34.149.211.227,port 443 Wednesday, Feb 23, 2022 04:03:43
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 03:54:33
[DoS attack: RST Scan] from source 54.148.137.175,port 443 Wednesday, Feb 23, 2022 03:52:40
[DoS attack: RST Scan] from source 54.148.137.175,port 443 Wednesday, Feb 23, 2022 03:51:07
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 03:43:16
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 03:26:08
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 03:14:36
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 03:00:54
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 02:47:56
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 02:36:23
[DoS attack: ACK Scan] from source 34.149.211.227,port 443 Wednesday, Feb 23, 2022 02:29:14
[DoS attack: snmpQueryDrop] from source 204.42.253.130,port 49502 Wednesday, Feb 23, 2022 02:26:46
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 02:19:16
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 02:07:43
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 01:54:56
[DoS attack: ACK Scan] from source 35.244.184.98,port 443 Wednesday, Feb 23, 2022 01:54:16
[DoS attack: RST Scan] from source 99.84.224.120,port 443 Wednesday, Feb 23, 2022 01:52:20
[DoS attack: RST Scan] from source 35.155.16.166,port 443 Wednesday, Feb 23, 2022 01:49:22
[DoS attack: RST Scan] from source 35.155.16.166,port 443 Wednesday, Feb 23, 2022 01:49:21
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 01:38:50
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 01:19:44
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 01:00:38
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 00:48:53
[DoS attack: ACK Scan] from source 34.149.211.227,port 443 Wednesday, Feb 23, 2022 00:40:29
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 00:37:08
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 00:25:23
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 00:13:38
[DoS attack: Fraggle Attack] from source 10.72.120.1,port 67 Wednesday, Feb 23, 2022 00:03:30
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No. It is blocking the "attacks". It doesn't return anything but sends a DROP in its firewall and logs an entry
NETGEAR's DoS protection is famously know for many, many false positives. Some can even come from your ISP or your own devices on LAN/WiFi. Always look up the IP address it reports to see if it's legitimate or not. If you have problems, disable DoS "protection" clompletely (you're not losing much at all) to relieve the router. If you want to keep it on, at least disable the logging of these "attacks"
PS: I run 4 years without this faulty DoS "protection" and never had any issues
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No. It is blocking the "attacks". It doesn't return anything but sends a DROP in its firewall and logs an entry
NETGEAR's DoS protection is famously know for many, many false positives. Some can even come from your ISP or your own devices on LAN/WiFi. Always look up the IP address it reports to see if it's legitimate or not. If you have problems, disable DoS "protection" clompletely (you're not losing much at all) to relieve the router. If you want to keep it on, at least disable the logging of these "attacks"
PS: I run 4 years without this faulty DoS "protection" and never had any issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Does Router Return "Unavailable" to sender with each "DoS attack" log?
Understood. Thanks for clarifying.
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more