@LamaZ This looks to have been going on for many years glad it made it. Secure Time!! Quizzes, Tests, Exams, etc all are now a bit more secure.

@RobbieTT I kind of like Windows it was a big upgrade over MSDOS 3.11 or DOSSHELL. But really it's like non stop Azure use even for home use now. Windows ME had pinball

@RobbieTT said in NTP = Amateur:

At £4000 to £5000

Pro is anti-cheap. 😊

@JonathanLee sorry if I wasn't clear. No, one URL should be enough

@LamaZ thank you for the code and figuring this out, I learned my first GitHub pull and fork also with this.

@marco-42 Welcome

Proxmox with a FreeBSD guest
Proxmox recommends using ntpd daemon in a FreeBSD client to maintain client real time synchronization. See pve.proxmox. com/wiki/FreeBSD_Guest_Notes and forum.proxmox. com/threads/time-drift-in-windows-7-guest.41268/#post-198848

Real time is set in the guest when it first starts. After which the guest clock drifts with the hosts processor crystal.

ntpd is the ntp daemon. See www.freebsd. org/cgi/man.cgi?query=ntpd&apropos=0&sektion=8&manpath=FreeBSD+12.2-stable&arch=default&format=html

Configured via /etc/ntp.conf

Command line interface ntpq See www.freebsd. org/cgi/man.cgi?query=ntpq&sektion=8&apropos=0&manpath=FreeBSD+12.2-RELEASE+and+Ports

11 minute hardware real time clock update can be enable by adding the line "SYNC_HWCLOCK=yes" to /etc/sysconfig/ntpdate

date gives time of day to 1 second resolution

Qemu guest agent
I think qemu can also sync time between the guest and Porxmox host.

Doing so is suggested github. com/aborche/qemu-guest-agent/blob/master/supported_command_reference.md

Other virtualization systems such as vmware have time synchronization between host and guest via the agent

Time synchronization should be done via only one system otherwise interaction between them decreases time system accuracy. Which mean if an agent and ntpd is used then there would need to be a way of disabling time synchronization via the agent. I'm not sure how to do this.

pfsense guest on Proxmox host
Given it is probably best to run ntp (chrony) on Proxmox then synch time in pfsense to the Proxmox host via ntpd over the LAN interface. Ideally I would like to do the following but not sure how to acheive that in pfsense

Enable ntpd on pfsense but not listening to clients on any interface. Selecting no interfaces in the GUI does the reverse.

Disable hardware real time clock update by pfsense. This is done every 11 minutes by chronyd on the Proxmox host. In pfsense the directory structure is different, so I can't goto to /etc/sysconfig/ntpdate and set SYNC_HWCLOCK=no

@Yo5hi said in NTP not syncing with clients:

I just wish that my devices don't have to wait 60-80 secs on boot to sync.

So, it boots, asks the time ones - got it, and sets it's own clock, and wants be sure and checks up a second time. It pauses the entire system while waiting for that ??

No RTC, bad NTP implementation ... hummm.

Thanks for the replies. I installed ChronyControl on both my Macs and disabled the inbuilt NTP client and it seems to be working. Unfortunately I don't have enough time to investigate it all much further now, and in any case I like the functionality that ChronyControl brings so will stick with that for now.

Thanks again Derelict for your valuable insights

I did see the Startech cards when I was searching for a good fit, and I am now ruing that I didn't order one. It looks like I have done my dough $$$ on the card I now have...

Your are absolutely correct - I didn't think it would be so hard to get things working.

This was supposed to be my cheap and economical to run setup.

I have a second machine with a Core i5 2500 (95W) that just chews the gas, but the MB has all the goodies integrated...

Looks like it's back to the drawing board lol

Mmm, I agree it seems odd. Have you been able to test it in FreeBSD directly?

If it is something we are doing in pfSense we could dig into it but if it's something FreeBSD does it would need to be reported upstream really.

Steve

attached two trace, one of my ntp local server and one of pfsense box with the same server configured.

1_1531170243257_pfsense.pcap 0_1531170243256_local.pcap