OPNsense Forum

English Forums => General Discussion => Topic started by: weust on February 28, 2016, 03:17:56 pm

Title: [SOLVED] Hyper-V and time sync
Post by: weust on February 28, 2016, 03:17:56 pm

I'm reading through some documentation to optimize my home virtual environment.
Running a Hyper-V 2012 R2 Free server which holds several VM's.
One is running OPNsense, another is a Windows Server 2012 R2 Domain Controller.

There is also a physical Windows Server 2012 R2 Domain Controller.
This one is my current Time Server for the domain and other devices to sync their time against.

It is recommended to have virtual Domain Controllers (DC) sync their time to the DC running the "PDC Emulator" role, while other VM's get their time through the "Time synchronization" from the Integration Services provided by Hyper-V host to the Guest VM.
On Linux and FreeBSD VM's this simply means not installing a NTP daemon so the Integration Service keeps the virtual clock in sync with the clock from the host.

One exception it OPNsense. It's config does not allow a blank entry for the "NTP Time Server" option in "General | Settings | System".

Is there a way to work around this, or does a patch need to be made to allow not setting a NTP Time Server?

Title: Re: Hyper-V and time sync
Post by: franco on February 28, 2016, 04:02:41 pm

You can set an unresolvable host name or wait for this commit in 16.1.5...

https://github.com/opnsense/core/commit/0d70b4a9dbde2889063fba177a06f5fb139d87f4

;)

Title: Re: [SOLVED] Hyper-V and time sync
Post by: weust on February 28, 2016, 04:34:38 pm

Awesome :-) Like the description in GitHub too haha