Erez,

Yes, we have 802.1q vlan. 4 bytes vlan head is added as vlan tag. But I think 
802.1q vlan will not add 4 bytes at the end of PDU.

The ptp4l configuration is as this:

[global]
#
# Default Data Set
#
twoStepFlag     1
slaveOnly       1
priority1       128
priority2       128
domainNumber        0
#utc_offset     37
clockClass      248
clockAccuracy       0xFE
offsetScaledLogVariance 0xFFFF
free_running        0
freq_est_interval   1
dscp_event      0
dscp_general        0
dataset_comparison  ieee1588
G.8275.defaultDS.localPriority  128
#
# Port Data Set
#
logAnnounceInterval 1
logSyncInterval     0
logMinDelayReqInterval  0
logMinPdelayReqInterval 0
announceReceiptTimeout  3
syncReceiptTimeout  0
delayAsymmetry      0
fault_reset_interval    4
neighborPropDelayThresh 20000000
masterOnly      0

#
# Run time options
#
assume_two_step     0
logging_level       6
path_trace_enabled  0
follow_up_info      0
hybrid_e2e      0
net_sync_monitor    0
tc_spanning_tree    0
tx_timestamp_timeout    1
use_syslog      1
verbose         0
summary_interval    0
kernel_leap     1
check_fup_sync          0
#
# Servo Options
#
pi_proportional_const   0.0
pi_integral_const   0.0
pi_proportional_scale   0.0
pi_proportional_exponent    -0.3
pi_proportional_norm_max    0.7
pi_integral_scale   0.0
pi_integral_exponent    0.4
pi_integral_norm_max    0.3
step_threshold      0.0
first_step_threshold    0.00002
max_frequency       900000000
clock_servo     pi
sanity_freq_limit   200000000
ntpshm_segment      0
#
# Transport options
#
transportSpecific   0x0
ptp_dst_mac     01:1B:19:00:00:00
p2p_dst_mac     01:80:C2:00:00:0E
udp_ttl         1
udp6_scope      0x0E
uds_address     /var/run/ptp4l
#
# Default interface options
#
clock_type      OC
network_transport   UDPv4
delay_mechanism     E2E
time_stamping       hardware
tsproc_mode     filter
delay_filter        moving_median
delay_filter_length 10
egressLatency       0
ingressLatency      0
boundary_clock_jbod 0
#
# Clock description
#
productDescription  ;;
revisionData        ;;
manufacturerIdentity    00:00:00
userDescription     ;
timeSource      0xA0

unicast_req_duration    60

[unicast_master_table]
table_id                1
logQueryInterval        2
UDPv4 169.254.32.10
[ens1f1]
unicast_master_table    1

Thanks,
Steven

From: Geva, Erez <erez.geva....@siemens.com>
Sent: Thursday, January 10, 2019 1:57 AM
To: Sun, Steven (NSB - CN/Qingdao) <steven....@nokia-sbell.com>; 
Linuxptp-devel@lists.sourceforge.net
Subject: RE: linuxptp2.02 processing the extra 4 bytes which is not in PTP 
length

Hi,

It happens with one message "Delay Response" in the length 104 bytes.
Did you check your VLAN, may be the VLAN add the 4 bytes?
Did you see this behavior without using VLAN?

What is your ptp4l configuration?

Erez

________________________________
From: Sun, Steven (NSB - CN/Qingdao) [steven....@nokia-sbell.com]
Sent: 09 January 2019 19:18
To: 
Linuxptp-devel@lists.sourceforge.net<mailto:Linuxptp-devel@lists.sourceforge.net>
Subject: [Linuxptp-devel] linuxptp2.02 processing the extra 4 bytes which is 
not in PTP length
Hello all,

Glad to join the linuxptp devel mail list.
We met an issue about ptp4l processing 4 more bytes which is not in PTP but in 
UDP payload.
Ptp4l keep reporting failure log as below:
Jan 07 12:11:58 slot-15 ptp4l[12876]: [247083.836] port 1: new foreign master 
fcaf6a.fffe.029a96-1
Jan 07 12:11:59 slot-15 ptp4l[12876]: [247084.572] selected local clock 
48df37.fffe.3a9f51 as best master
Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.836] selected best master clock 
fcaf6a.fffe.029a96
Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.836] running in a temporal vortex
Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.836] port 1: LISTENING to 
UNCALIBRATED on RS_SLAVE
Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.962] port 1: bad message
Jan 07 12:12:02 slot-15 ptp4l[12876]: [247088.031] port 1: bad message
Jan 07 12:12:03 slot-15 ptp4l[12876]: [247088.985] port 1: bad message

These 4 bytes is out of the PTP length which defined in PTP header.
I checked they are included in the UDP payload, so should not be FCS bytes. Not 
sure about the purpose of these 4 bytes but PTP may should not process them.

[cid:image001.png@01D4A8CD.DB66B390]

Thanks,
Steven
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to