Wojciech Owczarek

Hi - this was identified some time ago. PTPd is not maintained on SF anymore, pull the latest github source from https://github.com/ptpd/ptpd and you should not have this issue anymore. Thanks, Wojciech

Allan, OK - that would explain the reported empty messages received - as per the comment in the sources "mesage without a timestamp considered harmful". This is likely a driver issue. While for TX timestamps, PTPd has its own way of dealing with waiting for them - for RX timestamps it follows the API and does nothing special. Thanks, Wojciech

Hi there, What you are seeing is actually a "side effect" of the driver / OS not being able to capture the transmission timestamps of the delay request messages. This is a notorious problem with many cards and drivers, almost to be expected. Ptpd silently ignores this, but as a result you have sequence gaps, because the transmitted delayResp - which is physically transmitted - is considered not sent, and the response comes back, but is dropped. I think I will need to rework this, because this behaviour...

Hi, The truth is that it doesn't really matter, because the slaves also run the BMCA, so even if two masters become active, slaves will select only one anyway. When the active master goes away, the other two will wait n * announce interval (configurable) and will consider themselves best and will start transmitting, possibly both. But soon after the "worse" of the two receives the first announce message from the "better" one, it will stop being master. Actually not as soon as, but soon.How long this...

Hi, I am not sure what this question has to do with PTPd. Were you meant to post it somewhere else? Thanks, Wojciech

Hi - can you stop the NTP client and see if that makes a difference? Also make sure...

Hi - can you stop the NTP client and see if that makes a difference? Also make sure...

Hi - the stratum 1 NTP server, is it local or is it somewhere on the Internet? Also...