On 2011-09-15, Samuel Nyarko <[email protected]> wrote: > I am currently working on time synchronisation in wireless sensor > networks. I am using meinberg ntp software but i am having some small > complications about ntp time server. It does not provide time to the > clients and i dont know why such is happening. > > Below is the ntp configuration file
[snip: comment lines elidded] > server 127.127.1.1 > fudge 127.127.1.1 stratum 12 > driftfile "C:\Program Files\NTP\etc\ntp.drift" > multicastclient 224.0.1.1 > broadcastdelay 0.008 > broadcastclient > peer ns1.savonia.fi > peer ntp.a-lab.fi iburst > restrict 127.0.0.1 > restrict 192.168.3.189 > restrict 192.168.0.0 > server 192.168.3.100/24 > restrict 192.168.3.100 mask 255.255.255.255 nomodify notrap noquery > restrict 192.168.3.100 mask 255.255.255.0 nomodify notrap > restrict 192.168.3.101 mask 255.255.255.0 nomodify notrap > server 0.fi.pool.ntp.org minipoll 10 iburst > server 1.fi.pool.ntp.org minpoll 10 iburst > enable stats > statsdir "C:\Program Files\NTP\etc\" > statistics loopstats [snip] remote refid st t when poll reach delay offset jitter ====================================================================== > LOCAL(1) LOCL 12 l 11 64 007 0.000 0.000 0.001 > 193.167.78.100 194.1.. 2 u 9 64 007 0.779 -16.005 3.750 > *212.213.168.140 130.1.. 2 u 11 64 007 15.474 -19.101 3.175 > +80.75.100.83 212.6.. 3 u 122 1024 001 8.805 -20.678 0.454 [lines condensed for 80 cols and converted to original (i.e. unix) format] Can you post the ntpq -p output from one of your clients? -- Steve Kostecke <[email protected]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
