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] Strange and undocumented (?) result in traceroute JSON output
- Previous message (by thread): [atlas] Strange and undocumented (?) result in traceroute JSON output
- Next message (by thread): [atlas] Strange and undocumented (?) result in traceroute JSON output
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Jul 17 10:47:56 CEST 2013
Hi Stephane,
On 2013/07/17 9:17 , Stephane Bortzmeyer wrote:
> Measurement #1013405 contains:
>
> "result": [
> {
> "x": "*"
> },
> {
> "late": 20,
> "ttl": 61,
> "from": "88.79.15.141",
> "size": 96
> },
> {
> "x": "*"
> },
> {
> "x": "*"
> }
>
> While "late" is documented
> <https://atlas.ripe.net/doc/data_struct#v4400_traceroute>, the lack of
> "rtt" field is not and crashes tools like json2traceroute.py.
>
I'll update the documentation to say that rtt won't be there for packets
that are late.
Philip
- Previous message (by thread): [atlas] Strange and undocumented (?) result in traceroute JSON output
- Next message (by thread): [atlas] Strange and undocumented (?) result in traceroute JSON output
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]