Yes, until you start getting ntpd to accept data samples from your SHM
socket nothing will be working there.
So is there a way (something like a very verbose mode) that I can see that NTPD
is reading from the shared memory (and is having problems maybe)? Because in
the log file of NTPD
On Thu, 11 Sep 2014 21:09:46 +, Rob wrote:
Paul tik-...@bodosom.net wrote:
On Thu, Sep 11, 2014 at 2:29 PM, William Unruh un...@invalid.ca wrote:
I doubt that NAT would add much assymetry
NAT is symmetric. Otherwise it wouldn't work. But I don't see how
that's part of anything at
Claudio Persico writes:
Yes, until you start getting ntpd to accept data samples from your SHM
socket nothing will be working there.
So is there a way (something like a very verbose mode) that I can see
that NTPD is reading from the shared memory (and is having problems
maybe)?
Harlan Stenn wrote:
There are a bunch of issues here, and I don't think there is a simple
answer.
For starters, there is static asymmetry and dynamic asymmetry.
One of the core issues is that NTP is frequently multihop, and the
routing for at least some of these connections can spontaneously
William Unruh wrote:
No idea why a fudge parameter would be complicated. If you wanted to use
ntpd itself to figure out the assymmetry, that could well be
complicated. But if it is a fixed offset, I cannot see how that would be
complicated and it ihas already been implimented in the refclock
Rob wrote:
An offset between two GPS synced servers by definition means path asymmetry.
+1
However, path asymmetry includes
- systematic asymmetry (e.g. ADSL) on one ore more (!) parts of the path
between 2 nodes
- errors due to different link speeds, e.g 100 MBit from 1 switch port
to
Martin Burnicki martin.burni...@meinberg.de wrote:
- NAT doesn't hurt at all, unless you are trying to use NTP's authentication
NAT in itself does not hurt, but when you want to be a timeserver for
a large number of clients, it can be a problem.
Many home routers have no static NAT but only
Rob wrote:
Martin Burnicki martin.burni...@meinberg.de wrote:
- NAT doesn't hurt at all, unless you are trying to use NTP's authentication
NAT in itself does not hurt, but when you want to be a timeserver for
a large number of clients, it can be a problem.
Many home routers have no static
Martin Burnicki martin.burni...@meinberg.de wrote:
Rob wrote:
Martin Burnicki martin.burni...@meinberg.de wrote:
- NAT doesn't hurt at all, unless you are trying to use NTP's authentication
NAT in itself does not hurt, but when you want to be a timeserver for
a large number of clients, it
Rob wrote:
Martin Burnicki martin.burni...@meinberg.de wrote:
Rob wrote:
Martin Burnicki martin.burni...@meinberg.de wrote:
When you serve thousands of clients, this tends to overflow the NAT
table or stress the lookup code so much that it overloads the CPU.
Haven't had such case, yet since
On Thu, Sep 11, 2014 at 07:37:10PM +0100, David Taylor wrote:
It has been pointed out to me that this page:
http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver28.html
says: The gpsd man page suggests setting minpoll and maxpoll to 4. That was
an attempt to reduce jitter. The SHM
Terje Mathisen terje.mathi...@tmsw.no wrote:
Rob wrote:
Martin Burnicki martin.burni...@meinberg.de wrote:
Rob wrote:
Martin Burnicki martin.burni...@meinberg.de wrote:
When you serve thousands of clients, this tends to overflow the NAT
table or stress the lookup code so much that it
On Thu, Sep 11, 2014 at 3:50 PM, mike cook michael.c...@sfr.fr wrote:
Yup, AsymmetricDSL does have different up/down bit rates. What I really
meant was that the difference would not explain his issue.
ex: with a 12Mbps down rate and 1.3Mbps up rate, the ratio is around 40usec
to 300usec
See flag4 in driver28.html, and then collect and look at the clockstats
in the statsdir.
Ok there are my progresses:
I've updated my ntp.conf file following the suggestion that you gave me:
#
enable stats
statistics clockstats peerstats loopstats rawstats sysstats
statsdir
On 12/09/2014 13:01, Phil W Lee wrote:
[]
Yes, upgrading windoze to *NIX (FreeBSD for preference, with PPS_SYNC
enabled in the kernel).
Is there much difference now between FreeBSD and Linux in terms of NTP
and the precision with which its timekeeping is done?
--
Cheers,
David
Web:
Paul tik-...@bodosom.net wrote:
On Fri, Sep 12, 2014 at 4:03 AM, Martin Burnicki
martin.burni...@meinberg.de wrote:
+1
However, path asymmetry includes
I think you're abusing the conventional notion of asymmetric latency.
Uncorrected bandwidth asymmetry will result in offsets between
Claudio Persico cloudd...@gmail.com wrote:
I've set-up my application to write in the shared memory a very old time
(15th of May) just to see if the system time will be canged, but nothing
happened.
That is not going to work!
ntpd will reject that kind of wrong time.
Try with a time within
On Fri, Sep 12, 2014 at 11:48 AM, Rob nom...@example.com wrote:
No, not link-speed asymmetry but propagation-time asymmetry
Sure, you can say that after the fact. Only one other person in this
conversation *particularly, not the OP* meant that. As I said the
conventional notion of asymmetric
18 matches
Mail list logo
