Does anyone know how to stop ntpd to listen to local network interface
changes? That is, I want ntp to listen exclusively to the local GPS/PPS
signal (server 127.127.20.0) and ignore all other network interfaces,
messages, events, etc.
Background:
I'm using ntp on a Linux-based box for accurate ti
configure with appropriate parameters,
that you need for PPS-support anyhow). Then build and install.
At least the one system that we have tested until now performs as expected.
thanks
Joachim
Am 12.06.2015 um 11:37 schrieb Marco Marongiu:
> On 12/06/15 10:07, Joachim Fabini wrote:
>> I wa
uing an ifup command).
As simplest solution you can remove the rights on the file (sudo chmod
000 ntpdate) such that your ntp will no longer lose the time on network
interface status changes.
hope it helps and sorry for the noise,
br Joachim
Am 12.06.2015 um 12:26 schrieb Marco Marongiu:
> On
On 08.09.2015 09:44, Gabs Ricalde wrote:
> I've been running two devices (TPLink WR703N, MR3020) for more than 2
> years with almost no issue. Also impressed on what these devices could
> do. Does the new OpenWRT versions have the PPS driver for AR9331? I had
> to use this for Attitude Adjustment:
Comments inline
On 08.09.2015 13:46, Gabs Ricalde wrote:
> On Tue, Sep 8, 2015 at 5:17 PM, Joachim Fabini
> wrote:
>> On 08.09.2015 09:44, Gabs Ricalde wrote:
>>> I've been running two devices (TPLink WR703N, MR3020) for more than 2
>>> years with almost no
Sandip,
relative synchronization over the wireless link is a mess. I use Linux
desktop systems with GPS/PPS receivers for measuring one-way delay in
mobile setups and it works. Imho any PPS-capable GPS receiver on the
market should satisfy your needs when you integrate it correctly into a
Linux de
eters - perhaps we can improve the accuracy, too.
Thanks again,
Joachim
On 10.09.2015 12:46, Gabs Ricalde wrote:
> On Wed, Sep 9, 2015 at 2:47 PM, Joachim Fabini
> wrote:
>> Comments inline
>>
>> On 08.09.2015 13:46, Gabs Ricalde wrote:
>>> On Tue, Sep 8, 2015 at 5:17
On 14.09.2015 12:43, Hal Murray wrote:
> Joachim Fabini said:
>> - Re-compile your kernel for LinuxPPS support, following the instructions on
>> http://linuxpps.org/wiki/index.php/LinuxPPS_installation .
>
> That hasn't been necessary for a long long time.
Most rec
NTP algorithms rely on symmetric connection delay but DSL delay is
commonly highly asymmetrical. In measurements for my setup (VDSL;
8Mbit/s DL, 768kbit/s UL), the VDSL one-way delay at low packet payload
averages 12ms for DL and 6ms for UL. Very surprising if you consider the
DL/UL capacity ratio
Comments inserted inline below.
> Am 03.12.2015 um 17:46 schrieb Jan Ceuleers :
>
>> On 02/12/15 21:00, Joachim Fabini wrote:
>> NTP algorithms rely on symmetric connection delay but DSL delay is
>> commonly highly asymmetrical. In measurements for my setup (VDSL;
>
> Am 03.12.2015 um 22:10 schrieb Joachim Fabini :
>
> Comments inserted inline below.
>
>>>> Am 03.12.2015 um 17:46 schrieb Jan Ceuleers :
>>>
>>> On 02/12/15 21:00, Joachim Fabini wrote:
>>> NTP algorithms rely on symmetric connection delay bu
Is there any specific reason for insisting on TSIP? I have some
Copernicus II receivers operating accurately using NMEA over a serial
interface at 4800 8N1 on a Linux Desktop. You can change the Copernicus
II output with little effort using Trimble's GPS Studio (Windows PC
required).
One typical pi
Dear all,
does anyone know of a successful deployment of LinuxPPS with newer
kernel (4.4), ntp (4.2.8p?) and PPS over serial interface on x86-based
PCs? Or of any known issues that linuxpps has with such a configuration?
Background: A setup and configuration that has worked reliably over
years on
Hello Brandon,
Which version of ntp is deployed on your system?
Any relevant/suspect output in syslog when restarting ntpd?
What does ntpq report?
First guess: please remember http://bugs.ntp.org/show_bug.cgi?id=3367 -
this was staged (only) for ntp-4.2.8p11. Make sure that either your ntp
has th
14 matches
Mail list logo
