NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Various DoS attacks in log, what do?
The following events I have found in the log of my newly installed router. There appear to be several different types of DoS attacks listed. This goes on for days (installed saturday, log looks like ...
Your reply confuses me. I'm experiencing the same thing, from a different local IP (10.128.200.1), which doesn't exist in my network.
It makes sense to look at an IP that wouldn't be a "10.x.x.x ", as it may show an actual DoS attacker, but HOW DOES a local IP appear on these log entries??
Also, you say, Netgear may be logging 'false positives' (that is it's log entry is NOT due to a true DoS attempt).
So, you suggest turning off DoS to save router stress, aren't these log entries being triggered by "something?".....which would continue, would add stress to the router, and be undetected by us?
Thanks in advance for a reply
AZAX_user wrote:
Also, you say, Netgear may be logging 'false positives' (that is it's log entry is NOT due to a true DoS attempt).
This is a constant refrain.
Netgear's firmware is great at creating false reports of DoS attacks. Many of them are no such thing.
Search - NETGEAR Communities – DoS attacks
Use Whois.net to see who is behind some of them and you may find that they are from places like Facebook, Google, even your ISP.
Here is a useful tool for that task:
IPNetInfo: Retrieve IP Address Information from WHOIS servers
If these events are slowing down your router, that may be because it is using up processor time as it writes the events to your logs. Anything that uses processor power – event logging, QoS management, traffic metering – may cause slowdowns. Disable logging of DoS attacks and see if that reduces the problem. This does not prevent the router from protecting you from the outside world.
By the way, you have joined in on an existing conversation that may or may not have anything to do with your problems.
There is also a good chance that the official support team is busily monitoring new conversations and may miss your addition to this one.
If you do want help with your problem, check previous stuff that may be related then start your own discussion.