Print

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

[drick]

looking at the 1.08 beta release notes:

"22. Changes DST GUI design."

This now adds the following options to the GUI:

TIME CONFIGURATION :

Time Zone :

Enable Daylight Saving :    

Daylight Saving Dates :    
 DST Start    (mm/dd)
 DST End    (mm/dd)

Now i'm not clear on what the start or stop dates are for DST or why i would enter them in here manually? If is use a NTP server and click on DST, i want the system to figure it out, not me.

This is also different than the 1.03b66 code on my DNS-343, which doesn't even allow DST, but keeps the correct time.

Any inupt as to why you guys did it this way?

[drick]

FYI, when i select my correct time zone (PST) and enable NTP, the clock is still wrong (short by one hour).

this sticks even when i switch around between the NTP servers.

bottom line, this is still broken.

[drick]

this may have something to do with the fact that the 323 is still using an older version of the kernel vs. the 343.

root@DNS323:~# uname -a
Linux DNS323 2.6.12.6-arm1 #31 Mon Mar 23 19:39:43 CST 2009 armv5tejl unknown

root@DNS343:~# uname -a
Linux DNS343 2.6.22.7 #29 Thu Apr 2 09:24:36 CST 2009 armv5tejl unknown

[Arvald]

I got the NTP to work after another reboot.

first reboot did not pick it up.

[drick]

I got the NTP to work after another reboot.

first reboot did not pick it up.

are you using DST or not?

trying the 2nd reboot now

[drick]

2nd reboot didn't work, now i'm adding the DST dates per this site:

http://aa.usno.navy.mil/faq/docs/daylight_time.php

"In 2009, daylight time begins on March 8 and ends on November 1."

after adding these, and clicking on the save tab it finally picked up the right time.

that should be documented somewhere by D-Link IMHO. the help page for time doesn't mention any of this. excerpts below

Time
Time Configuration
There are three choices for setting the time.

NTP Server
Enter an NTP Server here. An NTP Server is a server on the Internet that maintains time. The DNS-323 will contact the server you entered and receive the correct time. Click 'Save Settings' after entering an NTP Server.

Set The Date And Time Manually
Enter the complete time and date settings manually. Click 'Save Settings' to apply these settings.
Activate Daylight Savings Time if it applies to your region. Click 'Save Settings' when finished.

Set Time From My Computer
Click 'Save Settings' to have the DNS-323 set its own clock according to the time on your computer.

Daylight Saving Time
Activate Daylight Savings Time if it applies to your region. Click 'Save Settings' when finished.

[Arvald]

yes using DST.  and it did not let me save till I put in the start and end dates so I did not mention that.

[ECF]

Yeah you have to designate the dates for daylight savings by default as you can see it is not set. it has been designed this way because the daylight savings dates have recently been changed last year and are not the same in all regions. It may just be California I am not sure.

[drick]

Yeah you have to designate the dates for daylight savings by default as you can see it is not set. it has been designed this way because the daylight savings dates have recently been changed last year and are not the same in all regions. It may just be California I am not sure.

just out of curiosity, why the difference between the 323 & 343?

[Arvald]

Yeah you have to designate the dates for daylight savings by default as you can see it is not set. it has been designed this way because the daylight savings dates have recently been changed last year and are not the same in all regions. It may just be California I am not sure.

Dates were alligned for DST all states and Canada using DST... that was 2007.
There are still some states that refuse to use DST so they did not change.

[rori]

I'm not sure wheather or not this is another reason to fix ntpd?

ntpd autokey stack buffer overflow

ntpd contains a stack buffer overflow, which may allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system or create a denial of service.

http://www.kb.cert.org/vuls/id/853097

[shanek]

I upgraded to 1.08 in an attempt to solve the DST issue (it seems to work good when you select ‘save’, but sometime over the next 24 hours, the DNS-323 reverts to an hour behind).  I see now that we’re supposed to set the start and end dates each year?  On one hand, hey, if it works, this is a step forward, but on the other hand, you’ve got to be kidding me?  I don’t know if I’ve ever seen such a thing in the equipment that I administer (many models of routers and switches, both high end and low end, Windows servers and Solaris servers).  Why not do it like the DIR-825 does it (in 1.11 code…the code itself has major issues, but it got the DST/time settings right on.  =)

There is some problem that won't let me upload an attachment right now it seems, but the DIR-825 effectively does it like the commecial UNIX variants - enter time zone (+/-), enable DST, DST offset (in my case an hour), and then both the start and end months, week numbers, days and hours.  Thus, for this year in Alaska, it would be:

Timezone (GMT-9)
Enable DST (checked)
Offset (+1:00)
Start: (Mar 2nd Sun 2am)
End: (Nov 1st Sun 2am)

I’d also like to request that the DNS-323 query the NTP servers a heck of a lot more often than it does.  I’ve had two in the house and they both loose ~15 seconds a day (this with 1.07 code).  A query every 24 hours would be nice.

[shanek]

Nope, v1.08 did not fix the DST problem either.    I was out of town since I upgraded and posted the above message and just got home to check...it has reverted to an hour behind again.

SK

[Tom]

Confirmed on my box as well.

[gunrunnerjohn]

Same here, I'm amazed that something this simple eludes them for all this time!  I've had the DNS-323 for over a year, and all the firmware versions come and go, and the time is still screwed up!