If time is syncing correctly it doesn't seem to be a problem with the ntp-server. It morely sounds like a problem with the timezone. Have you tried other timezones just for testing (e. g. +1 or -1 h of your timezone)?
As i read here in the forum, there seems to be very much problems with bulid 24461. Please have a look at:
The problem with NTP and timezones exists everywhere.
I can't confirm this! I'm using three Linksys WRT54G(L) as Routers/Access Points and none of this has a problem with getting the correct time from the ntp-server or using the correct timezone which i setted. The only "problem" is, that the time is only polled at a router restart, so there's no periodic resync. Time drifts away some seconds every day so this might be a problem if you don't restart your router e. g. one time per week. But: i solved this beahavior with a custom script so that the time get'S a sync every night.
@niclasc: Have you restarted your router after changing the setting?
The problem with NTP and timezones exists everywhere.
I can't confirm this! I'm using three Linksys WRT54G(L) as Routers/Access Points and none of this has a problem with getting the correct time from the ntp-server or using the correct timezone which i setted. The only "problem" is, that the time is only polled at a router restart, so there's no periodic resync. Time drifts away some seconds every day so this might be a problem if you don't restart your router e. g. one time per week. But: i solved this beahavior with a custom script so that the time get'S a sync every night.
@niclasc: Have you restarted your router after changing the setting?
No I havent restarted my router. I thought the idea with NTP is that it should sync the time periodically. To just do this at boot sound badly implemented.
Can you share me your script that you run every night?
Yes, it is! But i can't say if this behaviour matches all bulids or is just a problem of the builds i use with my WRT54G(L)s.
niclasc wrote:
Can you share me your script that you run every night?
Yes i can, but i haven't got the script running on my own router because i don't really need it. I'll have access to the the routers which which are running the script at the following weekend. Please send me a private message at the end of this week if i don't think about it any more.
Now I have rebooted my router and it still says "GMT" so NTP does NOT work.
A NTP only transmits his own time but not the timezone! It doesn't know in which timezone you are. You have to set your correct timezone on your own and save and apply it.
Now I have rebooted my router and it still says "GMT" so NTP does NOT work.
A NTP only transmits his own time but not the timezone! It doesn't know in which timezone you are. You have to set your correct timezone on your own and save and apply it.
Yes I have set my timezone. I had it set to "Europe/Stockholm". Thats GMT+2 and that didnt work. The time was GMT. 2 hours behind and when I checked with "date" it said GMT. I the tried "Europe/Kalingrad" which is GMT+4 but after a reboot it still 2 hours behind and "date" still says GMT
i am even using build 24461 of DD-WRT on a TP-Link TL-WR1043ND router.
On this device i have the same issue. the displayed time is 2 hours behind my actual time.
i added screenshots i take just a few minutes ago. my timezone is GMT+1 with summertime i think.
But i can't say if this behaviour matches all bulids or is just a problem of the builds i use with my WRT54G(L)s.
