Making Your Magnia a Local NTP Time Server

Installing ntpd

First, make sure ntp rpm is installed.
By default a Magnia does not have ntp installed.
These are the packages and install order:



Your mileage may vary, I got a failed dependencies error when installing ntp.

You may already have libcap installed.

Use RPMFIND.NET or RPM.PBONE.NET to find the packages you need.
You will want packages for REDHAT 7.3

Webmin is the easiest way to install them:

WEBMIN--> System--> Software Packages-->

Browse to the location of your rpm file(s) and install.

Configuration for running ntp as daemon

Now edit the following file:

I use WEBMIN--> Others--> File Manager

Navigate to the file and click on "Edit" in the toolbar.
The only important thing for a CLIENT is the line containing server
I have made the lines you want to check blue. Make sure you use the right LAN subnet.
You might also want to try a different timeserver from the one I've chosen.

# Prohibit general access to this service.
restrict default ignore

# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.

# -- CLIENT NETWORK -------
# Permit systems on this network to synchronize with this
# time service. Do not permit those systems to modify the
# configuration of this service. Also, do not use those
# systems as peers for synchronization.
restrict mask notrust nomodify notrap

# or remove the default restrict line
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.

restrict mask nomodify notrap noquery

#multicastclient # listen on default
# restrict mask notrust nomodify notrap
# restrict mask notrust nomodify notrap

# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
server # local clock
fudge stratum 10

# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /etc/ntp/drift
broadcastdelay 0.008

# Authentication delay. If you use, or plan to use someday, the
# authentication facility you should make the programs in the auth_stuff
# directory and figure out what this number should be on your machine.
authenticate no

# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
# systems might be able to reset your clock at will. Note also that
# ntpd is started with a -A flag, disabling authentication, that
# will have to be removed as well.
keys /etc/ntp/keys

fudge tells the server to pass on the correct time to the given network interface. stratum is the level of time servers, 10 being the lowest. You only need a higher number if you will be acting as a public internet timeserver with fast bandwidth.
You can name multiple servers for the daemon to check time with. Select the best as prefer

server prefer

Make sure you add ntpd as a boot (init) service.
WEBMIN--> System--> Bootup and Shutdown--> NTPD
At the very least you want to go in there and start the server.
You can also check the box there to make the daemon start automatically at boot.
Alternatively you can install the WEBMIN module for NTPD.
WEBMIN--> Webmin--> Webmin Configuration--> Webmin Modules --> From uploaded file
After installation you can access the module from
WEBMIN--> Hardware--> Time Synchronization
The System Time module is available there as well. You can use this module to set up a cron job to automatically adjust the Mangnia's clock. (For those who just want a more accurate Magnia clock, but not a local timeserver) I have been using this utility for quite some time. The Magnia requires about one minute per day adjustment!
I am still playing with the configurations. What I show here comes from faqs I have found elsewhere on the web.
You can verify your timeserver is "serving up" the time by having a NTP CLIENT running on your PC connect to the Magnia NTP server you just started.
CLOCKALIGN from is an excellent program for the Windows environment.


If you are having problems getting your box to sync, you may have a firewall issue.
NTP uses port 123, both UDP and TCP. Make sure this port is not blocked by the firewall.
You can open this port with:

$IPTABLES -A INPUT -j ACCEPT -p tcp --dport 123

Previously known valid and working ntp servers IPV6 ONLY USA USA USA USA USA USA USA USA USA USA USA USA USA USA