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/[email protected]/
[atlas] RFC1918 probes
- Previous message (by thread): [atlas] RFC1918 probes
- Next message (by thread): [atlas] RFC1918 probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Wed May 22 15:31:24 CEST 2019
> On May 22, 2019, at 8:40 AM, Mayer Hans <Hans.Mayer at iiasa.ac.at> wrote: > > > > Dear All, > > Looking at the result of a traceroute measurement I see very often that first hop has a RFC1918 address. > These days a found a result where the first 3 hops are showing something like 192.168.x.y > Of course this could falsify the result especially for response time. > Is there a way to select only Atlas probes which are located in non RFC1918 networks ? > If not it would be nice to have such a possibility. I think you’re speaking of just using the anchors? - Jared
- Previous message (by thread): [atlas] RFC1918 probes
- Next message (by thread): [atlas] RFC1918 probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]