[atlas] edst 193.0.0.228 in traceroute results
- Previous message (by thread): [atlas] [Request] System tags for DNS resolution
- Next message (by thread): [atlas] Architecture and firmware version filter in probe selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yang Yu
yang.yu.list at gmail.com
Fri Nov 13 07:01:38 CET 2015
Hello, In https://atlas.ripe.net/measurements/2928258, I did a UDP traceroute. "edst":"193.0.0.228" from first hop and second hop somehow showed up in the results after the last hop that responded to traceroute, which should have been a reply to buil-in measurement to tt01.ripe.net. And under maps tab the result is presented with the first 2 hops showing up after several non-responding hops. Is this a bug? I actually see it happening quite often in atlas traceroute results with firmware > 4680. Another example is https://atlas.ripe.net/measurements/2928262 >>> https://atlas.ripe.net/docs/bugs/ 2015-03-04 Before firmware 4680, traceroute could experience interference from other measurements. In general, periodic traceroutes did not interfere with other periodic traceroutes, but could experience interference from one-off traceroutes. Typically, this interference will show up in the 'edst' field. This problem was fixed in 4680. Thanks. Yang
- Previous message (by thread): [atlas] [Request] System tags for DNS resolution
- Next message (by thread): [atlas] Architecture and firmware version filter in probe selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]