Hello all,
While not a ptpd developer, I am a user and am getting quite a few log entries like this:
"Dec 13 13:39:45 (none) daemon.info ptpd2: Ignored followup, SequenceID doesn't match with last Sync message"
I'm looking for some help on what this might mean, Is it a problem to worry about, and how would I remedy it?
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This can happen if you're using two-step mode and packets got reordered when traversing the network - it might be the case that you received a follow-up before you received the sync it belonged to. However there was also a sequence number rollover bug that I think manifested itself identically - nothing to worry about, dropping one message will not decrease the performance drastically. If it is the sequence number issue, try version 2.2.2 and or better the current svn trunk.
Thanks
Woj
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
While not a ptpd developer, I am a user and am getting quite a few log entries like this:
"Dec 13 13:39:45 (none) daemon.info ptpd2: Ignored followup, SequenceID doesn't match with last Sync message"
I'm looking for some help on what this might mean, Is it a problem to worry about, and how would I remedy it?
Thank you.
Max,
This can happen if you're using two-step mode and packets got reordered when traversing the network - it might be the case that you received a follow-up before you received the sync it belonged to. However there was also a sequence number rollover bug that I think manifested itself identically - nothing to worry about, dropping one message will not decrease the performance drastically. If it is the sequence number issue, try version 2.2.2 and or better the current svn trunk.
Thanks
Woj