perfSONAR User Q&A and Other Discussion

[Brian Candler <>]

OK, I just tried again and it's working now. It's clear the clocks are 
~440ms out of sync. Maybe the time difference was higher previously.

Regards,

Brian.


From OSX to Perfsonar:

$ date; time owping 192.168.56.6
Mon  1 Dec 2014 14:51:59 GMT
owping: FILE=time.c, LINE=124, NTP syscalls unavail: Status UNSYNC 
(clock offset issues likely)
Approximately 12.9 seconds until results available

--- owping statistics from [Brians-MacBook-Air.local]:50754 to 
[192.168.56.6]:8841 ---
SID:    c0a83806d826ff0f7202009cc92f80b7
first:    2014-12-01T14:52:00.953
last:    2014-12-01T14:52:11.321
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = -439/-438/-437 ms, (unsync)
one-way jitter = 0.4 ms (P95-P50)
TTL not reported
no reordering


--- owping statistics from [192.168.56.6]:9313 to 
[Brians-MacBook-Air.local]:60233 ---
SID:    c0a83801d826ff0fe328e92d9a7f8114
first:    2014-12-01T14:52:00.982
last:    2014-12-01T14:52:10.457
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = 438/439/439 ms, (unsync)
one-way jitter = 0.5 ms (P95-P50)
TTL not reported
no reordering


real    0m14.197s
user    0m0.008s
sys    0m0.030s



From perfsonar to OSX:


$ owping 192.168.56.1
Approximately 13.2 seconds until results available

--- owping statistics from [perfsonar1.ws.nsrc.org]:8914 to 
[192.168.56.1]:9819 ---
SID:    c0a83801d826fe9c426bb55a9a4ee77e
first:    2014-12-01T14:50:05.004
last:    2014-12-01T14:50:15.106
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = 436/436/437 ms, (unsync)
one-way jitter = 0.4 ms (P95-P50)
TTL not reported
no reordering


--- owping statistics from [192.168.56.1]:9043 to 
[perfsonar1.ws.nsrc.org]:8770 ---
SID:    c0a83806d826fe9bd4e052438f763817
first:    2014-12-01T14:50:05.055
last:    2014-12-01T14:50:15.805
100 sent, 0 lost (0.000%), 0 duplicates
one-way delay min/median/max = -436/-435/-434 ms, (unsync)
one-way jitter = 0.4 ms (P95-P50)
TTL not reported
no reordering