Print

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

[Johnnyboy!]

So I *think* I have narrowed down my restart/instability issues down the NTP service on the router.

I'm using an A3 router with firmware 1.32b02 now, but I have had this problem with all firmwares 1.30+.  The basic problem is that I have been trying to upload several gigabytes of files (not using http or ftp, but an encrypted file transfer over an obscure port). The problem occurs when randomly, my router restarts itself, thus cutting my file transfer and pissing me off (the program doesn't auto-resume).

I have noticed some odd issues with the NTP service. I have been using ntp1.dlink.com and time.nrc.ca ntp services. Both have the same issues.

The first issue, is that occasionally, after a restart (either intentional restart or not) the router time reverts back to the *exact* time that I initially flashed the firmware. If I have the NTP service enabled, it will eventually correct it, though I think some things get messed up before that.

Here's an older log file describing the problem:

[INFO] Fri Jun 26 07:17:37 2009 Time synchronized
[INFO] Sat Jan 31 11:49:44 2004 Requesting time from 207.232.83.70
[INFO] Sat Jan 31 11:49:44 2004 Time server ntp1.dlink.com is at IP address 207.232.83.70
[INFO] Sat Jan 31 11:49:44 2004 Next dynamic DNS update scheduled for Tue Feb 24 10:49:43 2004
[INFO] Sat Jan 31 11:49:44 2004 Stored configuration to non-volatile memory
[INFO] Sat Jan 31 11:49:43 2004 Successfully updated dynamic DNS entry for ***.no-ip.ca nochg ***

If you notice, after a restart, the time reverted back to Jan 31, 2004 (not sure the significance of this date) then changed the date back to Jun 26, 2009. But before it corrected the date it updated the DynDNS registry and set the next update for Feb 24th, 2004.

Would this cause a crash to have conflicting dates programmed into the scheduler? I don't know.

In the 1.31 release notes, it states 14. Router time is not reset when factory reset. But I guarantee that it does indeed reset itself.

I'm not sure where I am going with this, all I know is that something is screwy with the NTP feature of the router. I know other people have had lots of issues with this feature as well. Without the time service enable, my router has run for nearly 24hrs now without a restart, which is (sadly) amazing!

I'll keep poking on it, see if I can come up with the exact issue.

Any other ideas?

jB

[partach1]

Good work
I have also seen NTP issues as said in a previous thread. I can safely say that also pool.ntp.org gives problems so indeed it does not seem to matter which server you use.

For me the problem became visible with loading saved settings. Before upgrading the firmware i saved my settings (which are quite some settings like schedules, wifi, virtual server, etc.; incl NTP and other timing settings in that page)
When loading this file into the new firmware i can no longer log in to the router and it starts to reboot every time (login in will give the nice page "router is determining the speed of the network or something". But this page never goes away again.

i narrowed this problem down to the time setting page (where you can also set NTP). Leaving this page default results in being able to load your settings and login afterwards. (and the router does not keep rebooting).

Sadly these NTP problems seem not related to the overall stability. Not setting a NTP server will still result in the router not being able to grant internet access after a few days. (all firmwares i have tested have stability problems: 1.20, 1.21 and 1.32b02)
In the first two firmwares the problems started with īDNS ALG relay message problemsī All clients donīt have access to DNS anymore. so no internet for all clients that get DNS settings via DHCP. (with or without DNS relay setting!!! yes really; I also tested this by setting fixed DNS settings in the client and switching of DNS relay, it can just not contact the DNS servers anymore)
1.32b02 has a new issue that pops up first after a few days: it shuts down wifi. After it has done that you can also not log in to the router anymore. It continously returns you to the log in page if you have logged in correctly.

Stablilty seems related to how much clients-data you ask the router to handle. So the harder the router has to work the sooner it decides to have itīs beauty sleep.

As there seem to be time issues with this router I think my next test will be to deactivate the schedule. I have a schedule that switches of wifi at night. If time is messed up it might explain that wifi is cut off during the day but doesnīt explain why I can not log in to the router from that point on until I reset it.

I hope a TS has enough information to start testing with this info. I am happy to share log or setting files if that would help (to a real TS, not to offend you Clancy, just have to say it I guess else you get pissed again )

[partach1]

Just turned of the schedule and noticed something really odd:
On the status page of the router is says:

Mon Jun 22 2009 21:50:54 GMT+0200 (Central Europe Daylight Time)

i just updated the firmware about a week ago and copied the time from my computer via the button on the time page.
Just did it again and saved it, the date is now correct.

it seems within a week it added an hour and lost a few days???

[lizzi555]

it seems within a week it added an hour and lost a few days???

I think it shows you the time from the last change when it wrote the settings into its non volatile memory.
Did you change settings and save them at that time ?

[partach1]

After upgrading the default time is January first a few years ago.
As I also discovered an NTP issue the only thing I did was copy the time from my computer (via the button on the time page) just after upgrading about a week ago
So I did change and save it else the time would not be that recent?

Exactly an hour difference suggests time offset bugs in the software.
The few days difference I can not explain at all

b.t.w. the time is shown in the overall status page and the time page, both where showing the same time and date, which was wrong

[partach1]

Just (23:40) checked the time of my router, set it 2.5 hours ago.
On the status page it is already running 35 minutes behind: 23:05 

but when going to the time page it looks ok again?!
Reverting back to the time page shows the correct time again??

The log doesn't show much except:
[INFO]   Sun Jun 28 23:16:44 2009   Administrator logout
i do not see an Admin login message?

So I logged in after 23:16, it showed me 23:05 when in fact, at the time i looked it was 23:40

Any explanation for that?

[Johnnyboy!]

So...  I have disabled all NTP time options, Set the wireless to 802.11g only using Channel 11 (no auto scan), disabled DNS Relay, disabled Shareport and disabled all wireless scheduling options (set to Always On) on my 1.32b02 A3 Router and now it's been running steady for 3 days and 15 hours without a restart!!!!  WoooHoooo!

First of all, I wish I knew what combination of the above actually fixed the restart problem.

Second, if I knew that I had to disable most advanced features of this router, I wish I just bought a $45 Wireless-G router with no features instead.

At least then I wouldn't be offering banana's to everyone at low low prices!

jB

[grking]

Hey Johnny. I have the same setup as you except I do have N+G enabled and it hasn't gone down in almost a week, Try enabling that and change nothing else.

[davevt31]

Johnnyboy, if you have it running for a while without issues.  Add 1 thing back and see if it stays running.  Wait a few days to a week then add 1 more and see what happens.  You may be able to isolate which combination of things is causing the reboots.

[Johnnyboy!]

Yeha, that's what I'm doing now. I just added the 802.11n+g option on channel 11. I still think it's got something to do with the NTP, but *sometimes* the NTP serivice runs without a hitch, which is why I am looking into combination factors now.

I think if it can go 48 hours without restarting itself, I will consider it stable.

jB

[KevTech]

I have also seen NTP issues as said in a previous thread. I can safely say that also pool.ntp.org gives problems so indeed it does not seem to matter which server you use.

You should not use just pool.ntp.org as that is all of the servers so your router keeps checking them till it finds the one for your time zone. This can result in your IP being banned by the servers.

From the pool site:

As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone might not exist for your country, or might contain only one or two timeservers. If you know timeservers that are really close to you (measured by network distance, with traceroute or ping), time probably will be even better.

[partach1]

I disabled the schedule option as well and it is now running for 3 days which is a record for the thing!
My feeling is also that the time settings are the biggest suspect.
NTP, schedules, time zones, etc.
Followed by Wifi...
It has shown for me (can any one else check this?) saving the config with NTP settings and reverting back from factory default to those settings goes wrong. Without NTP settings in the config all seems ok....

[partach1]

I finally have some proof that there is a problem with this router regarding time.
As posted in the NTP thread I set the time of my router a few days ago.
I switched many features of and it has been running for 3 days which for the thing is a miracle.
Attached a screenshot just taken.
it says July 2nd just after nine pm. So in about 4-5 days it runs almost two days behind.
Let's just say an unacceptable margin....
Can somebody please do a check at their side for this. The settings are shown in the displayed jpg.

LOL even the website doesn't work correctly... I will upload on the web and insert picture in a minute


for those that don't believe I pressed the copy time from computer button before capturing the image


Thinking my English was bad..... look at the alive time spelling....

[partach1]

Just activated NTP to correct my time and guess what!
INSTANT DEATH. 

The 655 got into a continious reboot cycle. No control possible. Only option: factory reset on the back...
This proves it beyond doubt for me that there is a serious problem with this thing.


and of-course the log is gone !"!#$!"$

[Xinot]

and of-course the log is gone !"!#$!"$

Thats why you should use something like THIS