• May 21, 2025, 12:18:28 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: beta 9 firmware does some sort of soft reboot?  (Read 16003 times)

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: beta 9 firmware does some sort of soft reboot?
« Reply #15 on: November 28, 2009, 12:45:30 AM »
Seems you are right. Too bad they do not log the crash reason via syslog.
with some decent try{}catch{} code that should be doable in most cases.

I would be happy to run a debug version with more logging here as I can repoduce things within a day!
DLink claim not to be able to reproduce things at their lab which is possible but why not let them give me go at it.

Many, many people would be helped if they nail the problem(s) of this router.......
DLink you have my email take me up on my offer.
« Last Edit: November 28, 2009, 01:42:23 AM by partach1 »
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: beta 9 firmware does some sort of soft reboot?
« Reply #16 on: November 30, 2009, 12:20:30 PM »
For everyone seeing this reboot, please list your hardware revisions.
I'll test it personally.
Logged

grking

  • Level 1 Member
  • *
  • Posts: 18
Re: beta 9 firmware does some sort of soft reboot?
« Reply #17 on: November 30, 2009, 01:12:08 PM »
Very similar reboots on A3
Logged

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: beta 9 firmware does some sort of soft reboot?
« Reply #18 on: December 02, 2009, 09:58:34 AM »
A4 here, would my config help?
Btw still rebooting each morning at 7 like clockwork...

btw talking about strange syslogsą
Dec  2 01:29:04 192.168.1.250 Wed Dec 02 01:29:04 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795
Dec  2 01:29:05 192.168.1.250 Wed Dec 02 01:29:06 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795
Dec  2 01:29:08 192.168.1.250 Wed Dec 02 01:29:08 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795
Dec  2 01:29:10 192.168.1.250 Wed Dec 02 01:29:10 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795
Dec  2 01:29:12 192.168.1.250 Wed Dec 02 01:29:13 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795
Dec  2 01:29:17 192.168.1.250 Wed Dec 02 01:29:17 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795
Dec  2 01:29:27 192.168.1.250 Wed Dec 02 01:29:27 2009 paco System Log: H.323 ALG rejected packet from 187.39.98.91:1720 to xx.xx.xx.xx:4795

Why did this (only saw 2 times such brief warnings) occur if firewall & security settings are not on? Glitch?
« Last Edit: December 02, 2009, 10:07:52 AM by partach1 »
Logged

bluenote

  • Level 2 Member
  • **
  • Posts: 82
Re: beta 9 firmware does some sort of soft reboot?
« Reply #19 on: December 02, 2009, 02:25:31 PM »
To summarize then, you have a schedule to turn off WIFI, and when it turns back on, the router reboots?

Some people have been asking for a 'feature' like this for a while :)  Because *without* a reboot, their router locks up solid :)

If it is indeed completely related to wireless schedule then I dont know what to suggest, except, to confirm that it is indeed the scheduling causing the reboot, and not some other event that happens at 7am, to disable the scheduling for a day or two.  At least this will confirm it solidly.

good luck
Logged

ruski

  • Level 1 Member
  • *
  • Posts: 11
Re: beta 9 firmware does some sort of soft reboot?
« Reply #20 on: December 02, 2009, 05:55:37 PM »
I am getting the reboot.  Hardware A2 beta09 firmware 11/05/09
Logged

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: beta 9 firmware does some sort of soft reboot?
« Reply #21 on: December 03, 2009, 09:47:07 AM »
Quote from: bluenote on December 02, 2009, 02:25:31 PM
To summarize then, you have a schedule to turn off WIFI, and when it turns back on, the router reboots?

Some people have been asking for a 'feature' like this for a while :)  Because *without* a reboot, their router locks up solid :)

If it is indeed completely related to wireless schedule then I dont know what to suggest, except, to confirm that it is indeed the scheduling causing the reboot, and not some other event that happens at 7am, to disable the scheduling for a day or two.  At least this will confirm it solidly.

good luck


It is about the stability of the 655 in general. Many people, including me, have problems with the many different versions released. It seems DLink has not nailed the mother of all problems yet as the latest firmware still has problems. I just found a scenario in which the router seems to go safe by rebooting. Or in other words encounters a problem is my assumption. Investigating this problem (by DLink) could lead to a root cause problem, potentially helping many people if fixed.
I am pretty sure that when I turn off the schedule the router will encounter a problem at some point altough probably after more days of running , for you I will test this now:)
« Last Edit: December 03, 2009, 09:49:44 AM by partach1 »
Logged

bluenote

  • Level 2 Member
  • **
  • Posts: 82
Re: beta 9 firmware does some sort of soft reboot?
« Reply #22 on: December 03, 2009, 11:13:28 AM »
I'm not suggesting that dlink not fix it.  Believe me, I know there are still lots of poorly handled errors that result in reboots even in the latest firmware.  And they should be fixed.

But I mean, really, do you expect them, after so long, to magically be able to fix all the things that are wrong with this router?

At least if you can properly narrow it down so that it *might* be reproducible it might get put on an issues list somewhere to actually get fixed.

If not, you can take your pick between slim, and none IMHO.
Logged

partach1

  • Level 2 Member
  • **
  • Posts: 52
Re: beta 9 firmware does some sort of soft reboot?
« Reply #23 on: December 04, 2009, 08:41:43 AM »
As said it also reboots without the 7:00 am schedule, although I must admit much sooner than i thought.
What's with all the wireless restarts anyway? The reboot seems linked to wireless problems then?
This is new. Have read the 'cracked wireless restart' thread but funny thing is that I have the router connected to a dlink green Gb switch, which connects it to all clients. At the time of the wireless restarts there was no laptop or any PC like client active. Only active party each night is my DS207+ NAS. No SEP to be seen anywhere in the house.... So are there other reasons to let it restart?

Dec  4 00:03:16 192.168.1.250 Fri Dec 04 00:03:19 2009 paco System Log: Wireless restart
Dec  4 00:04:23 192.168.1.250 Fri Dec 04 00:04:27 2009 paco System Log: Wireless restart
Dec  4 00:06:51 192.168.1.250 Fri Dec 04 00:06:54 2009 paco System Log: Wireless restart
Dec  4 00:16:42 192.168.1.250 Fri Dec 04 00:16:46 2009 paco System Log: Wireless restart
Dec  4 00:18:01 192.168.1.250 Fri Dec 04 00:18:04 2009 paco System Log: Wireless restart
Dec  4 00:21:33 192.168.1.250 Fri Dec 04 00:21:37 2009 paco System Log: Wireless restart
Dec  4 00:21:47 192.168.1.250 Fri Dec 04 00:21:50 2009 paco System Log: Wireless restart
Dec  4 00:22:12 192.168.1.250 Fri Dec 04 00:22:16 2009 paco System Log: Wireless restart
Dec  4 00:25:39 192.168.1.250 Fri Dec 04 00:25:43 2009 paco System Log: Wireless restart
Dec  4 00:27:29 192.168.1.250 Fri Dec 04 00:27:33 2009 paco System Log: Wireless restart
Dec  4 00:29:54 192.168.1.250 Fri Dec 04 00:29:58 2009 paco System Log: Wireless restart
Dec  4 00:34:05 192.168.1.250 Fri Dec 04 00:34:09 2009 paco System Log: Wireless restart
Dec  4 00:35:51 192.168.1.250 Fri Dec 04 00:35:55 2009 paco System Log: Wireless restart
Dec  4 00:38:41 192.168.1.250 Fri Dec 04 00:38:45 2009 paco System Log: Wireless restart
Dec  4 00:38:48 192.168.1.250 Fri Dec 04 00:38:52 2009 paco System Log: Wireless restart
Dec  4 00:39:15 192.168.1.250 Fri Dec 04 00:39:19 2009 paco System Log: Wireless restart
Dec  4 00:39:47 192.168.1.250 Fri Dec 04 00:39:51 2009 paco System Log: Wireless restart
Dec  4 00:41:23 192.168.1.250 Fri Dec 04 00:41:27 2009 paco System Log: Wireless restart
Dec  4 00:41:32 192.168.1.250 Fri Dec 04 00:41:35 2009 paco System Log: Wireless restart
Dec  4 00:41:35 192.168.1.250 Fri Dec 04 00:41:39 2009 paco System Log: Wireless restart
Dec  4 00:42:10 192.168.1.250 Fri Dec 04 00:42:13 2009 paco System Log: Wireless restart
Dec  4 00:46:09 192.168.1.250 Fri Dec 04 00:46:13 2009 paco System Log: Wireless restart
Dec  4 00:46:27 192.168.1.250 Fri Dec 04 00:46:31 2009 paco System Log: Wireless restart
Dec  4 00:48:44 192.168.1.250 Fri Dec 04 00:48:48 2009 paco System Log: Wireless restart
Dec  4 00:49:18 192.168.1.250 Fri Dec 04 00:49:22 2009 paco System Log: Wireless restart
Dec  4 00:50:14 192.168.1.250 Fri Dec 04 00:50:18 2009 paco System Log: Wireless restart
Dec  4 00:50:40 192.168.1.250 Fri Dec 04 00:50:44 2009 paco System Log: Wireless restart
Dec  4 00:50:43 192.168.1.250 Fri Dec 04 00:50:47 2009 paco System Log: Wireless restart
Dec  4 00:57:47 192.168.1.250 Fri Dec 04 00:57:51 2009 paco System Log: Wireless restart
Dec  4 00:58:35 192.168.1.250 Fri Dec 04 00:58:39 2009 paco System Log: Wireless restart
Dec  4 00:58:51 192.168.1.250 Fri Dec 04 00:58:55 2009 paco System Log: Wireless restart
Dec  4 01:00:46 192.168.1.250 Fri Dec 04 01:00:50 2009 paco System Log: Wireless restart
Dec  4 01:09:33 192.168.1.250 Fri Dec 04 01:09:38 2009 paco System Log: Wireless restart
Dec  4 01:11:13 192.168.1.250 Fri Dec 04 01:11:18 2009 paco System Log: Wireless restart
Dec  4 01:13:09 192.168.1.250 Fri Dec 04 01:13:14 2009 paco System Log: Wireless restart
Dec  4 01:19:47 192.168.1.250 Fri Dec 04 01:19:52 2009 paco System Log: Wireless restart
Dec  4 01:34:53 192.168.1.250 Fri Dec 04 01:34:58 2009 paco System Log: Wireless restart
Dec  4 01:35:02 192.168.1.250 Fri Dec 04 01:35:07 2009 paco System Log: Wireless restart
Dec  4 01:38:02 192.168.1.250 Fri Dec 04 01:38:07 2009 paco System Log: Wireless restart
Dec  4 01:38:23 192.168.1.250 Fri Dec 04 01:38:28 2009 paco System Log: Wireless restart
Dec  4 01:39:12 192.168.1.250 Fri Dec 04 01:39:17 2009 paco System Log: Wireless restart
Dec  4 01:40:34 192.168.1.250 Fri Dec 04 01:40:39 2009 paco System Log: Wireless restart
Dec  4 01:40:50 192.168.1.250 Fri Dec 04 01:40:55 2009 paco System Log: Wireless restart
Dec  4 01:42:07 192.168.1.250 Fri Dec 04 01:42:12 2009 paco System Log: Wireless restart
Dec  4 01:42:36 192.168.1.250 Fri Dec 04 01:42:41 2009 paco System Log: Wireless restart
Dec  4 01:43:58 192.168.1.250 Fri Dec 04 01:44:03 2009 paco System Log: Wireless restart
Dec  4 01:44:02 192.168.1.250 Fri Dec 04 01:44:07 2009 paco System Log: Wireless restart
Dec  4 01:46:21 192.168.1.250 Fri Dec 04 01:46:26 2009 paco System Log: Wireless restart
Dec  4 01:46:47 192.168.1.250 Fri Dec 04 01:46:52 2009 paco System Log: Wireless restart
Dec  4 01:47:12 192.168.1.250 Fri Dec 04 01:47:17 2009 paco System Log: Wireless restart
Dec  4 01:48:49 192.168.1.250 Fri Dec 04 01:48:54 2009 paco System Log: Wireless restart
Dec  4 01:55:27 192.168.1.250 Fri Dec 04 01:55:32 2009 paco System Log: Wireless restart
Dec  4 01:55:31 192.168.1.250 Fri Dec 04 01:55:36 2009 paco System Log: Wireless restart
Dec  4 01:58:05 192.168.1.250 Fri Dec 04 01:58:10 2009 paco System Log: Wireless restart
Dec  4 01:59:05 192.168.1.250 Fri Dec 04 01:59:10 2009 paco System Log: Wireless restart
Dec  4 02:00:33 192.168.1.250 Fri Dec 04 02:00:38 2009 paco System Log: Wireless restart
Dec  4 02:02:55 192.168.1.250 Fri Dec 04 02:03:00 2009 paco System Log: Wireless restart
Dec  4 02:03:01 192.168.1.250 Fri Dec 04 02:03:05 2009 paco System Log: Wireless restart
Dec  4 02:03:49 192.168.1.250 Fri Dec 04 02:03:54 2009 paco System Log: Wireless restart
Dec  4 02:04:33 192.168.1.250 Fri Dec 04 02:04:38 2009 paco System Log: Wireless restart
Dec  4 02:04:39 192.168.1.250 Fri Dec 04 02:04:43 2009 paco System Log: Wireless restart
Dec  4 02:06:59 192.168.1.250 Fri Dec 04 02:07:04 2009 paco System Log: Wireless restart
Dec  4 02:15:52 192.168.1.250 Fri Dec 04 02:15:57 2009 paco System Log: Wireless restart
Dec  4 02:19:28 192.168.1.250 Fri Dec 04 02:19:33 2009 paco System Log: Wireless restart
Dec  4 02:22:26 192.168.1.250 Fri Dec 04 02:22:31 2009 paco System Log: Wireless restart
Dec  4 02:22:37 192.168.1.250 Fri Dec 04 02:22:42 2009 paco System Log: Wireless restart
Dec  4 02:24:20 192.168.1.250 Fri Dec 04 02:24:25 2009 paco System Log: Wireless restart
Dec  4 02:27:42 192.168.1.250 Fri Dec 04 02:27:47 2009 paco System Log: Wireless restart
Dec  4 02:34:40 192.168.1.250 Fri Dec 04 02:34:45 2009 paco System Log: Wireless restart
Dec  4 02:34:59 192.168.1.250 Fri Dec 04 02:35:04 2009 paco System Log: Wireless restart
Dec  4 02:35:05 192.168.1.250 Fri Dec 04 02:35:10 2009 paco System Log: Wireless restart
Dec  4 02:36:18 192.168.1.250 Fri Dec 04 02:36:22 2009 paco System Log: Wireless restart
Dec  4 02:37:19 192.168.1.250 Fri Dec 04 02:37:24 2009 paco System Log: Wireless restart
Dec  4 02:39:13 192.168.1.250 Fri Dec 04 02:39:18 2009 paco System Log: Wireless restart
Dec  4 02:39:15 192.168.1.250 Fri Dec 04 02:39:20 2009 paco System Log: All Wireless shut down
Dec  4 02:39:15 192.168.1.250 Fri Dec 04 02:39:20 2009 paco System Log: Disconnect all stations
Dec  4 02:39:15 192.168.1.250 Fri Dec 04 02:39:20 2009 paco System Log: Wireless restart
Dec  4 02:39:15 192.168.1.250 Fri Dec 04 02:39:20 2009 paco System Log: Wireless link is down
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:37 2009 paco System Log: Wireless schedule init
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:38 2009 paco System Log: Device initialized
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:39 2009 paco System Log: LAN Ethernet Carrier Detected
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:39 2009 paco System Log: LAN interface is up
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:39 2009 paco System Log: WAN interface cable has been connected
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:39 2009 paco System Log: Bringing up WAN using Static IP Address
Dec  4 02:39:33 192.168.1.250 Tue Dec 01 20:44:39 2009 paco System Log: Estimating speed of WAN interface
Dec  4 02:39:40 192.168.1.250 Tue Dec 01 20:44:46 2009 paco System Log: Starting DHCP server
Dec  4 02:39:45 192.168.1.250 Tue Dec 01 20:44:51 2009 paco System Log: Wireless link is up
Dec  4 02:39:56 192.168.1.250 Tue Dec 01 20:45:02 2009 paco System Log: WAN interface speed measurement completed.  Upstream speed is 6791 kbps
Dec  4 02:40:02 192.168.1.250 Tue Dec 01 20:45:09 2009 paco System Log: Time server ntp1.dlink.com is at IP address 207.232.83.70
Dec  4 02:40:02 192.168.1.250 Tue Dec 01 20:45:09 2009 paco System Log: Requesting time from 207.232.83.70
Dec  4 02:40:02 192.168.1.250 Fri Dec 04 02:40:03 2009 paco System Log: Time synchronized
« Last Edit: December 04, 2009, 09:04:38 AM by partach1 »
Logged

bluenote

  • Level 2 Member
  • **
  • Posts: 82
Re: beta 9 firmware does some sort of soft reboot?
« Reply #24 on: December 04, 2009, 10:37:39 AM »
If you are actually just having actual router reboots then there's tonnes of explanations.  At the school the dlink programmers went to, they were sitting at the back, and they thought the instructor said "On Err Reboot" instead of "On Err Goto".

For myself, most recently I've had to stop my torrent client from using UPNP because that was causing reboots, and in the past I've had to dial down my connection numbers, turn off DHT / PXE and other services that dont respect connection limits and also invite many connections to be made.

Beyond that, if there's no correlations in your logs then you're going to have to play the disable-and-narrow-down game. 
Logged
Pages: 1 [2]
« previous next »