[j-nsp] Strange xntpd log messages

[Harry Reynolds]

Hmmm. I recall that xntpd needs an IP to bind to, and that lo0 is the
first interface initialized such that a valid (non 127.0.0.1) should
float xntpd's boat.  I suggest you open a case with JTAC.



> -----Original Message-----
> From: Jee Kay [mailto:jeekay at gmail.com] 
> Sent: Thursday, June 23, 2005 6:20 AM
> To: Harry Reynolds
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Strange xntpd log messages
> 
> On 6/23/05, Harry Reynolds <harry at juniper.net> wrote:
> > You might try adding a non-martian address to the loopback 
> interface.
> > Xntpd should bind to that IP and stop logging errors. I 
> expect you may 
> > have to restart routing (or at minimum the xntpd) for the change to 
> > take effect.
> 
> The loopback is in publically routable address space. There 
> are no martians in any part of the configuration. (The router 
> has been through a full reboot since the addition of the Lo interface)
>