[j-nsp] Strange xntpd log messages

[Harry Reynolds]

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. 

HTHs
	
 

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Jee Kay
> Sent: Wednesday, June 22, 2005 11:37 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Strange xntpd log messages
> 
> I'm getting a lot of messages like these in my logs from two M7is:
> 
> xntpd[17536]: bind() fd 23, family 2, port 123, addr 
> 10.0.0.1, in_classd=0 flags=0: Can't assign requested address
> 
> The address 10.0.0.1 isn't anywhere in the router's config 
> and my googling skills are failing to produce an answer, only 
> the same question from others.
> 
> Does anyone know what is causing this and how to stop it? 
> Other queries seem to have concluded it is some internal 
> Juniper addressing that can't be changed (wonder what would 
> happen if 10.0.0.1 was the address of my real NTP server?) - 
> if so, does anyone know what specific logging option is 
> causing this to be logged so I can turn it off? :)
> 
> Thanks,
> Ras
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>