Networking Use pfSense as a NTP Server


(20120219 – This post has been amended to provide better methods for using cron; to provide a slightly modified version of the ntp.conf file; and, to address minor changes resulting from newer versions of software — iceflatline)

(20130912 – This post has been amended so that default ntp.conf files are used in the examples; to address minor changes resulting from newer versions of software; to add an additional command in FreeBSD to perform a one-time NTP sync at system boot when using ntpd; to remove text concerning the command ntpq -p as it no longer appears to work with the NTP server implementation in pfSense; to update the list of software; and, to provide other minor edits — iceflatline)

In a previous post, I described how to install and setup pfSense in a home network. In this post I will describe how to configure pfSense to act as an Network Time Protocol (“NTP”) server and how to configure various hosts in your network to synchronize their local clock to this server.

pfSense (i.e., “making sense of packet filtering”) is a customized version of FreeBSD tailored specifically for use as a perimeter firewall and router, and managed almost entirely from a web-based GUI. In addition to being a firewall and routing platform, pfSense includes a long list of other features, as well as a package system allowing its capabilities to be expanded even further. pfSense is free, open source software distributed under the BSD license.

Originally designed by David L. Mills of the University of Delaware circa 1985, NTP is a protocol for synchronizing the clocks of computer systems over packet-switched, variable-latency data networks, and one of the oldest Internet protocols still in use. NTP uses User Datagram Protocol (UDP) port number 123. pfSense uses OpenNTPD, a free, easy to use implementation of NTP.

The versions for the software used in this post were as follows:

  • FreeBSD 9.1-RELEASE
  • NTP 1:4.2.6.p3+dfsg-1ubuntu3
  • pfSense v2.0.3
  • Ubuntu Desktop v12.04 (x64)
  • Windows 7 Professional (x64)
  • Configure OpenNTPD in pfSense

    Before configuring the OpenNTP server, it’s a good idea to ensure that pfSense itself is keeping accurate time. The best way to do that is to have it synchronize its clock with one or more remote NTP servers. First though, you should make sure that the clock in the machine hosting pfSense is set to something close to accurate – if the difference is too great, pfSense will not synchronize properly with the remote NTP server.

    Login to the pfSense machine using its “webConfigurator” (webGUI) interface. Navigate to System->General Setup and select the timezone that matches the physical location of the pfSense machine from among the options under “Time zone.” Next, enter the host name or IP address for the remote NTP server under “NTP time server.” Remember to add at least one DNS server under System->General Setup->DNS servers if you decide to use a host name instead of an IP address. Most likely you’ll find this field is already populated with one or more default remote NTP server(s) such as,, etc. These servers will work just fine in most cases, however you may get more accurate results if you use one of the continental zone servers (e.g., europe., north-america., oceania., or, and even more accurate time if you choose to use one of the country zone servers (e.g., in the United States). For all of these zones, you can use the 0, 1 or 2 prefix, like, to distinguish between servers from a particular region or country. (See the NTP Pool Project web site for more information on how to use servers). Like, these server entries will pick random NTP servers from a pool of known good ones. Also, while one NTP server is sufficient, you can improve reliability by adding more. Just make sure their host names or IP addresses are separated by a space.

    Now that the pfSense machine is on its way to keeping accurate time, let’s configure its OpenNTPD server. Navigate to Services->NTP and pick which interface OpenNTPD should listen on. This will typically be the “LAN” interface. When complete select “Save.” The OpenNTPD server will start immediately, however there may a delay of several minutes before it is ready to service NTP requests as it must first ensure that its own time is accurate. That’s all there is to it. You’ll find the OpenNTPD logs under by selecting the ‘NTP” tab under Status->System Logs.

    Configure Hosts


    After configuring the OpenNTPD server in pfSense, let’s configure a Windows host to synchronize its local clock to this server. Right-click on the time (usually located in the lower right corner of the desktop) and select “Adjust date/time.” Select the “Internet Time” tab, then select “Change settings.” Check the “Synchronize with an Internet time server” box, enter the host name or IP address of the pfSense machine, then select “Update now.” It’s not uncommon to get error message the first time you attempt to update. Wait a few seconds and try again; you should receive a “The clock was successfully synchronized…” message.


    Most Linux distributions feature two utilities to help the local clock maintain its accuracy: ntpdate and/or ntpd. The ntpdate utility is typically included in Linux distributions as a default package, but if yours does not you can install it using your distribution’s package manager, for example:

    ntpdate typically runs once at boot time and will synchronize the local clock with a default NTP server defined by the distribution. In Ubuntu, for example, this default NTP server is However what if this machine isn’t rebooted often, say in the case of a server for example? And what about using the OpenNTPD server in the pfSense machine? We can address both of those issues by occasionally running ntpdate using the following command. For this and subsequent examples we’ll assume the IP address assigned to the LAN interface in the pfSense machine is

    Perhaps a more effective approach though is to use cron, a *nix utility that allows tasks to be automatically run in the background at regular intervals by the cron daemon. These tasks are typically referred to as “cron jobs.” A “crontab” is a file which contains one or more cron job entries to be run at specified times. You can create a new crontab (or edit an exiting one) using the command crontab -e under your user account. Because ntpdate needs to be run by the system’s root user we’ll create the crontab using the command sudo crontab -e. Here’s some example cron job entries using the ntpdate command. Note that cron will attempt to email to the user the output of the commands it runs. To silence this, you can redirect the command output to /dev/null:

    While using ntpdate will certainly work well, the utility ntpd on the other hand is considerably more sophisticated. It continually runs, calculating the drift of the local clock and then adjusting its time on an ongoing basis by synchronizing with one or more NTP servers. By default ntpd acts as a NTP client, querying NTP servers to set the local clock, however it also can act as a NTP server, providing time service to other clients. Alas though, nothing is free, and using ntpd will result in yet one more system process that may not otherwise be running in your system, consuming both CPU and memory resources, albeit modestly.

    Like ntpdate many Linux distributions include ntpd by default. If yours does not, you can install it using your distribution’s package manager, for example:

    The installation process should add ntpd to the requisite run levels and start its daemon automatically. Now we need to configure it so that it acts as a NTP client only and not as a NTP server. After all, that’s what we’re going to use the pfSense machine for right?

    ntpd is configured using the file /etc/ntp.conf. Open this file and comment out the existing ntp pool servers, then add the IP address assigned to the LAN interface on the pfSense machine. Again, we’ll assume this address is Appending the “iburst” option to the address will provide for faster initial synchronisation. We’ll also want to comment out the NTP server-related options that allow the local machine to exchange time with other host devices on the network and interrogate the local NTP server. The remaining options can remain at their default settings:

    A comment about the driftfile option: this file is used to store the local clock’s frequency offset. ntpd uses this file to automatically compensate for the local clock’s natural time drift, allowing it to maintain reasonably accurate time even if it cannot communicate with the pfSense machine for some period of time.

    While not required, you can run the ntpdate command one time to fully synchronize the local clock with the OpenNTPD server in pfSense, then restart ntpd.


    ntpdate and ntpd are installed in FreeBSD by default, however ntpd is not configured to start at boot time.

    Similar to Linux, we can run ntpdate manually as root to synchronize with the OpenNTP server running in the pfSense machine. Again, we’ll assume is the IP address assigned to the LAN interface on the pfSense machine.

    ntpdate can also be made to run at boot time in FreeBSD by adding the following lines in the file /etc/rc.conf:

    We can also use cron under FreeBSD to run ntpdate. You can create a new crontab (or edit an exiting one) using the command crontab -e as root. The example cron job entries provided above under Linux will also work under FreeBSD.

    To enable ntpd under FreeBSD, open /etc/ntp.conf and comment out the existing ntp pool servers and add the IP address assigned to the LAN interface on the pfSense machine. The remaining options can remain at their default settings:

    Now open /etc/rc.conf as root and add the following two lines. The first line enables ntpd; the second tells the system to perform a one time sync at boot time:

    Run the ntpdate command one time to synchronize the local clock with the OpenNTPD server in pfSense, then start ntpd.


    This concludes the post on how to how to configure your pfSense machine to also act as a NTP server. The OpenNTPD service in pfSense will listen for requests from FreeBSD, Linux and Windows hosts and allow them to synchronize their local clock with that of the OpenNTPD server in pfsense. Using pfSense as a NTP server in your network ensures that your hosts always have consistent accurate time and reduces the load on the Internet’s NTP servers. Configuring Windows hosts to utilize this server is straightforward, while configuration under FreeBSD and Linux involves the use of ntpdate and/or ntpd and requires a bit more work.


    Buechler, C.M. & Pingle, J. (2009). pfSense: The definitive guide. USA: Reed Media

    Tags: , , , , ,

    3 Responses to “Use pfSense as a NTP Server”

    1. leroy jessee Says:

      Ultra great page…….THANKS……..

    2. NTP Configuration in pfSense - pfSense Setup HQ Says:

      […] Use pfSense as an NTP Server – another post from the excellent iceflatline blog. […]

    3. bb271 Says:

      Very helpful. Thanks.

    Leave a Reply