Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-M option doesn't work #6

Open
Gunterwa opened this issue Jul 8, 2022 · 4 comments
Open

-M option doesn't work #6

Gunterwa opened this issue Jul 8, 2022 · 4 comments

Comments

@Gunterwa
Copy link

Gunterwa commented Jul 8, 2022

192.168.3.26 is ptpmaster, it got multicast packets from ntpperf (192.168.3.57) and responsed, but it seemd the response msg were ignored by ntpperf..
WechatIMG529
.

@Gunterwa
Copy link
Author

ptpmaster response in the test are multicast, is it OK?

@mlichvar
Copy link
Owner

mlichvar commented Jul 11, 2022

Multicast responses are ok. Are they coming from the address specified by the -d option?

Do you see both requests and responses in tcpdump and could you post few lines from the output showing at least one request and response?

@Gunterwa
Copy link
Author

Delay_Response.pcapng.zip
Enclosed please find the pcap file, thanks for your great support.

@mlichvar
Copy link
Owner

It looks like there might be two issues. One is that the NIC could be filtering multicast traffic if there is nothing else using it. The other is your server seems to be using source port 319 even for general messages and not just event messages as is normally expected.

Please try it again with the current code in git.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants