On Wed, Jun 08, 2016 at 04:25:17PM +0200, dsp...@gmx.de wrote:
> I use on the slave side the ptp timestamp with high accuracy for logging data,
> parallel i want to capture some wireshark frames with tcpdump.
> tcpdump uses the RTC so i'm not able to see directly the associated
> timestamps of PTP
Sorry, i hope now it is correct:
Hi Richard,
thanks for your help!
>> The ptp hardware clock seems to be adjusted correct but with phc2sys i can't
>> set the RTC on the same value as the PHC. It is 36 seconds away like TAI-UTC.
>
>The RTC should *not* have the same value as the PHC. The RTC us
No html, please.
Thanks,
Richard
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth.
Hi Richard,
thanks for your help!
>> The ptp hardware clock seems to be adjusted correct but with phc2sys i can't
>> set the RTC on the same value as the PHC. It is 36 seconds away like TAI-UTC.
>
>The RTC should *not* have the same value as the PHC. The RTC uses the
>UTC timescale, but
On Wed, Jun 08, 2016 at 09:19:40AM +, DSP wrote:
> The ptp hardware clock seems to be adjusted correct but with phc2sys i can't
> set the RTC on the same value as the PHC. It is 36 seconds away like TAI-UTC.
The RTC should *not* have the same value as the PHC. The RTC uses the
UTC timescale,
