Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[partach1]

This new firmware version (beta 9) seems to decide to do some sort of soft reset from time to time.
Anyone else observed this?
I have observed from the alive counter that there were 4 'reboots'. This is what it looks like as the alive timer was reset in all those cases.
On average after about a day (1 time the router lasted for several days)
The log pretty much (this new version does not completely loose the logs after automated reset?) tells the same story:

[INFO]   Tue Nov 24 08:14:38 2009   Wireless restart
[INFO]   Tue Nov 24 07:01:31 2009   Time synchronized
<------------------- after trying to synchorinse NTP it seems to go wrong -------->
[INFO]   Fri Nov 20 19:12:32 2009   Requesting time from 207.232.83.70
[INFO]   Fri Nov 20 19:11:35 2009   Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO]   Fri Nov 20 19:11:32 2009   Time synchronization failed (status 2)
[INFO]   Fri Nov 20 19:11:30 2009   Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO]   Fri Nov 20 19:11:29 2009   Requesting time from 207.232.83.70
[INFO]   Fri Nov 20 19:11:29 2009   Time server ntp1.dlink.com is at IP address 207.232.83.70

After requesting time the router does not log anything anymore. This was the kind of break point all four times. This could suggest NTP problems still (also observed in previous firmware)

According the current alive time (log above is fresh) the system was operational for about 10 hours meaning that the entry at about 7:00 am is the first one.
The logs tell me it was not a full reboot as the standard intialisation stuff does not apear at 7:00 ish in the log. Or?
Who can explain this?

[Lycan]

How about a syslog? I'd like to see the log entries before the unit reboots.

[partach1]

I will set a syslog server up today.
It seems pretty reproducible anyhow.

this morning it rebooted again. Here is the entire internal log (filtered out firewall & security, rest is on):
Priority   Time   Message
[INFO]   Wed Nov 25 09:15:05 2009   Allowed configuration authentication by IP address 192.168.1.197
[WARN]   Wed Nov 25 09:12:38 2009   A network computer (Name) was assigned the IP address of 192.168.1.197.
[INFO]   Wed Nov 25 09:12:36 2009   Dlinkrouter: Wireless system with MAC address xxxxxxxxxxxx secured and linked
[INFO]   Wed Nov 25 09:12:36 2009   Dlinkrouter: Wireless system with MAC address xxxxxxxxxxxx associated
[INFO]   Wed Nov 25 09:12:36 2009   Above message repeated 1 times
[INFO]   Wed Nov 25 07:00:37 2009   Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO]   Wed Nov 25 07:00:33 2009   Above message repeated 1 times
[INFO]   Wed Nov 25 07:00:33 2009   Time synchronized
[INFO]   Fri Nov 20 19:11:31 2009   Requesting time from 207.232.83.70
[INFO]   Fri Nov 20 19:11:31 2009   Time server ntp1.dlink.com is at IP address 207.232.83.70
[INFO]   Fri Nov 20 19:11:25 2009   WAN interface speed measurement completed. Upstream speed is 99862 kbps
[INFO]   Fri Nov 20 19:11:22 2009   Wireless link is up
[INFO]   Fri Nov 20 19:11:17 2009   Starting DHCP server
[INFO]   Fri Nov 20 19:11:10 2009   Estimating speed of WAN interface
[INFO]   Fri Nov 20 19:11:10 2009   Bringing up WAN using Static IP Address
[INFO]   Fri Nov 20 19:11:10 2009   WAN interface cable has been connected
[INFO]   Fri Nov 20 19:11:10 2009   LAN interface is up
[INFO]   Fri Nov 20 19:11:10 2009   LAN Ethernet Carrier Detected
[INFO]   Fri Nov 20 19:11:09 2009   Device initialized
[WARN]   Fri Nov 20 19:11:08 2009   Wireless schedule init
[INFO]   Fri Nov 20 19:11:08 2009   No Internet access policy is in effect. Unrestricted Internet access

allowed to everyone

It seems a complete reboot and the shift in time stamps of a couple of days is due to the fact it takes a while to get NTP data? So after a reboot it lost all track of previous time? So how does this work if i turn of NTP? how does it get back the previous set time? is it stored in NVM somewhere?

Would be good to have some understanding of how time is managed on the router (NTP vs fixed) to figure out what it does or should do. Time is an important variable used in the router also regarding schedules. And I have some idea that the reboot is happening when the wireless schedule is about to turn wireless back on

I turned of securespot yesterday, it seems it has no effect on the symptom

[partach1]

Syslog server is running. Hoping to get results tomorrow...

[bluenote]

Nice detailed info.
Is it always "time synchronized" before the reboot and log gap?

If so, if you disable NTP, does this behaviour stop?

You are using the standard NTP dlink server right?

Cory

[partach1]

Nice detailed info.
Is it always "time synchronized" before the reboot and log gap?

If so, if you disable NTP, does this behaviour stop?

You are using the standard NTP dlink server right?

Cory

Did not have time yet to check if the router failed last night. Will do that tonight.
in the log you can see i used the standard dlink NTP server: ntp1.dlink.com
I first want to reproduce the problem and supply the logs to dlink. After that I can make changes, like not using NTP, to see what will happen.

[partach1]

Ok it happende again. The Connection Up Time :  0 Day 10 Hour 54 Min 23 Sec .
So exactly at 7:00 there should have been a restart

The log by syslog (other way round than standard log)
Nov 26 01:00:01 192.168.1.250 Thu Nov 26 01:00:04 2009 paco System Log: : Wireless schedule stop
Nov 26 01:00:01 192.168.1.250 Thu Nov 26 01:00:04 2009 paco System Log: Disconnect all stations
Nov 26 01:00:01 192.168.1.250 Thu Nov 26 01:00:04 2009 paco System Log: Wireless restart
Nov 26 01:00:01 192.168.1.250 Thu Nov 26 01:00:04 2009 paco System Log: Wireless link is down
Nov 26 07:00:00 192.168.1.250 Thu Nov 26 07:00:04 2009 paco System Log: : Wireless schedule start
Nov 26 07:00:00 192.168.1.250 Thu Nov 26 07:00:04 2009 paco System Log: Wireless link is down
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:08 2009 paco System Log: Wireless schedule init
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:09 2009 paco System Log: Device initialized
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:10 2009 paco System Log: LAN Ethernet Carrier Detected
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:10 2009 paco System Log: LAN interface is up
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:10 2009 paco System Log: WAN interface cable has been connected
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:10 2009 paco System Log: Bringing up WAN using Static IP Address
Nov 26 07:00:17 192.168.1.250 Fri Nov 20 19:11:10 2009 paco System Log: Estimating speed of WAN interface
Nov 26 07:00:24 192.168.1.250 Fri Nov 20 19:11:17 2009 paco System Log: Starting DHCP server
Nov 26 07:00:29 192.168.1.250 Fri Nov 20 19:11:22 2009 paco System Log: Wireless link is up
Nov 26 07:00:54 192.168.1.250 Fri Nov 20 19:11:47 2009 paco System Log: WAN interface speed measurement completed.  Upstream speed is 77369 kbps
Nov 26 07:01:00 192.168.1.250 Fri Nov 20 19:11:53 2009 paco System Log: Time server ntp1.dlink.com is at IP address 207.232.83.70
Nov 26 07:01:00 192.168.1.250 Fri Nov 20 19:11:53 2009 paco System Log: Requesting time from 207.232.83.70
Nov 26 07:01:00 192.168.1.250 Thu Nov 26 07:00:59 2009 paco System Log: Time synchronized
Nov 26 07:01:00 192.168.1.250 Thu Nov 26 07:00:59 2009 paco System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Nov 26 07:01:03 192.168.1.250 Thu Nov 26 07:01:03 2009 paco System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Nov 26 08:54:53 192.168.1.250 Thu Nov 26 08:54:53 2009 paco System Log: A network computer (xxxxxxxxxx) was assigned the IP address of 192.168.1.199.
Nov 26 08:54:58 192.168.1.250 Thu Nov 26 08:54:58 2009 paco System Log: A network computer (lin1) was assigned the IP address of 192.168.1.198.
Nov 26 08:55:16 192.168.1.250 Thu Nov 26 08:55:16 2009 paco System Log: A network computer (lin1) was assigned the IP address of 192.168.1.198.
Nov 26 10:38:58 192.168.1.250 Thu Nov 26 10:38:58 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx associated
Nov 26 10:38:58 192.168.1.250 Thu Nov 26 10:38:58 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx associated
Nov 26 10:38:58 192.168.1.250 Thu Nov 26 10:38:58 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx secured and linked
Nov 26 10:38:59 192.168.1.250 Thu Nov 26 10:38:59 2009 paco System Log: A network computer name) was assigned the IP address of 192.168.1.196.
Nov 26 10:39:04 192.168.1.250 Thu Nov 26 10:39:04 2009 paco System Log: A network computer (name) was assigned the IP address of 192.168.1.197.
Nov 26 12:22:39 192.168.1.250 Thu Nov 26 12:22:38 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx disconnected for reason: Received Deauthentication
Nov 26 17:21:59 192.168.1.250 Thu Nov 26 17:21:59 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx associated
Nov 26 17:21:59 192.168.1.250 Thu Nov 26 17:21:59 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx associated
Nov 26 17:21:59 192.168.1.250 Thu Nov 26 17:21:59 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxx secured and linked
Nov 26 17:22:06 192.168.1.250 Thu Nov 26 17:22:06 2009 paco System Log: A network computer (name) was assigned the IP address of 192.168.1.197.
Nov 26 17:48:32 192.168.1.250 Thu Nov 26 17:48:32 2009 paco System Log: Allowed configuration authentication by IP address 192.168.1.197
Nov 26 17:51:06 192.168.1.250 Thu Nov 26 17:51:06 2009 paco System Log: Log viewed by IP address 192.168.1.197

no reset visible in this one? So did it reboot or not? according the alive timer it did AND the normal log of the device itself it did as well (or?) post after this is the log via the router web interface of today.

[partach1]

the log via the web interface. WHICH IS DIFFERENT FROM THE SYSLOG ??

[INFO]   Thu Nov 26 18:00:10 2009   Administrator logout
[INFO]   Thu Nov 26 17:51:06 2009   Log viewed by IP address 192.168.1.197
[INFO]   Thu Nov 26 17:48:32 2009   Allowed configuration authentication by IP address 192.168.1.197
[WARN]   Thu Nov 26 17:22:06 2009   A network computer (Ruk1) was assigned the IP address of 192.168.1.197.
[INFO]   Thu Nov 26 17:21:59 2009   paco: Wireless system with MAC address xxxxxxxxxx secured and linked
[INFO]   Thu Nov 26 17:21:59 2009   paco: Wireless system with MAC address xxxxxxxxxx associated
[INFO]   Thu Nov 26 17:21:59 2009   Above message repeated 1 times
[INFO]   Thu Nov 26 12:22:38 2009   paco: Wireless system with MAC address xxxxxxxxxx disconnected for reason: Received Deauthentication
[WARN]   Thu Nov 26 10:39:04 2009   A network computer (name) was assigned the IP address of 192.168.1.197.
[WARN]   Thu Nov 26 10:38:59 2009   A network computer (name) was assigned the IP address of 192.168.1.196.
[INFO]   Thu Nov 26 10:38:58 2009   paco: Wireless system with MAC address xxxxxxxxxx secured and linked
[INFO]   Thu Nov 26 10:38:58 2009   paco: Wireless system with MAC address xxxxxxxxxx associated
[INFO]   Thu Nov 26 10:38:58 2009   Above message repeated 1 times
[WARN]   Thu Nov 26 08:55:16 2009   A network computer (Lin1) was assigned the IP address of 192.168.1.198.
[WARN]   Thu Nov 26 08:54:58 2009   Above message repeated 1 times
[WARN]   Thu Nov 26 08:54:53 2009   A network computer (xxxxxxxxxx ) was assigned the IP address of 192.168.1.199.
[INFO]   Thu Nov 26 07:01:03 2009   Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO]   Thu Nov 26 07:00:59 2009   Above message repeated 1 times
[INFO]   Thu Nov 26 07:00:59 2009   Time synchronized
[INFO]   Fri Nov 20 19:11:53 2009   Requesting time from 207.232.83.70
[INFO]   Fri Nov 20 19:11:53 2009   Time server ntp1.dlink.com is at IP address 207.232.83.70
[INFO]   Fri Nov 20 19:11:47 2009   WAN interface speed measurement completed. Upstream speed is 77369 kbps
[INFO]   Fri Nov 20 19:11:22 2009   Wireless link is up
[INFO]   Fri Nov 20 19:11:17 2009   Starting DHCP server
[INFO]   Fri Nov 20 19:11:10 2009   Estimating speed of WAN interface
[INFO]   Fri Nov 20 19:11:10 2009   Bringing up WAN using Static IP Address
[INFO]   Fri Nov 20 19:11:10 2009   WAN interface cable has been connected
[INFO]   Fri Nov 20 19:11:10 2009   LAN interface is up
[INFO]   Fri Nov 20 19:11:10 2009   LAN Ethernet Carrier Detected
[INFO]   Fri Nov 20 19:11:09 2009   Device initialized
[WARN]   Fri Nov 20 19:11:08 2009   Wireless schedule init
[INFO]   Fri Nov 20 19:11:08 2009   Syslog server set as IP address 192.168.1.100
[INFO]   Fri Nov 20 19:11:08 2009   No Internet access policy is in effect. Unrestricted Internet access allowed to everyone

Who can explain this? I know UDP packets (of syslog) do not necessarily arrive but this is not the issue. I will check the main differences next but would be happy if someone could explain:
- Did the router reboot. Does the connection up time display the time between reboots?
-Why is there a difference between the webpage log info and syslog info...

[partach1]

Ok here are the differences:
In syslog and not in 'weblog'
Nov 26 07:00:00 192.168.1.250 Thu Nov 26 07:00:04 2009 paco System Log: : Wireless schedule start
Nov 26 07:00:00 192.168.1.250 Thu Nov 26 07:00:04 2009 paco System Log: Wireless link is down

In 'weblog' and not in syslog
[INFO]   Fri Nov 20 19:11:08 2009   No Internet access policy is in effect. Unrestricted Internet access allowed to everyone[INFO]   Thu Nov 26 18:00:30 2009   Log viewed by IP address 192.168.1.197
[INFO]   Fri Nov 20 19:11:08 2009   Syslog server set as IP address 192.168.1.100
[WARN]   Fri Nov 20 19:11:08 2009   Wireless schedule init

Syncs up at [INFO]   Fri Nov 20 19:11:09 2009   Device initialized

In syslog:
Nov 26 07:01:00 192.168.1.250 Thu Nov 26 07:00:59 2009 paco System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129

Same time stamp but message in weblog says:
[INFO]   Thu Nov 26 07:00:59 2009   Above message repeated 1 times

This happens more so syslog does not know the trick: 'above message repeated n times' which makes sense or it should be called previous message repeated n time


So concluding:
- did a reboot occur yes or no?
- is the connection up time the alive time between reboots?
- differences syslog and weblog explainable. At start weblog works already, syslog not yet.
- When is weblog cleared?? Only at reboot? If so than there was a reboot but there are no problems reported in syslog? The question is why!

It also seems that the log settings in the weblog apply to syslog in that when you do not want to include security settings in the weblog they also do not show up in the syslog.
Hope someone can answer the questions raised.

Will now switch off NTP to see what this will do.....

[davevt31]

One thing I would do is uncheck the autocheck for firmware updates. Its not really needed.

The wireless restarts can happen at anytime the router changes channels.  If it picks up a signal from any neighboring radio sources it may change the channel.

I know when I was running Vista on my Desktop PC that was wired by 2 ethernet cables to the router, when I started the computer the first time each day, I would see a wireless restart due to the Nvidia program that teamed the 2 wired connection together.  I am pretty sure it was flooding the network on the inital startup.  The router didn't do a complete reset, but I could see in the logs that the wireless was restarting at that time.

[bluenote]

I'd say thats rebooting, but I only skimmed over your logs.  If you really want to have an external reference, if you have a windows machine plugged directly into the router, you should have an event log entry stating that the interface went down and up.  Of course, this by itself doesn't always mean reboot, since in certain situations I suppose autonegotiation could kick in/the port coudl be reset, and the router wouldn't actually have to reboot.
 On vista, you can even set up an event to fire on that event log ID, so it will bring up a little message box.

incidently, whats your time zone offset?  I wonder if that might be related to NTP possible causing you reboots.

good luck

Cory

[partach1]

I'd say thats rebooting, but I only skimmed over your logs.  If you really want to have an external reference, if you have a windows machine plugged directly into the router, you should have an event log entry stating that the interface went down and up.  Of course, this by itself doesn't always mean reboot, since in certain situations I suppose autonegotiation could kick in/the port coudl be reset, and the router wouldn't actually have to reboot.
 On vista, you can even set up an event to fire on that event log ID, so it will bring up a little message box.

incidently, whats your time zone offset?  I wonder if that might be related to NTP possible causing you reboots.

good luck

Cory

Time offset is GMT+1. Hope Lycan can comment if it is a reboot or not. At least thanks for the link-down tip of the port but the router is not that easily movable and would want to avoid to build an even larger test setup

[partach1]

Even with NTP switched of it happened again:
Here is the syslog log of today

Nov 27 00:03:33 192.168.1.250 Fri Nov 27 00:03:30 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx associated
Nov 27 00:03:33 192.168.1.250 Fri Nov 27 00:03:30 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx associated
Nov 27 00:03:33 192.168.1.250 Fri Nov 27 00:03:30 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx secured and linked
Nov 27 00:03:37 192.168.1.250 Fri Nov 27 00:03:34 2009 paco System Log: A network computer (name) was assigned the IP address of 192.168.1.197.
Nov 27 00:06:32 192.168.1.250 Fri Nov 27 00:06:29 2009 paco System Log: Allowed configuration authentication by IP address 192.168.1.197
Nov 27 00:07:00 192.168.1.250 Fri Nov 27 00:06:57 2009 paco System Log: Stored configuration to non-volatile memory
Nov 27 00:07:02 192.168.1.250 Fri Nov 27 00:06:59 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx associated
Nov 27 00:07:02 192.168.1.250 Fri Nov 27 00:06:59 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx associated
Nov 27 00:07:02 192.168.1.250 Fri Nov 27 00:06:59 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx secured and linked
Nov 27 00:08:08 192.168.1.250 Fri Nov 27 00:08:06 2009 paco System Log: Successfully exported configuration file
Nov 27 00:08:49 192.168.1.250 Fri Nov 27 00:08:47 2009 paco System Log: Stored configuration to non-volatile memory
Nov 27 00:08:51 192.168.1.250 Fri Nov 27 00:08:49 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx associated
Nov 27 00:08:51 192.168.1.250 Fri Nov 27 00:08:49 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx associated
Nov 27 00:08:51 192.168.1.250 Fri Nov 27 00:08:49 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx secured and linked
Nov 27 00:10:53 192.168.1.250 Fri Nov 27 00:10:50 2009 paco System Log: paco: Wireless system with MAC address xxxxxxxxxxxx disconnected for reason: Received Deauthentication
Nov 27 00:14:08 192.168.1.250 Fri Nov 27 00:14:05 2009 paco System Log: Administrator logout
Nov 27 01:00:06 192.168.1.250 Fri Nov 27 01:00:04 2009 paco System Log: : Wireless schedule stop
Nov 27 01:00:06 192.168.1.250 Fri Nov 27 01:00:04 2009 paco System Log: Disconnect all stations
Nov 27 01:00:06 192.168.1.250 Fri Nov 27 01:00:04 2009 paco System Log: Wireless restart
Nov 27 01:00:06 192.168.1.250 Fri Nov 27 01:00:04 2009 paco System Log: Wireless link is down
Nov 27 07:00:06 192.168.1.250 Fri Nov 27 07:00:04 2009 paco System Log: : Wireless schedule start
Nov 27 07:00:06 192.168.1.250 Fri Nov 27 07:00:04 2009 paco System Log: Wireless link is down
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:50 2009 paco System Log: Wireless schedule init
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:51 2009 paco System Log: Device initialized
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:52 2009 paco System Log: LAN Ethernet Carrier Detected
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:52 2009 paco System Log: LAN interface is up
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:52 2009 paco System Log: WAN interface cable has been connected
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:52 2009 paco System Log: Bringing up WAN using Static IP Address
Nov 27 07:00:23 192.168.1.250 Thu Nov 26 19:18:52 2009 paco System Log: Estimating speed of WAN interface
Nov 27 07:00:31 192.168.1.250 Thu Nov 26 19:18:59 2009 paco System Log: Starting DHCP server
Nov 27 07:00:35 192.168.1.250 Thu Nov 26 19:19:04 2009 paco System Log: Wireless link is up
Nov 27 07:00:39 192.168.1.250 Thu Nov 26 19:19:07 2009 paco System Log: WAN interface speed measurement completed.  Upstream speed is 99932 kbps
Nov 27 08:21:41 192.168.1.250 Thu Nov 26 20:40:11 2009 paco System Log: A network computer (name) was assigned the IP address of 192.168.1.197.
Nov 27 08:21:42 192.168.1.250 Thu Nov 26 20:40:12 2009 paco System Log: Wireless restart
Nov 27 08:22:32 192.168.1.250 Thu Nov 26 20:41:01 2009 paco System Log: Wireless restart
Nov 27 08:25:30 192.168.1.250 Thu Nov 26 20:43:59 2009 paco System Log: A network computer (xxxxxxxxxxxx) was assigned the IP address of 192.168.1.199.
Nov 27 08:25:35 192.168.1.250 Thu Nov 26 20:44:05 2009 paco System Log: A network computer (Lin1) was assigned the IP address of 192.168.1.198.
Nov 27 08:25:53 192.168.1.250 Thu Nov 26 20:44:23 2009 paco System Log: A network computer (Lin1) was assigned the IP address of 192.168.1.198.
Nov 27 08:40:02 192.168.1.250 Thu Nov 26 20:58:32 2009 paco System Log: Allowed configuration authentication by IP address 192.168.1.197


Another thing I noticed is that the current router time in the syslog is spot on but the web interface under menu 'time' tells me it is now thursday 26 november 2009 21:09:27. This suggests that multiple instances of time are used in the software? anyone to explain?

Lycan I did collected quite some data for you, is it helpfull? Do you need more specific data?
I think we can safely conclude that:
- the router does reboot by itself (watchdog?)
- It always reboots at 7:00 in the morning, even with NTP off. I use 1 schedule in the router from 7am to 1am. I use it for switching off wifi at night. So when it's time for the router to esthablish a wifi network again it dies in the attempt. (see syslog at 7:00)
- The jump of time stamp when using NTP is different than just setting the time. At least NTP is on the 20th of nov and without it says the day before. Always it talks about 7pm and some minutes when it should be 7:00 am flat

Why doesn't the log show the reason for the router to reboot? If it is a controlled reboot in the software (watchdog or other) it makes sense to log it via syslog. Is it build in?

My suggestion is that there are multple time variables used in the software which need to be looked over.
Syslog reports two time stamps? Why? calculating between two different time stamps could generate odd results...

[partach1]

hhhmmm without NTP the router does not work for me it seems.
See log addition today:

ov 27 12:41:30 192.168.1.250 Fri Nov 27 01:00:00 2009 paco System Log: : Wireless schedule stop
Nov 27 12:41:30 192.168.1.250 Fri Nov 27 01:00:00 2009 paco System Log: Disconnect all stations
Nov 27 12:41:30 192.168.1.250 Fri Nov 27 01:00:00 2009 paco System Log: Wireless restart
Nov 27 12:41:30 192.168.1.250 Fri Nov 27 01:00:00 2009 paco System Log: Wireless link is down

the time is 12:41 so that's ok. But the internal clock used for schedule is 1:00 so wireless is stopped according the schedule (see above posts)....

I set the time of the router yesterday and within a day it is about half a day behind ?!
At least with NTP it keeps more decent track of time it seems. and both with and without NTP the reboot happens....

[tentimes]

I think at this stage they don't want to comment. The soft reboot is curing things. I suspect something like a buffer overrun or memory leak from the code is causing the problems but they are unable to fnd it. I suppose if this fixes it then it isn't the end of the world.