Chriskovic's picture
Chriskovic - Sat, 2025/05/10 - 01:58
I'm using two network interfaces for Zoneminder - one for the VM and another for the cameras. What's the best way to get my camera interface to query my VM interface for NTP? Do I have to install ntpd or chrony? Thanks
Forum: 
Support
Tags: 
zoneminder
ntp
Jeremy Davis's picture

Jeremy Davis - Tue, 2025/05/13 - 08:40

TurnKey uses ntpsec (a security hardened version of ntpd) - installed direct from the Debian apt repos.

It should "just work" and automatically update the time once per day. By default it should use all available interfaces - so if the interface you use for your cameras doesn't provide a route to the timeservers, that shouldn't be an issue.

Although rereading your post, I'm not sure if that answers your question? If not, could you please elaborate on what exactly you are trying to do and/or what you are trying to achieve?

Chriskovic's picture

Chriskovic - Sun, 2025/05/18 - 20:24
Thank you for the response Jeremy. I thought "just work" was going to work. Interface 1: Network + application access with NTP. Interface 2: Just cam access. The cams weren't pulling NTP. Due to lack of time I went went with installing chrony and that did the trick. After some easy config it was querying interface 1 for NTP and serving NTP to Interface 2. Best
Jeremy Davis's picture

Jeremy Davis - Tue, 2025/05/20 - 09:31

I'm glad that you got it working. Sorry that I misunderstood. My previous response was in context of your TurnKey server being an NTP client and getting time updates for itself. I now understand that you meant to use your TurnKey server as a NTP host for your cameras. Rereading your post now I should have realized that sooner...

Considering that you've found a solution, this is no doubt irrelevant to you now - but FWIW using TurnKey as a NTP server "just works" for me?! I couldn't find anything specific regarding different networks/interfaces but I also couldn't find anything that suggests it wouldn't respond to any interface either. My tests weren't using multiple network segments, so I guess that must/might be the issue? Regardless, using a 192.168.1.0/24 (or 192.168.1.0 netmask 255.255.255.0) I confirmed that it worked as a ntp server OOTB.

Add new comment