Hello Richard,

Ohh yeah i forgot the GM in the case of the Recoding is not so important a 
college try'ed to remove the Mac.
(Don't ask why it's a dev device so it will never see the light.. )

Hmm i currently use the 8021q device to tag/untag the frames as we wanted 
to use vlan 150. 
It still shows only best master clock selected no offsets but only in the 
case if two gm's are attached. 

Can the ptp4l manage vlans himself? As you wrote about a vlan raw that 
should be logged or is that just if it gets a frame with vlan.
Here the raw without vlan capture:



Best regards,

Hamar



Von:    Richard Cochran <richardcoch...@gmail.com>
An:     Armin HAMAR <armin.ha...@sprecher-automation.com>
Kopie:  linuxptp-users@lists.sourceforge.net
Datum:  09.12.2019 16:09
Betreff:        Re: Antwort: Re: [Linuxptp-users] No offsets at all?



On Fri, Dec 06, 2019 at 07:12:18AM +0100, Armin HAMAR wrote:
> Sadly i can't send you a capture as it's to big.. 

No problem.  The text dump shows everything.  You have a very stange
network that is unfamilar to me.  I'm not sure I can help you at
all...

The log shows:

   ptp4l[1208613.181]: port 1: new foreign master 001b21.fffe.df71ab-8193
   ptp4l[1208617.145]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
   ptp4l[1208617.181]: selected best master clock 001b21.fffe.df71ab

Notice the port ID?  But the text dump shows:

   No.     Time           Source                Destination Protocol 
Length sequenceId ID         Info
         3 0.042398971    Sprecher_05:00:c4     LLDP_Multicast PTPv2    72 
    25635      150        Path_Delay_Req Message
 
   Ethernet II, Src: XXXXXX_01:02:03 (00:00:00:01:02:03), Dst: 
LLDP_Multicast (01:80:c2:00:00:0e)
       Source: XXXXXX_01:02:03 (00:00:00:01:02:03)
           Address: XXXXXX_01:02:03 (00:00:00:01:02:03)
           .... ..0. .... .... .... .... = LG bit: Globally unique address 
(factory default)
           .... ...0 .... .... .... .... = IG bit: Individual address 
(unicast)
       Type: 802.1Q Virtual LAN (0x8100)
   802.1Q Virtual LAN, PRI: 0, DEI: 0, ID: 150
       000. .... .... .... = Priority: Best Effort (default) (0)
       ...0 .... .... .... = DEI: Ineligible
       .... 0000 1001 0110 = ID: 150
       Type: PTPv2 over Ethernet (IEEE1588) (0x88f7)
   Precision Time Protocol (IEEE1588)
       ClockIdentity: 0x000000fffe010203
       SourcePortID: 0
       sequenceId: 25635

Things wrong here:
~~~~~~~~~~~~~~~~~~

1. The Source MAC Sprecher_05:00:c4 (in the summary)
   is not the same as Source: XXXXXX_01:02:03 (00:00:00:01:02:03)

2. There is a VLAN tag.  linuxptp never adds VLAN tags!

And look at the response:

   No.     Time           Source                Destination Protocol 
Length sequenceId ID         Info
         4 0.042448275    IntelCor_df:6f:6c     LLDP_Multicast PTPv2    72 
    25635      150        Path_Delay_Resp Message
 
   Ethernet II, Src: IntelCor_df:6f:6c (00:1b:21:df:6f:6c), Dst: 
LLDP_Multicast (01:80:c2:00:00:0e)
       Source: IntelCor_df:6f:6c (00:1b:21:df:6f:6c)
           Address: IntelCor_df:6f:6c (00:1b:21:df:6f:6c)
           .... ..0. .... .... .... .... = LG bit: Globally unique address 
(factory default)
           .... ...0 .... .... .... .... = IG bit: Individual address 
(unicast)
       Type: 802.1Q Virtual LAN (0x8100)
   802.1Q Virtual LAN, PRI: 0, DEI: 0, ID: 150
       000. .... .... .... = Priority: Best Effort (default) (0)
       ...0 .... .... .... = DEI: Ineligible
       .... 0000 1001 0110 = ID: 150
       Type: PTPv2 over Ethernet (IEEE1588) (0x88f7)
   Precision Time Protocol (IEEE1588)
       ClockIdentity: 0x001b21fffedf6f6c
       SourcePortID: 1
       sequenceId: 25635
       requestingSourcePortIdentity: 0x000000fffe010203
       requestingSourcePortId: 0

Things wrong:
~~~~~~~~~~~~~

1. ClockIdentity: 0x001b21fffedf6f6c with SourcePortID: 1 does not
   match the selected master 001b21.fffe.df71ab-8193

2. the VLAN tag.  I didn't see the message ("raw: switching to VLAN mode")
   in your log output.

Maybe this capture comes from a man in the middle?

If so, try tcpdump/tshark on the actual slave node instead.  It could
very well be that the peer delay responses are not arriving at the slave.

HTH,
Richard


Attachment: card_ptp.pcapng
Description: Binary data

_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to