I am running Gargoyle (1.4.4) on a WRT54GL. The router has been operating well and I reboot it every day at 4am.
This morning my router was not usable. No clients could connect, no web interface, etc. I pulled the power to reset, same issue. At this point I noticed the power light was blinking which I assume means the firmware could not load. I pushed the SES button on the front of the router, and magically everything now works. While this is good news, I have some questions:
While searching, I am still not sure what the SES button cleared. The router configuration seems unchanged. What exactly did this do (I have attached no custom scripts to this button...everything is "stock").
When I do a logread, I see a no log entries between Dec 31 and Jan 22. This seems odd to me. Does this indicate a system health issue and any pointers to resolve?
Anything I should be concerned about (preventative work) or is this just in the "*it happens" category.
mix wrote:Don't the contents displayed by logread clear out every time you restart your router, which is apparently each day at 4 am for some reason?
Which would be fine, if I did not have those Dec 31 entries in the buffer (for a router that runs every day). I have cleared out the buffer and will monitor for awhile.
The bigger issue remains of why I had a problem to begin with, and why the SES button had an impact
mix wrote:Don't the contents displayed by logread clear out every time you restart your router, which is apparently each day at 4 am for some reason?
Which would be fine, if I did not have those Dec 31 entries in the buffer (for a router that runs every day). I have cleared out the buffer and will monitor for awhile.
...
It is possibly before it gets the date/Time through NTP.
mix wrote:Don't the contents displayed by logread clear out every time you restart your router, which is apparently each day at 4 am for some reason?
Which would be fine, if I did not have those Dec 31 entries in the buffer (for a router that runs every day). I have cleared out the buffer and will monitor for awhile.
...
It is possibly before it gets the date/Time through NTP.
Yes... and your timezone changes it to dec 31st, 2000
new in 1.4.5/1.5.2 wrote:Time initialized to be Jan 1st, 2001 instead of 1970 before NTP started, so timezone shift never puts it before unix epoch
