For introducing as direct peer, do I need to add like: peer 192.168.17.22 ?
ntpq -c "rv 0 version" output : assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart, version="ntpd [email protected] Tue Apr 19 07:08:18 UTC 2011 (1)" BTW, I didn't quite get what you mean by: "automatic server discovery scheme in mesh configuration" ? Thanks, Ali On Wed, May 23, 2012 at 11:36 PM, Dave Hart <[email protected]> wrote: > On Thu, May 24, 2012 at 3:22 AM, Ali Nikzad <[email protected]> wrote: > > #ntp.conf > > #ip: 192.168.17.11 > > driftfile /etc/ntp.drift > > server 192.168.17.22 > > > tos cohort 1 orphan 11 > > restrict source nomodify > > restrict default kod notrap nomodify nopeer noquery > > restrict 127.0.0.1 > > > > #ntp.conf > > #ip: 192.168.17.22 > > > > driftfile /etc/ntp.drift > > server 192.168.17.11 > > tos cohort 1 orphan 11 > > restrict source nomodify > > restrict default kod notrap nomodify nopeer noquery > > restrict 127.0.0.1 > > > > But they are still not synchronized. > > Alternatively you can use an automatic server discovery scheme in mesh > configuration. For orphan mode to operate as intended, all > participants must see all others as direct peers. > > If it goes well, one host will show refid LOCL and stratum 11, the > others will all be stratum 12. If it doesn't work, please show ntpq > -c "rv 0 version" output. > > Cheers, > Dave Hart > _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
