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] RFC1918 probes
- Previous message (by thread): [atlas] RFC1918 probes
- Next message (by thread): [atlas] RFC1918 probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed May 22 15:37:32 CEST 2019
On 2019-05-22 14:40, Mayer Hans 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. > > Kind regards > Hans Hi, When you set up your measurement, you can exclude probes that are tagged with IPv4 RFC1918 (system-ipv4-rfc1918). Regards, Robert
- Previous message (by thread): [atlas] RFC1918 probes
- Next message (by thread): [atlas] RFC1918 probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]