In my local network, I have an ntp server daemon running on my Tomato router. I have a pretty good source of time, so this works rather well having Tomato run this daemon. I simplified what I use, and this is the result. If anyone finds this useful, then the minimal effort used to create this wasn't wasted. In this ntp server, the router will return it's own time, wrapped around the ntp protocol. Last April, I made an update to ntpc (ntp client) which allows small incremental changes to the system time. If you run that (ntpstep) in a cron, you can keep the router to within a second or so of real time. If that level of accuracy is 'good enough', then having the router provide time via ntp is very practical. Some people just want to set the clocks on their PC and have it be reasonably close. So it really just boils down to what your specific requriements are. There is more information in the README from the attached file (along with the source code, executable, new Makefile, and a copy of RFC2030).