Related CategoriesCommunity Contributed Virtual Appliance | Production | System Administrator | Other NTP (Network Time) Appliance [Updated 2008_02_04]A hardened appliance, with Windows support, that will communicate with NTP servers around the world to keep current time. Description
New in update: Technical notes: Enable the status page and use Alt-F12 to view ntp peer status. Wait until an asterisk ( * ), plus ( + ), or minus ( - ) symbol appears; about 2 minutes. When this happens, the ntpd process should have configured itself with a proper stratum number and should be able to serve ntp query requests. Description 1. This appliance will attempt to pull random ip addresses from pool.ntp.org (13 + time.nist.gov), synchronize the virtual machine clock, and start the server service for Network Time Protocol (NTP). Having correct time is important for many servers. For example, logs from Intrusion Detection Systems without proper clocks may be thrown out of court as evidence for a crime. Considering Microsoft's Active Directory and Domains, all domain controllers must have their system clocks synchronized in order for "replication" to occur. An unsynchronized domain controller will only be able to provide read-only access to Active Directory objects. Another useful scenario for this virtual appliance is the clock synchronization for all machines. The virtual appliance is able to respond to NTP queries as well as support for the Windows Operating System. Even certain phone or PBX systems, such as Avaya's IP Office, will be able to synchronize the correct time with this appliance. Cost is also a factor. Compare this free virtual machine appliance to other hardware based models. Quoting from http://www.buyntp.com/resources_buying_guide.asp, "A high quality time server costs roughly $3,000 to $10,500, depending on the level of accuracy required." The appliance is setup to be automatic and very little end-user configuration is needed. To increase security, shorewall and iptables is used to harden the appliance, only allowing NTP communications and/or Windows support. 2. Mandrivia Linux 2006 was used for the initial setup of this appliance. Only the base system was installed (no XWindows) and tools were installed for kernel compilation. In order to provide Windows support with the "net time" command, Samba was installed and setup. Throughout the course of development, new Linux kernels were released and the one currently in this appliance is kernel 2.6.16.18. The kernel was custom compiled to reduce size occupied on disk and in memory. VMtools was installed, however vmhgfs was removed since file sharing is not a desirable option. The only other module that can be compiled is vmxnet. After testing, a meticulous process of hand pruning unnecessary files was done. Then an empty virtual machine harddisk was set up to accomodate this final smaller size for the guest operating system. Files were tar'd to a backup virtual disk and untar'd to this new drive to shrink the vmdk file for final submission. A custom menu system was created to aid the end-user in managing this virtual machine, so there should be no reason to enter the "command console." If the end user wishes, a bash console is found in the custom menu. Developed to use the fewest resources, this virtual appliance is configured to only use 24megs of RAM and 100megs of physical hard disk space. 3. An end user should just start the virtual machine normally. The appliance is configured for "first time" setup and will prompt the end user for configuration of the system. 4. Everything in this appliance is open source. Last updated: 02/05/2008 Operating system: Mandrivia Linux 2006 Applications installed: VMware Tools installed: Yes
Size:
28MB MB Primary account Submitted by: kamphor Download link provided by the submitter, not VMware. Report broken downloads here. « BACK... |