[ntp:questions] Trying to make NTP daemon as one of the Sync source
*Hi all, * *I am trying to implement a system where NTP daemon will be a Sync source like others (GNSS/PTP/NL). * *These all sync sources (GNSS/PTP/NL) provide a CLOCK REPORT based on their accuracy. * *Which consist * - *TimeError, * - *FrequencyError, * - *Time Uncertainty and * - *Frequency Uncertainty.* *Can i get these four parameters in ntpq -pcrl output so that i can implement NTPD as a sync source. presently i am getting the ntpq -pcrl output like below.* *# ntpq -pcrl remote refid st t when poll reach delay offset jitter== 130.107.154.104 .STEP. 16 u- 102400.0000.000 0.000*129.107.154.104 169.254.169.254 3 u1 64 377 280.966 52.995 43.666associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,version="ntpd 4.2.8p5@1.3265-o Thu May 25 19:52:00 UTC 2017 (1)",processor="armv7l", system="Linux/3.10.49-perf", leap=00, stratum=4,precision=-20, rootdelay=282.690, rootdisp=80.613, refid=104.154.107.129,reftime=dcd7cb67.7569a73c Tue, May 30 2017 10:43:51.458,clock=dcd7ccc7.1f2fb0c4 Tue, May 30 2017 10:49:43.121, peer=62203, tc=6,mintc=3, offset=52.994796, frequency=6.065, sys_jitter=0.00,clk_jitter=17.546, clk_wander=6.134Please help in finding these parameter or how can i calculate the above by using the ntpq -pcrl output.Thanks,Akash Saxena* ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] trying to get broadcast to work
> > I'm trying to get broadcasts to work. > > > client 192.168.64.150 > > - > > driftfile /var/lib/ntp/ntp.drift > > > > restrict -4 default kod notrap nomodify nopeer > > restrict -6 default kod notrap nomodify nopeer > > > > restrict 127.0.0.1 > > restrict ::1 > > > > disable auth > > broadcastclient > > > So I wonder: what am I doing wrong? what could be the cause? > > I think you need to remove the nopeer restriction on the client, or > enable authentication (server and client sharing a symmetric key). That's the one! Thanks a lot! ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Only Garbage from Raw DCF
> It looks like you still have some missing pulses, probably due to local > interference. This is a problem here as well, as you saw from my logfile > posting. This thread is pretty old, so just for the record: Note that there's a relatively easy way to judge the quality of DCF77 reception: using your ears :-) The regular pulses are extremely easy to distinguish from any kind of "noise", which presents itself as random "warbling". If all you can hear is the "alien scanner tapping", you've found a nice spot for your antenna. To get your alien scanner going, just plug or "wiretap" the output pulse train of your DCF77 receiver into a speaker. The output itself is too "soft" to drive a passive speaker or earphones, but if you use a powered computer speaker (anything you find lying around), that will have a high-Z line input and will work. Or, you can plug the DCF77 pulse train into the line input of a computer sound card. Note: line in, not microphone in - the signal is too strong for a mic in. I've used this not only for immediate playback, but also for recording. This way I was able to discover ionospheric interferential outages in my reception. Obviously you don't want to sit there listening to hours of DCF77 tapping, but you can use software such as the Spectrum Lab to create an FFT waterfall, which will fit the spectrum of the "audio" for the period of a day onto a single screen of the waterfall diagram. Example spectrum waterfall: http://support.fccps.cz/download/Meinberg/prehled/2012_06_29__around_23-00_UTC_spectrum.png Using some additional circuitry, I was also able to measure the RSSI signal from a Meinberg analog receiver: http://support.fccps.cz/download/Meinberg/prehled/RSSI_UL.png DCF77 is analog HAM fun, especially if you live further away from Frankfurt (a couple hundred km). YMMV. Frank ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] trying to get broadcast to work
On Mon, May 29, 2017 at 09:43:08PM +0200, folkert wrote: > Hi, > > I'm trying to get broadcasts to work. > client 192.168.64.150 > - > driftfile /var/lib/ntp/ntp.drift > > restrict -4 default kod notrap nomodify nopeer > restrict -6 default kod notrap nomodify nopeer > > restrict 127.0.0.1 > restrict ::1 > > disable auth > broadcastclient > So I wonder: what am I doing wrong? what could be the cause? I think you need to remove the nopeer restriction on the client, or enable authentication (server and client sharing a symmetric key). -- Miroslav Lichvar ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
