Date: Sat, 15 Aug 2015 14:27:10 -0400 From: "Michael B. Eichorn" <ike@michaeleichorn.com> To: Christian Weisgerber <naddy@mips.inka.de>, freebsd-stable@freebsd.org Subject: Re: 10.2: ntp update breaks DCF77 clock Message-ID: <1439663230.5785.15.camel@michaeleichorn.com> In-Reply-To: <slrnmsunlo.104l.naddy@lorvorc.mips.inka.de> References: <slrnmsunlo.104l.naddy@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sat, 2015-08-15 at 15:46 +0000, Christian Weisgerber wrote: > I have a little Soekris box whose ONLY task is to get the time from > a simple DCF77 time signal receiver and redistribute it with NTP. > The update from 10.1 to 10.2 has broken this functionality. > > The relevant ntp.conf configuration... > > server 127.127.8.0 mode 14 > fudge 127.127.8.0 time1 0.235 > > ... now results in the obscure error message: > > PARSE receiver #0: parse_start: parse_setfmt() FAILED. > > The ntp code is not very transparent, but I think the root cause > are the ntp/config.h changes that came with the 4.2.8p3 update. A > number of previously disabled obscure clock drivers were enabled, > but crucially CLOCK_RAWDCF was disabled, and this is the PARSE > subdriver needed to use the popular DCF77 serial receivers. > > Frankly, it looks like we used to have a carefully considered > selection of clock drivers which has been blindly splattered with > the upstream defaults in the last update. > > I don't know how to proceed here. The system ntpd is broken. The > ntpd in ports also doesn't enable this clock type by default, so > no package. The whole raison d'être for this setup was to have a > maintenance-free NTP server that does not require custom compiling > ntpd. *sigh* > Dunno as to what happened with ntp or how to fix it, but there are a couple other ntp soultions in ports that might work. NTP is known to be very complex, IIRC phk@ is being paid by the Linux Foundation to write a replacement, ntimed. While there has not yet been an official release ntimed is in ports. Another option is OpenNTPD from OpenBSD, the portable version of this is in ports as well. I have no idea if they will work any better with your receiver, but since they are completely separate implementations they might be worth a try. Not really an expert here, you mentioned trying the ntp port, and I was aware of these two alternative implementations. [-- Attachment #2 --] 0 *H 010 `He 0 *H 000]0 *H 01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 150613202446Z 160614003550Z0H1 0 U ike@michaeleichorn.com1%0# *H ike@michaeleichorn.com0"0 *H 0 UՀ,k9D %Z|Y6J<rrK g;&|uNlUE9)V.[ט̊:qS](#v SYDz* CpugYݔ,v<`j(w aS#ڒ6n(K5'KVLåErv< J=[}W bLA%gޭnVb| I?M7D :$׃bM_T[,ƃ\ 00 U 0 0 U 0 U %0++0 U jj: γ+39啖0 U #0Sr풜\|~5NԸQ0!U 0ike@michaeleichorn.com0LU C0?0; +70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U /0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U 0http://www.startssl.com/0 *H x+ȐF}pw.X vF?rg P]EOp)L˻yA ;hi0u2]m [Sbp$_ gr Xm*YP3 #H>mKAǠt)HO|=@} 3ӝ'iO81> 03 v'h5U "H;ECZtpҗ4rWHu^6+i*kJL8shAV|5;?HMc\ j[j|+000]0 *H 01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 150613202446Z 160614003550Z0H1 0 U ike@michaeleichorn.com1%0# *H ike@michaeleichorn.com0"0 *H 0 UՀ,k9D %Z|Y6J<rrK g;&|uNlUE9)V.[ט̊:qS](#v SYDz* CpugYݔ,v<`j(w aS#ڒ6n(K5'KVLåErv< J=[}W bLA%gޭnVb| I?M7D :$׃bM_T[,ƃ\ 00 U 0 0 U 0 U %0++0 U jj: γ+39啖0 U #0Sr풜\|~5NԸQ0!U 0ike@michaeleichorn.com0LU C0?0; +70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U /0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U 0http://www.startssl.com/0 *H x+ȐF}pw.X vF?rg P]EOp)L˻yA ;hi0u2]m [Sbp$_ gr Xm*YP3 #H>mKAǠt)HO|=@} 3ӝ'iO81> 03 v'h5U "H;ECZtpҗ4rWHu^6+i*kJL8shAV|5;?HMc\ j[j|+040 0 *H 0}1 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o -we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U 00U 0 U Sr풜\|~5NԸQ0 U #0N @[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[U T0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u +70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^ #wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0& ;@#13qۑ& ̢o 6r_;GO>*I( 74XS1r3)!LJy6Kotˆ# _wSr ;B ADp(fs 䰷6%.W0J3:bC<8t X1<Cn=t==wST~\wkBf|15zUP)(IjVB!OfI=bb\4-*em/нSJm7N[]'@ڽ D9Kr>R7/|o^I@ټ'Pa $ z9a'L)( I}vcH]۸D*W} m>Q|C.(,lQ10001 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA]0 `He 0 *H 1 *H 0 *H 1 150815182710Z0O *H 1B@D{Z2%xEi#ҬIV+ţ5l2Մ1{r=K: Ace;d0 +71001 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA]0 *H 101 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA]0 *H Ge+OQޒ".0! S]Λ#pqz .FN2p4k'E*7{eghvkK8($(`\&F 1ky|2W>, ¿b9nv:ph;zFKj+S!+\ %ϽV{]q@bW*o*:9](s*v*/7LCg?SR3RzW nF t۲j9 #ƿN)t>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1439663230.5785.15.camel>