Thanks for the replies,
I think I now have the server sending the multicast correctly, using
this:
broadcast 229.1.1.8 ttl 2
I see the packets coming over the satellite using tcpdump:
22:50:05.750313 IP 192.168.1.2.123 > 229.1.1.8.123: NTPv4 bcast, strat
3, poll 6, prec -20
Im running ntpd on the client with this config:
driftfile /var/lib/ntp/ntp.drift
restrict default nomodify nopeer
restrict 127.0.0.1
multicastclient 229.1.1.8
disable auth
It seems that ntpd is listening to the multicast:
root # netstat -na | grep 229.1.1.8
udp 0 0 229.1.1.8:123 0.0.0.0:*
but I don't see the peer come up on he client when I go:
root # ntpq -pn
No association ID's returned
Should I see it as a peer?
I did not expect to see 229.1.1.8 on the server as a peer:
water root # ntpq -pn
remote refid st t when poll reach delay offset
jitter
==============================================================================
+213.205.157.156 129.69.1.153 2 u 25 64 377 7.595 0.466
0.251
*130.159.196.118 131.188.3.222 2 u 34 64 377 19.902 -2.001
0.247
-158.43.128.33 193.67.79.202 2 u 32 64 377 2.892 3.140
0.632
-158.43.128.66 193.67.79.202 2 u 35 64 377 2.844 3.764
0.489
-158.43.192.66 193.79.237.14 2 u 31 64 377 1.978 7.359
0.288
+130.88.202.49 194.81.227.227 2 u 27 64 377 15.726 -3.481
0.427
+130.88.200.98 128.86.8.123 2 u 21 64 377 16.155 -4.333
15.601
229.1.1.8 .MCST. 16 u - 64 0 0.000 0.000
4000.00
Does this look correct?
Danny, you said,
> You can disable auth in the client by adding disable auth to the config
> file. You would need to do it for your case.
does this mean that if I disable auth, the client will not try to
contact the server for authentication, and so there is not a need for
novolley?
many thanks for your time,
Julian
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
