Re: [chrony-dev] SW/HW timestamping on Linux

[Denny Page]

Btw, it might be good for Chrony to support configuration for corrections 
similar to what is discussed in that thread:

  delayAsymmetry - corrects for any asymmetry between the Rx and Tx paths
  egressLatency  - corrects the transmit latency at the MAC/PHY
  ingressLatency - corrects the receive latency at the MAC/PHY

Denny


> On Dec 13, 2016, at 23:21, Miroslav Lichvar  wrote:
> 
> [1] https://sourceforge.net/p/linuxptp/mailman/message/34782351/


--
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Re: [chrony-dev] SW/HW timestamping on Linux

[Denny Page]

Interesting! I would not have thought of this. Both the i211 and i354 have the 
SDP pins. Not exactly a pre-made PPS input, but possible with some soldering 
and some code.

Denny


> On Dec 13, 2016, at 23:21, Miroslav Lichvar  wrote:
> 
> On Tue, Dec 13, 2016 at 05:03:15PM -0800, Denny Page wrote:
>> Unfortunately, I’ve not yet received any response on the Intel list. While 
>> it’s quite clear that both the i211 and i354 require some compensation, I 
>> don’t have a good way to determine it other than by shots in the dark. The 
>> i211 seems to correspond with the i210 correction parameters, so I am 
>> currently using those for the i210, but the i354 is completely different. 
>> Still at it.
> 
> Do you know if the i211 or i354 has a PPS input? i210 does have one
> [1]. I have not had a chance to try it yet. If you could connect it to
> the LeoNTP unit, maybe you could measure the difference between errors
> in TX and RX timestamping, and with direct connection to the server
> maybe even estimate the absolute value of the TX/RX corrections.
> 
> [1] https://sourceforge.net/p/linuxptp/mailman/message/34782351/


--
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Miroslav Lichvar]

On Wed, Dec 14, 2016 at 05:07:11PM +0100, Miroslav Lichvar wrote:
> I found the following commit, which would explain the problem:
> 
> https://github.com/freebsd/freebsd/blob/3fa64907439c00965fb0cbb222a6bf073c452630/lib/libc/gen/recvmmsg.c

Ehm, this is the actual commit
https://github.com/freebsd/freebsd/commit/3fa64907439c00965fb0cbb222a6bf073c452630

> Is it safe to assume this will be included in FreeBSD 11.1?

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

RE: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Bill Unruh]

On Wed, 14 Dec 2016, Adri Koppes wrote:


Bill,

If you read the original message, chrony 2.4.1 is running without problems.

This implies the network is working, name resolutions is fine and the firewall 
isn't blocking stuff.
I am the network and systems administrator, so I know it's ok!
The test with chrony 3.0-pre1 is also using the same /etc/chrony.conf.


OK, sorry to have made a silly observation. I note that Miroslav seems to have 
found the
problem.



Adri.



-Original Message-
From: Bill Unruh [mailto:un...@physics.ubc.ca]
Sent: woensdag 14 december 2016 16:58
To: chrony-dev@chrony.tuxfamily.org
Subject: Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from
socket on FreeBSD



William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_
www.theory.physics.ubc.ca/

On Wed, 14 Dec 2016, Adri Koppes wrote:



Miroslav,



I have chronyd 2.4.1 running on FreeBSD 11.0 release and it’s working fine.

All refclocks are internet servers and data is received normally.

I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp

data from the internet refclocks.


I tried again with the latest master from git and it fails in the same
way,

This is some debug output from the git master version and it seems
there is an almost immediate timeout on both send and receiving data

from any socket.


This may be a silly question, but are you sure you have networking working.
Can you browse with a browser for example.
Are you sure your firewall will let you send and receive ntp packets?






2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
timeout for [194.171.167.130:123]

2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to
194.171.167.130:123 from [UNSPEC] fd 7

2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
from 194.171.167.130:123 to [UNSPEC] fd=7
if=-1 tss=1 delay=0.000104191

2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
timeout for [80.94.65.10:123]

2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to
80.94.65.10:123 from [UNSPEC] fd 8

2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
from 80.94.65.10:123 to [UNSPEC] fd=8 if=-1
tss=1 delay=0.99536



If there is anything I can do to test or provide more information, please let

me know.





 > Adri,.








--
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

RE: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Adri Koppes]

Bill,

If you read the original message, chrony 2.4.1 is running without problems.

This implies the network is working, name resolutions is fine and the firewall 
isn't blocking stuff.
I am the network and systems administrator, so I know it's ok!
The test with chrony 3.0-pre1 is also using the same /etc/chrony.conf.

Adri.


> -Original Message-
> From: Bill Unruh [mailto:un...@physics.ubc.ca]
> Sent: woensdag 14 december 2016 16:58
> To: chrony-dev@chrony.tuxfamily.org
> Subject: Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from
> socket on FreeBSD
> 
> 
> 
> William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
> Physics _|___ Advanced Research _| Fax: +1(604)822-5324
> UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
> Canada V6T 1Z1 | and Gravity __|_
> www.theory.physics.ubc.ca/
> 
> On Wed, 14 Dec 2016, Adri Koppes wrote:
> 
> >
> > Miroslav,
> >
> >
> >
> > I have chronyd 2.4.1 running on FreeBSD 11.0 release and it’s working fine.
> >
> > All refclocks are internet servers and data is received normally.
> >
> > I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp
> data from the internet refclocks.
> >
> > I tried again with the latest master from git and it fails in the same
> > way,
> >
> > This is some debug output from the git master version and it seems
> > there is an almost immediate timeout on both send and receiving data
> from any socket.
> 
> 
> This may be a silly question, but are you sure you have networking working.
> Can you browse with a browser for example.
> Are you sure your firewall will let you send and receive ntp packets?
> 
> 
> >
> >
> >
> > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
> > timeout for [194.171.167.130:123]
> >
> > 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to
> > 194.171.167.130:123 from [UNSPEC] fd 7
> >
> > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
> > from 194.171.167.130:123 to [UNSPEC] fd=7
> > if=-1 tss=1 delay=0.000104191
> >
> > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit
> > timeout for [80.94.65.10:123]
> >
> > 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to
> > 80.94.65.10:123 from [UNSPEC] fd 8
> >
> > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes
> > from 80.94.65.10:123 to [UNSPEC] fd=8 if=-1
> > tss=1 delay=0.99536
> >
> >
> >
> > If there is anything I can do to test or provide more information, please 
> > let
> me know.
> >
> >
> >
>   > Adri,.
> >
> >
> >
> >
> >

--
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Miroslav Lichvar]

On Wed, Dec 14, 2016 at 04:57:49PM +0100, Miroslav Lichvar wrote:
> On Wed, Dec 14, 2016 at 03:34:30PM +, Adri Koppes wrote:
> > Miroslav,
> > 
> > I have chronyd 2.4.1 running on FreeBSD 11.0 release and it's working fine.
> > All refclocks are internet servers and data is received normally.
> > I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp 
> > data from the internet refclocks.
> > I tried again with the latest master from git and it fails in the same way,
> > This is some debug output from the git master version and it seems there is 
> > an almost immediate timeout on both send and receiving data from any socket.
> > 
> > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout 
> > for [194.171.167.130:123]
> > 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
> > 194.171.167.130:123 from [UNSPEC] fd 7
> > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
> > 194.171.167.130:123 to [UNSPEC] fd=7 if=-1 tss=1 delay=0.000104191
> > 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout 
> > for [80.94.65.10:123]
> > 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
> > 80.94.65.10:123 from [UNSPEC] fd 8
> > 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
> > 80.94.65.10:123 to [UNSPEC] fd=8 if=-1 tss=1 delay=0.99536
> > 
> > If there is anything I can do to test or provide more information, please 
> > let me know.
> 
> Hm, I have it working on FreeBSD 10.1. I guess it might be related to
> the new support for recvmmsg(). Do you see 'HAVE_RECVMMSG 1' in
> config.h after running ./configure? If yes, can you remove that line
> from config.h, recompile chronyd, and see if it works?

I found the following commit, which would explain the problem:

https://github.com/freebsd/freebsd/blob/3fa64907439c00965fb0cbb222a6bf073c452630/lib/libc/gen/recvmmsg.c

Is it safe to assume this will be included in FreeBSD 11.1?

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Miroslav Lichvar]

On Wed, Dec 14, 2016 at 03:34:30PM +, Adri Koppes wrote:
> Miroslav,
> 
> I have chronyd 2.4.1 running on FreeBSD 11.0 release and it's working fine.
> All refclocks are internet servers and data is received normally.
> I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp 
> data from the internet refclocks.
> I tried again with the latest master from git and it fails in the same way,
> This is some debug output from the git master version and it seems there is 
> an almost immediate timeout on both send and receiving data from any socket.
> 
> 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout for 
> [194.171.167.130:123]
> 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
> 194.171.167.130:123 from [UNSPEC] fd 7
> 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
> 194.171.167.130:123 to [UNSPEC] fd=7 if=-1 tss=1 delay=0.000104191
> 2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout for 
> [80.94.65.10:123]
> 2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
> 80.94.65.10:123 from [UNSPEC] fd 8
> 2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
> 80.94.65.10:123 to [UNSPEC] fd=8 if=-1 tss=1 delay=0.99536
> 
> If there is anything I can do to test or provide more information, please let 
> me know.

Hm, I have it working on FreeBSD 10.1. I guess it might be related to
the new support for recvmmsg(). Do you see 'HAVE_RECVMMSG 1' in
config.h after running ./configure? If yes, can you remove that line
from config.h, recompile chronyd, and see if it works?

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Re: [chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Bill Unruh]

William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/

On Wed, 14 Dec 2016, Adri Koppes wrote:



Miroslav,

 

I have chronyd 2.4.1 running on FreeBSD 11.0 release and it’s working fine.

All refclocks are internet servers and data is received normally.

I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp data 
from the internet refclocks.

I tried again with the latest master from git and it fails in the same way,

This is some debug output from the git master version and it seems there is an 
almost immediate timeout on both
send and receiving data from any socket.



This may be a silly question, but are you sure you have networking working.
Can you browse with a browser for example. 
Are you sure your firewall will let you send and receive ntp packets?





 

2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout for 
[194.171.167.130:123]

2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
194.171.167.130:123 from [UNSPEC] fd 7

2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
194.171.167.130:123 to [UNSPEC] fd=7
if=-1 tss=1 delay=0.000104191

2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout for 
[80.94.65.10:123]

2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
80.94.65.10:123 from [UNSPEC] fd 8

2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
80.94.65.10:123 to [UNSPEC] fd=8 if=-1
tss=1 delay=0.99536

 

If there is anything I can do to test or provide more information, please let 
me know.

 


 > Adri,.


 

[chrony-dev] Chrony 3.0-pre1 fails to send or receive data from socket on FreeBSD

[Adri Koppes]

Miroslav,

I have chronyd 2.4.1 running on FreeBSD 11.0 release and it's working fine.
All refclocks are internet servers and data is received normally.
I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp data 
from the internet refclocks.
I tried again with the latest master from git and it fails in the same way,
This is some debug output from the git master version and it seems there is an 
almost immediate timeout on both send and receiving data from any socket.

2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout for 
[194.171.167.130:123]
2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
194.171.167.130:123 from [UNSPEC] fd 7
2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
194.171.167.130:123 to [UNSPEC] fd=7 if=-1 tss=1 delay=0.000104191
2016-12-14T15:25:22Z ntp_core.c:1056:(transmit_timeout) Transmit timeout for 
[80.94.65.10:123]
2016-12-14T15:25:22Z ntp_io.c:830:(NIO_SendPacket) Sent 48 bytes to 
80.94.65.10:123 from [UNSPEC] fd 8
2016-12-14T15:25:22Z ntp_io.c:668:(process_message) Received 0 bytes from 
80.94.65.10:123 to [UNSPEC] fd=8 if=-1 tss=1 delay=0.99536

If there is anything I can do to test or provide more information, please let 
me know.

Adri,.

[chrony-dev] [GIT] chrony/chrony.git branch master updated. 3.0-pre1-13-g5634e6b

[git]

This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.

The branch, master has been updated
   via  5634e6b963657a71758111ef66dc344705fa8bfa (commit)
   via  db312a5ff6696fe9eec4b14cce2aa2da4c0f550d (commit)
   via  88c31b378599d01857041ee899ff49ee14772450 (commit)
   via  967f3e4f77951cc44f3e3a535e9776005bcd02a1 (commit)
   via  2e311d176633c48fef915c77c3dc9ace63dbd176 (commit)
  from  11f7cc05072fef4e533bba9b385d0cb514153324 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit 5634e6b963657a71758111ef66dc344705fa8bfa
Author: Miroslav Lichvar 
Date:   Wed Dec 14 13:30:17 2016 +0100

doc: improve hwtimestamp description

commit db312a5ff6696fe9eec4b14cce2aa2da4c0f550d
Author: Miroslav Lichvar 
Date:   Wed Dec 14 12:15:32 2016 +0100

ntp: allow wildcard in hwtimestamp directive

If "*" was specified, use getifaddrs() to get a list of all interfaces,
and try to enable HW timestamping on all of them.

commit 88c31b378599d01857041ee899ff49ee14772450
Author: Miroslav Lichvar 
Date:   Wed Dec 14 10:56:22 2016 +0100

client: improve ntpdata output

commit 967f3e4f77951cc44f3e3a535e9776005bcd02a1
Author: Miroslav Lichvar 
Date:   Wed Dec 14 09:56:52 2016 +0100

client: don't require address in ntpdata command

If no address is specified, use the SOURCE_DATA command to get addresses
of NTP sources, and request NTP_DATA for all of them.

commit 2e311d176633c48fef915c77c3dc9ace63dbd176
Author: Miroslav Lichvar 
Date:   Wed Dec 14 08:59:52 2016 +0100

sourcestats: add upper bound for skew

---

Summary of changes:
 client.c | 155 +++
 doc/chrony.conf.adoc |  12 ++--
 doc/chronyc.adoc |  12 ++--
 ntp_io_linux.c   |  55 +-
 sourcestats.c|   7 +--
 5 files changed, 163 insertions(+), 78 deletions(-)


hooks/post-receive
-- 
chrony/chrony.git

-- 
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.