This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Traceroute path consistency
- Previous message (by thread): [atlas] Traceroute path consistency
- Next message (by thread): [atlas] Traceroute path consistency
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Aug 15 13:32:37 CEST 2012
On 8/15/12 12:39 , David Lebrun wrote: > > I have a suggestion regarding the udp traceroute feature: allowing the > user to specify the source port. > > The motivation for this suggestion is to keep consistent paths between > two traceroutes towards the same destination. I understand that the > source port is used to discriminate concurrent traceroutes, so perhaps > allocating a range for user-defined source ports would do the trick. > > The paris-traceroute mode, which is default for firmware above 4400 keeps the source port consistent as long as a UDM is running on a probe. It does vary the destination port to trigger different routes, but the variation is included in the output (paris_id) Unfortunately, for IPv4 the source port is needed by the traceroute implementation, so it cannot be made user settable. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20120815/9a47b326/attachment.html>
- Previous message (by thread): [atlas] Traceroute path consistency
- Next message (by thread): [atlas] Traceroute path consistency
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]