NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CrimpOn
Nov 01, 2018Guru - Experienced User
Change in Sending Log Files
Just noticed another change in the way Orbi handles log files. In the past, when a log filled, the Orbi would email it out, clear the log file, and start over. Now, the Orbi sends the log file every day at midnight and does not clear the log. What was once a continuous record has become multiple duplicates as the same DHCP entries get mailed day after day.
Does anyone know of a way to restore the previous behavior?
25 Replies
- FURRYe38Guru - Experienced User
- Christian_RNETGEAR Employee Retired
Hello CrimpOn - Thank you for reaching out. Have you made any recent changes? What FW version are you on?
~Christian
- ekhalilMaster
CrimpOn wrote:
Just noticed another change in the way Orbi handles log files. In the past, when a log filled, the Orbi would email it out, clear the log file, and start over. Now, the Orbi sends the log file every day at midnight and does not clear the log. What was once a continuous record has become multiple duplicates as the same DHCP entries get mailed day after day.
Does anyone know of a way to restore the previous behavior?
You can select how the logs be sent to you. Under >>Advanced >> Security >> E-Mail , you can select if the logs should be sent to you when full or daily, weekly, ... at a specific time. See attached snapshot:
- CrimpOnGuru - Experienced User
Thanks for the tip. I looked at Advanced->Security->EMail, and this is what it shows:
i.e. That's what I set it to months ago, and it's still set that way. Only the behavior has changed. My firmware is V2.2.1.210
I will set it to something else, and then set it back. Will be interesting to see tomorrow morning if I get an email (or not).
- Christian_RNETGEAR Employee Retired
CrimpOn - Thank you for getting back. Please let us know the outcome and if you require further assistance. I can see if we can get support to contact you.
~Christian
- FURRYe38Guru - Experienced User
- CrimpOnGuru - Experienced User
Just thought I'd mention....... I understand completely that "reset to factory and configure from scratch" is the solution of (next to last) resort. Some bit in there is corrupted and tinkering with settings simply never clears it. However, that's a lot like the advice to "wipe your hard drive, reinstall Windows from CD, reinstall all your apps, reconfigure everything....." and see if that helped. i.e. resetting to factory involves a considerable effort. (inputting IP reservations, setting device names, setting up log email, etc. etc. etc.) If my Orbi "didn't work", I would be all over this. Mine works. It updates firmware automatically. Performance is great. I just think the log file handling is messed up. I checked ALL the boxes, but the log shows only DHCP assignments. I asked to send the log "when full", but it sends every day.
p.s. "Last resort" seems to be to manually downgrade to earlier firmware and jump through hoops to keep the Orbi from updating itself. No chance of that by me!
- CrimpOnGuru - Experienced User
Well, gone completely wack-o now. This morning I thought, "hey, did I miss getting my daily log file?" In Advanced->Admin->Logs, this is what I see:
[admin login] from source 192.168.1.2, Monday, November 05, 2018 10:23:37
[Time synchronized with NTP server] Saturday, November 03, 2018 10:35:58
[admin login] from source 192.168.1.2, Friday, November 02, 2018 18:47:58
[admin login failure] from source 192.168.1.2, Friday, November 02, 2018 10:37:21
[Time synchronized with NTP server] Friday, November 02, 2018 10:35:56
[admin login] from source 192.168.1.2, Friday, November 02, 2018 10:34:54
[Initialized, firmware version: V2.2.1.210] Friday, November 02, 2018 10:34:38i.e. Between Friday and Monday, the ONLY thing logged was NTP sync and admin logins. NO DHCP leases. Nothing! I guess it's a good thing that it no longer sends a log every midnight, but this is just weird. All the possible boxes remain checked:
- Retired_Member
Having the same identical issues with logging since upgrade to v2.2.1.210 from v2.1.4.16. Factory Reset made no difference.