-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Support Dublin
multipath strategy for IPv6/UDP
#272
Comments
Dublin
multipath strategy for IPv6
Dublin
multipath strategy for IPv6/UDP
Does not currently set a MAGIC prefix on payloads for IPv6/UDP/Dublin. This means an unrelated ICMP response with a UDP original datagram may be misinterpreted as being a response we should process. Arguably this lack of MAGIC prefix checking is general UDP (and TCP) issue and not specific to IPv6/UDP/Dublin. For IPv4 we cannot check this as we are not going to receive enough of the original datagram (i.e. the payload) to be sure to be able to read the MAGIC prefix. For IPv6/UDP (classic & paris) we get a sequence number and so can use that to filter uninteresting responses. Fixing this is tricky as we need to:
The issue is that we do not know, when processing a received ICMP packet with UDP original datagram, if we are in Dublin mode. We either have to make the receiver aware of that or we have to always use the MAGIC prefix for IPv6/UDP. Update: resolved by adding a |
Dublin traceroute for IPv6 (go implementation) uses
payload length
field of the IPv6 header to hold the sequence, see here.The text was updated successfully, but these errors were encountered: