Now it is ntpd that can't find anything

[jekillen]

On Nov 1, 2007, at 11:18 AM, N.J. Thomas wrote:

> * <jekillen at prodigy.net> [2007-10-31 16:08:10 -0800]:
>>>> I set up ntpd on FreeBSD 6.2 and am getting complaints from ntpd
>>>> that there is no route to such and such address. It gives what
>>>> appears to be an interface card address.
>>
>> ntpq -p
>>      remote           refid      st t when poll reach   delay    
>> offset  jitter
>> ====================================================================== 
>> ========
>>  2610:1f8:d8:2:2 .INIT.          16 u    -   64    0    0.000     
>> 0.000 4000.00
>>  2001:4830:1210: .INIT.          16 u    -   64    0    0.000     
>> 0.000 4000.00
>>  hydrogen.cert.u 164.67.62.194    2 u   10   64    3   13.909   
>> -261.61   2.936
>>  pubts2-sj.witim 64.125.78.85     2 u    8   64    3   20.023   
>> -256.60   2.883
>>
>> Here are the console messages:
>> ntpd (706) send to(2610:1f8:d8:2:216:cbff:fea3:4b2e:) no route to host
>>   "       "         "       (2001:4830:1210:0;280:10ff:fe00:48b9)   "
>>
>> are these ipv6 addresses? Or are they expecting authentication and
>> refusing connections?
>
> The last two time servers seem to be communicating fine with your ntp
> daemon. The bad ones look like IPv6 sites to me. What time servers do
> you have listed in your ntp.conf file?
>
> What is the output of "grep -i server /etc/ntp.conf"?
>
These are the servers I have listed:
server lain.ziaspace.com
#server ntp2.sf-bay.org
server reva.ziaspace.com
server hydrogen.cert.ucr.edu
server pubts2-sj.witime.net
The one commented out was not responding to ping.
I suppose I should find ones that are reachable via ipv4.
Jeff K