Re: [Linuxptp-users] time stamping

[Milutin A. <mil...@ho...>]

Hello,
Maybe I didn't understand but I was thinking that I can get traffic
of network packets (packets that go out of network card like wireshark does) with exact times when they were sent not the time on the host but the times on
the network card. And I was thinking I could do it with your ptp4l program.
So I need the exact time (timestamping on the card with accuracy of 1 microsecond) and length of packets on the link. If I can't do it with your program's packet can you tell me with which program I can do it.
Thank you in advance,
Milutin Aksic.

> From: jac...@in...
> To: ric...@gm...; mil...@ho...
> CC: lin...@li...
> Subject: RE: [Linuxptp-users] time stamping
> Date: Fri, 19 Jul 2013 20:50:58 +0000
> 
> 
> > -----Original Message-----
> > From: Richard Cochran [mailto:ric...@gm...]
> > Sent: Friday, July 19, 2013 10:24 AM
> > To: Milutin Aksic
> > Cc: lin...@li...
> > Subject: Re: [Linuxptp-users] time stamping
> > 
> > On Fri, Jul 19, 2013 at 04:29:07PM +0100, Milutin Aksic wrote:
> > > Ok, when I do the command: ptp4l -i eth1 -p /dev/ptp0 -m
> > > I get the following:
> > >
> > > ptp4l[468.371]: selected /dev/ptp0 as PTP clock
> > > ptp4l[468.372]: failed to read out the clock frequency adjustment:
> > Operation not supported
> > > ptp4l[468.372]: port 1: get_ts_info not supported
> > > ptp4l[468.372]: driver changed our HWTSTAMP options
> > > ptp4l[468.372]: tx_type   1 not 1
> > > ptp4l[468.372]: rx_filter 1 not 12
> > > ptp4l[468.372]: port 1: INITIALIZING to LISTENING on INITIALIZE
> > > ptp4l[468.373]: port 0: INITIALIZING to LISTENING on INITIALIZE
> > > ptp4l[474.372]: port 1: LISTENING to MASTER on
> > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> > 
> > This looks okay.
> > 
> > > and 2nd line I supose is not the problem (failed to read out the
> > > clock frequency adjustment). But what I should do next to get the
> > > time stamp times of packets?
> > 
> > What do you mean? The program appears to be working correctly,
> > including getting time stamps (otherwise you would see an error
> > message).
> > 
> > Thanks,
> > Richard
> > 
> 
> What you are seeing is your device going into master mode because there are no other nodes detected. Are you running at least one other node connected to the same network?
> 
> This is the expected behavior for a master node.
> 
> - Jake
>