Sorry for the confusion David.
I have two similarly configured situations. The one I posted the
detailed data from was the easiest to physically get to, but had a
slightly different network to what I had described in the original
email. The client machine is connected to a variety of
John Zornig wrote:
Enabled
interface 7: fd=23, bfd=-1, name=eth1, flags=0x19, scope=0
sin=10.1.1.9 bcast=10.1.1.255, mask=255.255.255.0
It's failed to find the interface on which you are listening. Why so
many? Is the target interface real?
I seem to remember there
John Zornig wrote:
The client system is an uptodate Red Hat 5.2 system. The ntp.x86_64
version installed is 4.2.2p1-8.el5
^
That's relatively old. libisc/ifiter_ioctl.c, the most likely source of
the problem on Linux, was updated in December 2006, or later.
On Mon, 20 Oct 2008 22:47:11 GMT, [EMAIL PROTECTED] (John Zornig) wrote:
receive: at 35 10.10.1.9-10.10.9.1 flags 39 restrict 000
receive: at 35 10.10.1.9-10.10.9.1 mode 5 code 6 keyid 0002 len
48 mac 20 auth 2
Your server is adding an MD5 key to the time packet but the client isn't
On 2008-10-20, John Zornig [EMAIL PROTECTED] wrote:
Full ntp.conf file
Are you positive there are no other restrict lines?
logconfig all
restrict 10.10.9.1
restrict 127.0.0.1
These restrict lines drop all restrictions for the listed IP addresses.
They are meaningless
On an isolated network, not connected to the internet, I have a
timeserver appliance connected to GPS which is doing NTP broadcast
across a UDP one way link to the client system I am trying to
configure as a broadcast client.
On the client I have a network interface IPaddr:10.9.2.1
On 2008-10-20, John Zornig [EMAIL PROTECTED] wrote:
On an isolated network, not connected to the internet, I have a
timeserver appliance connected to GPS which is doing NTP broadcast
across a UDP one way link to the client system I am trying to
configure as a broadcast client.
Good!
John Zornig wrote:
Any suggestions on what I have to do to get ntpd to set the time on my
client?
Please provide the output of the following ntpq sub-commands, run on the
client:
peers
assoc
rv 0
rv any association number reported by assoc
If the peers command shows the server, but at
Thanks Steve and David,
On 21/10/2008, at 7:28 AM, Steve Kostecke wrote:
On 2008-10-20, John Zornig [EMAIL PROTECTED] wrote:
On an isolated network, not connected to the internet, I have a
timeserver appliance connected to GPS which is doing NTP broadcast
across a UDP one way link to the
