Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Noticed oddity in TG582n Event Logs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Noticed oddity in TG582n Event Logs
Noticed oddity in TG582n Event Logs
11-09-2012 12:14 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I installed the router over the weekend, but there are entries in the log dated Jan 1
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?
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.
Message 1 of 4
(2,905 Views)
3 REPLIES 3
Re: Noticed oddity in TG582n Event Logs
11-09-2012 12:22 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
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.
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.
Message 2 of 4
(814 Views)
Re: Noticed oddity in TG582n Event Logs
11-09-2012 12:23 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
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.
Message 3 of 4
(814 Views)
Re: Noticed oddity in TG582n Event Logs
11-09-2012 1:42 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Thanks both
No one has to agree with my opinion, but in the time I have left a miracle would be nice.
Message 4 of 4
(814 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Noticed oddity in TG582n Event Logs