NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBRE960 emailing logs has string buffer bug, doesn't send the whole log, doesn't list attacks, etc.
I was doing this on my RBR50 for the last 2.5 years: Every 3am, email me the log. That also resulted in the log getting reset, so every morning I would have a copy of the previous day's log in my ema...
I, also, have two old RBR50's sending me logs. They send "when the log is full", rather than at a specific time. While I agree that the product should do what it says it will do, I wonder as a diagnostic effort what would happen if your 960 is set to send logs when full. (I have also found it somewhat humorous that email settings fall under Security on the older Orbi, while logs fall under Administration. Same on the 960?)
Also, while there is a log setting for "Known DoS attacks and port scans" in the log settings, there is also a check box in the WAN Setup page to "Disable Port Scan and DoS Protection". Is there a similar setting on the 960? (Ah, yes. On page 62 of the user manual.)
I could not help but notice your 960 appears to be connecting to the Internet a lot. All those "internet Conected" followed by "Time Synchronized" entries. Since they all appear in the log, it is clear that the 960 did not reboot (which would clear the log).
Scheduled and on-demand E-Mailing of router logs has been an issue on Netgear products since some of the first AX capable devices.
I have the same issue on my 960 and have had the same issue in regards to this since day 1. Some days I get 1 line, some days I get 20 lines, and they are always from the earliest entry forward, except that the latest entry it decides to actual include in the mail on that run is listed last.
Some days the router logs clear after mailing, some days they do not. It's all a crapshoot.
I hate to say this, but if nothing else, I am brutally honest. Do not expect consistent and complete router logs through the automated mailing process - at least for now. Hopefully it is something being worked on, and will be corrected in a future firmware update.