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] Garbage Measurements
- Previous message (by thread): [atlas] Garbage Measurements
- Next message (by thread): [atlas] Reddit?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Mon Aug 26 13:32:19 CEST 2013
Hello, On 2013.08.26. 8:52, Peter Koch wrote: > On Mon, Aug 26, 2013 at 02:37:34AM +0200, Philip Homburg wrote: > >> I have no idea what the purpose is of those measurements. But user that >> created them does get charged for the results. And probes return >> results. So from that point of view nothing is wrong. > > maybe it's time to compile a filter list to counter reconnaissance of > thge probes' network vicinity, which I don't think was the stated purpose > of the Atlas project. > > -Peter Indeed, we do exclude the "probes' network vicinity", as you called it. At the moment, this is the exclusion list: exclude4 = ('PRIVATE', 'RESERVED') exclude6 = ('LINKLOCAL', 'UNSPECIFIED', 'LOOPBACK', 'MULTICAST') (The above acronyms are defined in the IPy Python module, see https://github.com/haypo/python-ipy/blob/master/IPy.py for details.) Please speak up if you have justification for other networks to be excluded. Note that it's very difficult to apply the above filters to perfection; a sophisticated enough user may be able to find ways around it. Retards, Robert
- Previous message (by thread): [atlas] Garbage Measurements
- Next message (by thread): [atlas] Reddit?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]