plugout.net

It will be possible in future to make a change in the setup menu (Set Clock from internet time server NTP).
Here I think it would be better if you could enter web addresses (0.pool.ntp.org, 1.pool.ntp.org 2.pool.ntp.org) and not IPs like now.
IPs may change sometimes. It happened to me twice already.
Last time, two days ago.

Even when works, it is a problem with "Set Time Zone:" area; I'm in Romania and would be natural to select "(GMT 2:00) Eastern European Time", but does not show the correct time unless I select "(GMT 3:00) Kuwait, Moscow".
You can change anything about this, the next version?

If you can not do anything to change it, there is no problem.
I am happy with this firmware anyway, and thank you for all the effort you have made​​.
So please do not interpret me as a reproach what I wrote above.

Hi bozo29,

No problem with your questions. ;)

You must choose a time zone further east because we are in summer time (ie with a lag of one hour). In winter time, time zone will be correct. :-D

This is required because the ntp daemon does not support switching to summer time (this should not change in the future: too much work compared to two actions of the administrator! :tapfoot )

The current version of the demon does not support also dns addresses for NTP servers. So something to deepen if recent versions allow it. But I am surprised that you can't select servers with fixed IP address. Since 2009, the servers that I use have never changed their IP addresses!

Of course you must use stratum two time servers (see this list)

Hi Jocko,

I thank you for your answer and for the time servers list.
I know that because of summer time this happens, but I did not know that ntp daemon does not support changing to summer time.
I use Tomato firmware on my router and there are two settings: Time Zone and Auto Daylight Savings Time and when to switch to summer time this occurs automatically.
That is why I asked this question.
Of course there is no trouble that twice a year to make it work.

The problem is different and I can not express myself properly the first time:
I introduced the two IPs and I set the GMT +3 time instead of GMT +2.
Everything worked for a period not know exactly how, say approximately one month.
Then suddenly I realized that the time displayed in "System Information" was 4 hours prior to the correct time. :hammerhead
I looked in "Setup" and here everything was right (IPs were in place and the time was set to GMT +3). :dontknow
I rebooted the NAS and nothing. Then I put two other NTP server IPs and time returned to normal. :-D

That's actually my problem. Time has changed suddenly, and I have made ​​no changes in NAS's settings.
And it happens a second time, first time it happened when it was winter time.
Do you know why this happens?
I have to tell you something. I have 2 NWSP2, a "classic" and a "lite" and both had the same problem simultaneously.

Of course I do not find a problem to change settings hour twice a year.

Whatever the situation I am very pleased with this firmware, for which I thank you.
This firmware made ​​me buy the second NWSP2.

Hi bozo29,

We identified only one problem but it does not seem to be yours.

After a power failure, the ntpd daemon does no longer update the system time and it is shifted by twice the GMT+X selected. In your case, time would have had a gap of six hours, too three hours !

Fvdw and me are not able to reproduce this problem clearly. :scratch It seems to appear when the serveur is started while Internet access is not yet available at the ISP box.

I have to tell you something. I have 2 NWSP2, a "classic" and a "lite" and both had the same problem simultaneously.

If this happens to your two NWSP simultaneously, I think the problem is on side of the selected NTP servers. So Try to select others time servers and use different servers for each nwsp2.

If your problem reappears again with your two NAS, then we will have to seek on side of the firmware. :whistle

If there is a big jump in time then it will take the nas a very long time to correct the system time to this new value.
The reason is that the ntp daemon does it gradually in small steps. Only at boot it set in one step to the correct time. It is the normal way of working of the ntp daemon when running. Normally the time only drifts slowly and only small steps are required to correct it.
If the ntp daemon would adapt the time immediately in a step of 3 hours it can cause conflicts with applications actually running as it might then see suddenly times in the future or past.

Are you sure that the change was suddenly, it could be that the time drifted over time because ntp damon could not contact the internet time server and adjust it.