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

Variable udp and tcp paths causes incorrect trace #269

Closed
fujiapple852 opened this issue Aug 18, 2022 · 0 comments · Fixed by #335
Closed

Variable udp and tcp paths causes incorrect trace #269

fujiapple852 opened this issue Aug 18, 2022 · 0 comments · Fixed by #335
Labels
bug Something isn't working tcp udp
Milestone

Comments

@fujiapple852
Copy link
Owner

When the trace path changes between rounds (as can happen for UDP and TCP where the src/dest port are not fixed) the tracer can fail to find all hops on the path in subsequent rounds.

Sequence of events:

  • In round 1 the target is found for hop 10, target_ttl is set to be 10
  • In round 2 the target is found for hop 5, target_ttl is set to be 5
  • In round 3 the target is not found as the trace only sends probes for ttl up to 5 (target would have been found by ttl 10)

This should not occur if stable src/dest port numbers are used, i.e. when using Parisian checksums.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tcp udp
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant