From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3790 invoked by alias); 25 Feb 2003 14:30:52 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 3771 invoked from network); 25 Feb 2003 14:30:51 -0000 Date: Tue, 25 Feb 2003 14:30:00 -0000 From: Andrew Lunn To: Gary Thomas Cc: eCos Maintainers Subject: Re: FWD: SNTP client package Message-ID: <20030225143038.GA14575@biferten.ma.tech.ascom.ch> References: <20030225094253.GA11159@biferten.ma.tech.ascom.ch> <1046181499.21674.2070.camel@hermes.chez-thomas.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1046181499.21674.2070.camel@hermes.chez-thomas.org> User-Agent: Mutt/1.4i X-Filter-Version: 1.6 (rubicon) X-SW-Source: 2003-02/txt/msg00051.txt.bz2 > It looks reasonable to me. Feel free to check in in - trunk only. > I assume that you [Ascom] wrote it yourself? Yep, i wrote it. > Also, I'd like to test it. Great. Do you have a big endian system? I only have little endian. > Can you give some hints on how to set up a NTP server locally? There is a lot of documentation at www.ntp.org I run debian. They ship two ntp server packages. These are ntp-simple and ntp-refclock. If you have network access, use ntp-simple and add a server x.x.x.x line to ntp.conf. You can find public servers at http://www.eecis.udel.edu/~mills/ntp/clock2a.html. If you don't have access to a server, you need ntp-refclock. You can then use a reference clock connected to your computer. The simplest, and least accurate, is to use the built in clock set to wallclock time. To do that you need to add a line server 127.127.1.1 to the configuration. You then need to configure it to send out broadcasts. You do this per interface by adding a line broadcast 192.168.9.255, where the IP address is the IP broadcast address. I found it did not start broadcasting imeadiately. I think it waits until its got a degree of synchronization to the source clock. Use tcpdump to see if its doing anything. Once its running, you should see a broadcast every 64 seconds. The test program in the packet will then run and should pass. Andrew