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] Ability to traceroute to 240/4 - software vs. hardware probes
- Previous message (by thread): [atlas] Ability to traceroute to 240/4 - software vs. hardware probes
- Next message (by thread): [atlas] Magellan report on built-in measurement 1
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Seth David Schoen
schoen at loyalty.org
Mon Jan 9 16:36:18 CET 2023
Robert Kisteleki writes: > > What could account for the difference in how hardware and software > > probes handle this task? I would have thought that the change from > > last November would make software probes willing to attempt these. > > I'd believe it's the combination of what versions these probe run (i.e.. is > it at least 5060?) plus the properties of the network they are in. The code > is otherwise the same. Thank you. This is now confirmed: after I upgraded my own software probe to the most recent release, its behavior matches what I expect.
- Previous message (by thread): [atlas] Ability to traceroute to 240/4 - software vs. hardware probes
- Next message (by thread): [atlas] Magellan report on built-in measurement 1
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]