NTP+PPS works just fine on XP/32 and Win7/32.
Here is what i have on ntpq -p
remote refid st t when poll reach delay offset jitter
==
oGPS_NMEA(1) .GPS.0 l 72 16 3600.000
On 09/09/14 06:46, valizade...@gmail.com wrote:
1-Is the not digitally signed normal in screenshots 3??
Almost certainly. There is a cost in being able to create digital
signatures acceptable to Microsoft.
___
questions mailing list
On 09/09/2014 06:46, valizade...@gmail.com wrote:
NTP+PPS works just fine on XP/32 and Win7/32.
Here is what i have on ntpq -p
remote refid st t when poll reach delay offset jitter
==
oGPS_NMEA(1)
On 09/09/2014 07:57, David Woolley wrote:
On 09/09/14 06:46, valizade...@gmail.com wrote:
1-Is the not digitally signed normal in screenshots 3??
Almost certainly. There is a cost in being able to create digital
signatures acceptable to Microsoft.
Strangely, David, I see the same, and yet
Is there a way to compensate for asymmetric delay to/from one specific
peer or server?
My home LAN is connected to my school's network via a cable modem.
There appears to be a consistent asymmetry of 2-3 msec between my home
and the school's network. I can see this by comparing the time on
my
Rich Wales ri...@richw.org wrote:
Is there a way to compensate for asymmetric delay to/from one specific
peer or server?
My home LAN is connected to my school's network via a cable modem.
There appears to be a consistent asymmetry of 2-3 msec between my home
and the school's network. I can
Replying to Rob:
Yes, you can use: fudge 1.2.3.4 time1 -0.002 or similar.
see the manual.
This didn't work. And the following error message appeared in my syslog:
inappropriate address 10.0.229.163 for the fudge command,
line ignored
As best I can tell from the online manual, the
On Tue, Sep 9, 2014 at 5:11 PM, Rich Wales ri...@richw.org wrote:
I checked the manual before asking my question
Good start, so many don't -- even years later.
I might point you at The Huff-n'-Puff Filter but perhaps you could
explain your concern. An error in the small millisecond range is
The issue is that the huff-n-puff filter will work in the case where a
symmetrical delay becomes asymmetric, and it will tolerate or
accommodate an asymmetric delay (caused by a large download, for
example) for some period of time.
This is a case where there is reasonably-understood asymmetry for
