Re: [Linuxptp-users] using ptp4l on vlan interfaces

[Shawn B. <sha...@gm...>]

On Fri, Dec 13, 2013 at 04:54:22PM +0100, Richard Cochran wrote:
> On Wed, Dec 11, 2013 at 03:42:09PM -0600, Shawn Bohrer wrote:
>  
> > I left the message in but let it continue.  It appears to work fine
> > with software timestamps, or at least I don't see any relevant errors
> > and it is adjusting the clock.  I haven't looked into the "port 1:
> > delay timeout" messages yet.
> 
> Those are harmless debug messages that say, "it is time to transmit
> another delay request."

Excellent ptp4l with software timestamps works just fine on the vlan
interface as long as you omit the ethtool check.

> > My end goal though is to use hardware timestamps and that currently
> > does not work on the vlan interface simply because the SIOCSHWTSTAMP
> > ioctl fails.
> 
> For now, if you know the real inteface, you can set the ioctl by hand
> using the hwstamp_ctl program. Then, just hack ptp4l to skip over the
> ioctl, and it might work for you.

I just finished testing ptp4l with hardware timestamps on the vlan as
well and that works as long as you both omit the ethtool check, and
omit the ioctl.  You but then first use the hwstamp_ctl program to
setup the timestamps before you start ptp4l.
 
> >  I'm not sure how it is done, but should ptp4l recognize
> > that it is a vlan interface and perform ioctl and ethtool queries
> > against the actual device interface?  I know the 'ip' tool associates
> > vlan807 with eth4 so that mapping can be detected somehow:
> 
> I think it would be nicer if the kernel did this for us automatically,
> but I'll have to take this up on the netdev list.

Cool, I agree that it seems like the kernel should at least pass only
the ethtool information from the actual device for a vlan interface.
What is your suggestion for the ioctl?  Should the kernel
automatically perform that on the correct driver as well?  Are you
going to raise this on netdev or should I?

Thanks,
Shawn