D-Link Forums
The Graveyard - Products No Longer Supported => DNS-323 => D-Link Storage => Beta code! => Topic started by: drick on May 16, 2009, 07:37:18 AM
-
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?
-
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.
-
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
-
I got the NTP to work after another reboot.
first reboot did not pick it up.
-
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
-
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.
-
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.
-
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.
-
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?
-
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.
-
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 (http://www.kb.cert.org/vuls/id/853097)
-
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.
-
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
-
Confirmed on my box as well.
-
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!
-
I've been running 1.08b5 for a week or so now (currently on daylight savings time), and it's syncing to an NTP server on my LAN, and, so far, it's kept perfectly good time.
-
I upgraded to 108b5, reset the box to defaults, and I think it's actually keeping time now. I have the latest beta on my DNS-321 now, and it's finally keeping time as well. I guess even if the account permissions are all screwed up, at least the box can keep time now. ::)
-
21 days and my dns323 has more or less the correct time. still pretty stupid that i have to specify the exact dates each year that dst should be in effect, but hey, this is a major step forward!! =) =)
-
Mine keeps the proper time, it's obviously setting itself from the time server.
Specifying the exact dates for start and end of DST isn't that stupid, believe it or not, there are still variations across the country.
-
I have to respectfully disagree. I have been in this industry for a long time and I configure a lot of devices, anywhere from $50 to $150K in cost, serves, routers, switches, etc. until the DNS-323, I've never once (at least in the last decade...maybe before...too long ago to remember ;-) had to specific/change the dates every year. In some cases I specify a time zone, in others, a time zone and starting/ending month/day/time and offset (great flexibility on the later). An example would be '2nd sunday in march at 2am, 1st sunday in november at 2am, +1 hour' Point being though, I set it once and don't touch it again until our beloved government starts mucking with the rules for no good reason.
-
I have to respectfully disagree. I have been in this industry for a long time and I configure a lot of devices, anywhere from $50 to $150K in cost, serves, routers, switches, etc. until the DNS-323, I've never once (at least in the last decade...maybe before...too long ago to remember ;-) had to specific/change the dates every year. In some cases I specify a time zone, in others, a time zone and starting/ending month/day/time and offset (great flexibility on the later). An example would be '2nd sunday in march at 2am, 1st sunday in november at 2am, +1 hour' Point being though, I set it once and don't touch it again until our beloved government starts mucking with the rules for no good reason.
However there are places they do change and this doesn't just go to one country. I'm not sure time servers serve outs DST time but depend on the client to handle that e.g many OS would have something built in to sort it out (lookup zoneinfo). This avoids that mechanism and probably you'll set it once and forget. Pity it doesn't work for the Southern Hemisphere.
-
I’m not sure I understand your first sentence…
Correct, time servers don’t send out DST information, but rather rely in the local host to know where it is. You can check out Wikipedia if you want for a description of the NTP protocol (http://en.wikipedia.org/wiki/Network_Time_Protocol).
I also don’t understand your statement about NTP/DST not working in the Southern Hemisphere? A client that implements these properly will work in any city/state/country in the world.
-
I’m not sure I understand your first sentence…
Correct, time servers don’t send out DST information, but rather rely in the local host to know where it is. You can check out Wikipedia if you want for a description of the NTP protocol (http://en.wikipedia.org/wiki/Network_Time_Protocol).
I also don’t understand your statement about NTP/DST not working in the Southern Hemisphere? A client that implements these properly will work in any city/state/country in the world.
The date you enter is month/date and it appears validation is done on just these two values. Here it means start date is effectively after end date. ie start 26 Sep end in 6 Apr.
-
:(
Oh, I see...
Wow, it's amazing that they can screw it up so badly, isn't it? Espeically considering that they get it so right in other products!