Hi all,
I’m trying to setup a system which connects to multiple NTP server with
symmetric key authentication.
For testing, I’m creating my own NTP servers and client taking help from this
link. https://access.redhat.com/solutions/393663
I’m using SHA1 as the type of authentication.
While I was
Am 05.06.2020 um 09:53 schrieb ah@***.ru:
пятница, 5 июня 2020 г., 10:25:24 UTC+3 пользователь Uwe Klein написал:
Am 05.06.2020 um 08:36 schrieb ah@***.ru:
This sounds more like bit errors in serial reception.
( i.e errors coming up in all magnitudes.)
That is reception via NMEA?
do you
Am 05.06.2020 um 00:10 schrieb a...@avtodoria.ru:
The typical
behaviour in case of time jump is that suddenly we have time in
gpspipe jumped forth or back for [some seconds - some years].
This sounds more like bit errors in serial reception.
( i.e errors coming up in all magnitudes.)
That is
пятница, 5 июня 2020 г., 10:25:24 UTC+3 пользователь Uwe Klein написал:
> Am 05.06.2020 um 08:36 schrieb ah@***.ru:
> >> This sounds more like bit errors in serial reception.
> >> ( i.e errors coming up in all magnitudes.)
> >
> >> That is reception via NMEA?
> >> do you check the NMEA checksum (
> What is the wrong data? Ie, how much of an offset does the wrong data
> imply?
> What does wrong data mean? Do you mean that the PPS is wrong? that of
> course has no time attached so can be wrong by only up to 1 second.
> Or do you mean that the time reported by the NMEA sentences is wrong?
>
Hi,
I've tried searching with google to try and find an answer to my
question, but have failed, so I thought I would try asking here.
I've been running ntp for a long time under Linux, relying on ntpd
getting time over my DSL connection, and it has done pretty well.
The DSL is rather symmetric -
пятница, 5 июня 2020 г., 10:04:44 UTC+3 пользователь William Unruh написал:
> On 2020-06-05, a...@avtodoria.ru wrote:
> >> This sounds more like bit errors in serial reception.
> >> ( i.e errors coming up in all magnitudes.)
> >
> >> That is reception via NMEA?
> >> do you check the NMEA checksum
Hello!!
I have time jumps made by ntpd because gpsd sometimes puts wrong data to SHM
because of wrong data from gps receiver(very bad chips)
I have only one time source in ntp.conf — 127.127.28.1 with PPS enabled
I want to add another two internet sources for stability but at first i want to
> This sounds more like bit errors in serial reception.
> ( i.e errors coming up in all magnitudes.)
> That is reception via NMEA?
> do you check the NMEA checksum ( Portion after * afair)?
Thank you for response. Yes, that is reception via NMEA. No i didn't check
checksum, i think gpsd should
On 2020-06-05, a...@avtodoria.ru wrote:
>> This sounds more like bit errors in serial reception.
>> ( i.e errors coming up in all magnitudes.)
>
>> That is reception via NMEA?
>> do you check the NMEA checksum ( Portion after * afair)?
>
> Thank you for response. Yes, that is reception via NMEA.
10 matches
Mail list logo
