You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. run ptpv2d with -8 option
2. run Wireshark or other LAN analyzer
3. observe IPv4 Multicast join packets sent on network
What is the expected output? What do you see instead?
A) It would be better that if the encapsulation selected is Direct Ethernet
that no IPv4 packets are generated.
Please use labels and text to provide additional information.
1) In the case of the -8 option, it would probably be better if only a raw
socket was opened and the opening of IPv4 UDP sockets was skipped. This would
avoid the Multicast join message being generated and also would make it so that
IPv4 packets would be ignored.
2) Downside is that I had some thoughts about allowing future versions of
ptpv2d auto-detect the best grandmaster regardless of protocol type and then
adapt to it.
Comments and thoughts on this are welcome.
This bug is mostly cosmetic.
Original issue reported on code.google.com by a...@bartky.net on 28 Aug 2010 at 5:23
The text was updated successfully, but these errors were encountered:
When it comes to precision on my Windows portation, I did not do anything
special when it comes to time adjustment and time accuracy.
I did not have any experience in doing a Winsock application as this is the
first one I've ever done.
With that, when it came to both socket application and getting/setting time
from the operating system, I did the best I could.
So I'm not surprised that the accuracy is less than Linux as from what I
could tell, standard Windows calls for getting/setting time are not very
accurate.
If you know of a better way that time could be measured and set, I'd be open
to porting it into the code.
Alan
Original comment by a...@bartky.net on 16 Apr 2011 at 8:51
Hi Alan
Thank you for your attention~ I tried to use PTPV2D on the WIndows XP. I found
some problems as following:
1) I run PTPV2D on 2 computers. After that, according to the debug message of
msgUnpackV2Header, the time is synchronized. Which API or method is expected to
use for getting the time which are synchronized?
- getTime(TimeInternal *time, Integer16 utc_offset)?
- GetSystemTimeAsFileTime?
- etc?
2) When the time is synchronized by using PTPV2D, the system clock will not be
adjusted(changed) by PTPV2D program . How can I let the program to set the
system clock in order to let the system clock are synchronized between 2
computers.
I found that the void updateClock(RunTimeOpts*,PtpClock*) in ptpd_dep.h without
called.
Original comment by mcw...@gmail.com on 18 Apr 2011 at 4:17
MCW, comments edited in below.
If you are a member of the ptpv2d google group, please use the ptpv2d group
instead of the issues page on code.google.com.
Original comment by a...@bartky.net on 23 Apr 2011 at 10:55
Original issue reported on code.google.com by
a...@bartky.net
on 28 Aug 2010 at 5:23The text was updated successfully, but these errors were encountered: