You could write a script and run it as a cron job once a day if you really want to.
I find it isn't necessary...once it gets the time...you should be all set after that...the majority of the problems are due to DST changes.
redhawk
I know that, what I'm trying to say 2 different version have different behavior. ver 13000 - adjusted time by itself, ver 13230 only after running this special script.
Now, obviously, if you're not fiddling with the clock rate, there's no need to be doing this as often as shown there, but it's the same principle. This example would correct the time at 6AM daily. Paste these commands into Administration/Management/Additional Cron Jobs, and then Save/Apply.
Give a sec or 2 between each command. No reboot needed. Uptime will not be lost.
I have a cron job stopping and starting the process monitor on 2 wrt320n since the clock is running about 2 to 3 minutes faster per day. Other than having NTP do it's update when cycling the process monitor what else does the process monitor do?
I ONLY need the NTP to update at my scheduled request; isn't there a "better" way then cycling the process monitor? _________________ Dual-N Band Backbone Linking Dual Subnet to Upper and Lower Floors
--Upper Floor Newtork-- (Dual Subnet Cat6 Backbone)
Linksys E3000 K2.6 KONG-VPN 20575 Gateway
NetGear GS108Ev2 8-Port Smart Switch (802.1Q & 802.1P)
Linksys E3000 K2.6 KONG-VPN 20575 Dual-N AP Linking to Lower Floor + Dual DHCP Services
--Lower Floor Network-- (Dual Subnet Cat6 Backbone)
Linksys E3000 K2.6 KONG-VPN 20575 Dual-N RB Linking to Upper Floor
Linksys E2000 K2.6 KONG-VPN 20575 NG-Mixed AP + VAPs
Linksys WRH54G K2.4 EKO-MicroPlus 15508 (802.1Q 5-Port Smart Switch Only)
I ONLY need the NTP to update at my scheduled request; isn't there a "better" way then cycling the process monitor
Good question. I would certainly think so, but the method came from Eko (or was it BS) in the thread I quoted above, so perhaps not.
Reading the link is does look like it came from EKO. I would great if the NTP GUI gets an upgrade to input custom scheduling. _________________ Dual-N Band Backbone Linking Dual Subnet to Upper and Lower Floors
--Upper Floor Newtork-- (Dual Subnet Cat6 Backbone)
Linksys E3000 K2.6 KONG-VPN 20575 Gateway
NetGear GS108Ev2 8-Port Smart Switch (802.1Q & 802.1P)
Linksys E3000 K2.6 KONG-VPN 20575 Dual-N AP Linking to Lower Floor + Dual DHCP Services
--Lower Floor Network-- (Dual Subnet Cat6 Backbone)
Linksys E3000 K2.6 KONG-VPN 20575 Dual-N RB Linking to Upper Floor
Linksys E2000 K2.6 KONG-VPN 20575 NG-Mixed AP + VAPs
Linksys WRH54G K2.4 EKO-MicroPlus 15508 (802.1Q 5-Port Smart Switch Only)
&& makes the commands execute sequentially on success
cheers _________________ Linksys WRT320N
dd-wrt.v24-14929_NEWD-2_K2.6_mini.bin (previously using: dd-wrt.v24-13575_NEWD-2_K2.6_mini.bin, dd-wrt.v24-13493_NEWD-2_K2.6_mini_wrt320n.bin)
Debricked once ...using a DKU-5 cable. +++ 2011: Finally distroyed from overheating. Lent it out, and on a hot summer day the router took a sunbath behind glass. +++
Sorry for digging up an old thread, but my routers clock is not keeping the time correctly. I've set it to reboot once / week at night to sync the time, but it's no longer an option.
Does the above solution work 100%? Other messages tell to wait a few secs between the commands, so would it be "playing safe" to put something like this:
Another thing: has anyone yet discovered what other thing the process_monitor has to do other than ntpdate? Does that affect any other processes & tasks done by the router?
Joined: 04 Jan 2007 Posts: 10812 Location: Wherever the wind blows- North America
Posted: Sat Sep 24, 2011 20:25 Post subject:
My Asus 520gu has the clock_fix turned off...so it loses exactly 10 minutes an hour....this is what I use to fix the clock...Its on the Administration>>Management tab.
once per hour (since it's off by 10 minutes...I reset it every 50 minutes of router time)
redhawk
Clipboard01.jpg
Description:
Filesize:
17.59 KB
Viewed:
3023 Time(s)
_________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
Posted: Fri Dec 09, 2011 3:23 Post subject: On clocks and problems
redhawk0 wrote:
My Asus 520gu has the clock_fix turned off...so it loses exactly 10 minutes an hour....this is what I use to fix the clock...Its on the Administration>>Management tab.
once per hour (since it's off by 10 minutes...I reset it every 50 minutes of router time)
redhawk
I'm wondering if the NTP behavior is maybe what is causing some issues with WDS. I'm seeing my WDS link just "evaporate" after several days. The routers on both sides are working, but the WDS tunnel is down. And when I log into each router manually, I find that the clocks are off. Not always by much, but I'm thinking that if time is important for encryption, then it might just be off by enough to disrupt the tunnel. Does that make any sense?
I find that when I simply click Administration:Apply Settings on both, the time syncs back up and the tunnel comes back up by itself.
If my suspicion is right, this could be what is effecting WDS on some routers in general, considering that any router that is hardwired to an internet connection gets its time updated pretty quick (at boot time and within 120s), whereas any WDS nodes that are remote will be stuck sitting in the '70s. Basically a race condition: does the tunnel negotiate successfully in 1970 or fail in 2011.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
...using a DKU-5 cable.