NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

ninja661's avatar
ninja661
Luminary
Sep 06, 2026

Router log alert messages

I would be so appreciative if Netgear would in it's user guides would include a section on log file messages generated by the router and what they mean.  I have been trying to decipher these strange messages (ACK and RST mean absolutely NIL) and alert types for the most part I understand what a scan is but the terminology they use is confusing.  Just a simple request as they don't include anything in the router help or the user guide.  So, if you could please let us know and then maybe we might know what's going on out there.

 

Thanks!!!

2 Replies

  • There have been many conversations on the Forum about messages in Netgear router logs.  It is important to understand that these log entries are produced by code that Netgear includes in the firmware which seeks to discover patterns in connection attempts.  I say "attempts" because Netgear routers do not accept connection attempts unless the user has specifically set the router to do so. (For example, by forwarding specific ports to devices on the LAN, by enabling automatic UpNP, by activating the OpenVPN Host feature, etc.)  Those log entries SCREAMING OUT  ATTACK!!!  Are equivalent to having your home phone issue an ALERT any time there is a crank phone call, or someone screaming out ALERT any time there is junk mail in the mailbox.

     

    There is nothing anyone can do to prevent some device on the internet from attempting to connect to your public IP address. (Just like you cannot prevent anyone from dialing your phone number or sending mail to your home street address.)

     

    While Netgear does not publish information about how it determines that some sequence of connection attempts match a pattern, it is almost trivial to search the internet for explanations of the various types of "attacks".

  • I completely agree. A simple explanation of common router log messages like ACK, RST, scans, and other alerts would make troubleshooting much easier. Clear documentation for these logs would be a very useful addition to the user guide.