cancel
Showing results for 
Search instead for 
Did you mean: 

Noticed oddity in TG582n Event Logs

Luzern
Hero
Posts: 4,823
Thanks: 872
Fixes: 9
Registered: ‎31-07-2007

Noticed oddity in TG582n Event Logs

I installed the router over the weekend, but there are entries in the log dated Jan 1
Quote
Recorded Events

Time Message

Sep 11 11:59:27 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)

Sep 11 11:09:11 SNTP Synchronised to server: 212.159.13.49

Sep 11 10:30:59 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)

Sep 11 10:09:11 SNTP Synchronised to server: 212.159.13.50

Sep 11 09:09:11 SNTP Synchronised again to server: 212.159.13.49

Sep 11 08:09:11 SNTP Synchronised again to server: 212.159.13.49

Sep 11 07:09:11 SNTP Synchronised to server: 212.159.13.49

Sep 11 06:09:11 SNTP Synchronised to server: 212.159.13.50

Sep 11 05:09:11 SNTP Synchronised to server: 212.159.6.9

Sep 11 04:09:11 SNTP Synchronised to server: 212.159.6.10

Sep 11 03:23:29 LOGOUT User admin logged out on TELNET (192.168.1.64)

Sep 11 03:23:28 LOGIN User admin logged in on TELNET (192.168.1.65)

Sep 11 03:09:11 SNTP Synchronised to server: 212.159.13.49

Sep 11 02:23:09 LOGIN User admin logged in on TELNET (192.168.1.64)

Sep 11 02:09:11 SNTP Synchronised to server: 212.159.6.10

Sep 11 01:09:11 SNTP Synchronised to server: 212.159.13.49

Sep 11 00:09:11 SNTP Synchronised to server: 212.159.6.9

Sep 10 23:38:59 LOGOUT User admin logged out on TELNET (192.168.1.64)

Sep 10 23:09:11 SNTP Synchronised to server: 212.159.13.50

Sep 10 22:09:11 SNTP Synchronised to server: 212.159.6.10

Sep 10 21:09:11 SNTP Synchronised to server: 212.159.13.49

Sep 10 20:09:11 SNTP Synchronised to server: 212.159.6.10

Sep 10 19:09:11 SNTP Synchronised to server: 212.159.6.9

Sep 10 18:09:11 SNTP Synchronised to server: 212.159.13.50

Sep 10 17:09:11 SNTP Synchronised again to server: 212.159.13.49

Sep 10 16:09:10 SNTP Synchronised to server: 212.159.13.49

Sep 10 15:09:10 SNTP Synchronised to server: 212.159.6.9

Sep 10 14:44:47 LOGIN User admin logged in on TELNET (192.168.1.64)

Sep 10 14:44:43 LOGOUT User admin logged out on TELNET (192.168.1.64)

Sep 10 14:09:10 SNTP Synchronised to server: 212.159.13.50

Sep 10 13:09:10 SNTP Synchronised again to server: 212.159.6.9

Sep 10 12:16:15 LOGIN User admin logged in on TELNET (192.168.1.64)

Sep 10 11:09:10 SNTP Synchronised to server: 212.159.6.9

Sep 10 11:09:10 SNTP Systemtime update: time setting 00:05:50 > new time setting: 11:09:10

Jan 1 00:02:56 CONFIGURATION saved by TR69

Jan 1 00:02:15 FIREWALL event (1 of 6): deleted rules

Jan 1 00:02:15 PPP link up (Internet) [91.125.154.210]

Jan 1 00:02:14 PPP CHAP Chap receive success : authentication ok

Jan 1 00:02:14 PPP CHAP Receive challenge (rhost = ptn-ag04)

Jan 1 00:02:13 PPP CHAP Receive challenge (rhost = bras-red5.bs)

Jan 1 00:02:10 xDSL linestate up (ITU-T G.992.5; downstream: 7843 kbit/s, upstream: 440 kbit/s; output Power Down: 18.9 dBm, Up: 12.8 dBm; line Attenuation Down: 47.5 dB, Up: 26.5 dB; snr Margin Down: 3.1 dB, Up: 23.2 dB)

Jan 1 00:01:44 xDSL linestate down

Jan 1 00:01:18 xDSL linestate down

Jan 1 00:01:02 [ANTI_SPOOFD] (err) llist_getobject_at for ENV.ANTI_SPOOFD's value failed

Jan 1 00:00:48 xDSL linestate down

Jan 1 00:00:38

This seems somewhat odd and I wonder why the entries are there with the unlikely date, and if theymight have an effect on the router in any way.
Could ny other thread somehow be related?
No one has to agree with my opinion, but in the time I have left a miracle would be nice.
3 REPLIES 3
w23
Pro
Posts: 6,347
Thanks: 96
Fixes: 4
Registered: ‎08-01-2008

Re: Noticed oddity in TG582n Event Logs

The router has no 'real time clock', when switched on it always thinks it's the 1st of Jan, once it contacts a time server it updates
Quote
Sep 10 11:09:10  SNTP Systemtime update: time setting 00:05:50 > new time setting: 11:09:10
Call me 'w23'
At any given moment in the universe many things happen. Coincidence is a matter of how close these events are in space, time and relationship.
Opinions expressed in forum posts are those of the poster, others may have different views.
James
Grafter
Posts: 21,036
Thanks: 5
Registered: ‎04-04-2007

Re: Noticed oddity in TG582n Event Logs

Looks like it defaults to 01/01 00:00 until it received a time update at which point the correct times and dates were used.
Luzern
Hero
Posts: 4,823
Thanks: 872
Fixes: 9
Registered: ‎31-07-2007

Re: Noticed oddity in TG582n Event Logs

Thanks both
No one has to agree with my opinion, but in the time I have left a miracle would be nice.