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] Wrong IP prefix values accepted?
- Previous message (by thread): [atlas] Wrong IP prefix values accepted?
- Next message (by thread): [atlas] Wrong IP prefix values accepted?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Tue Mar 17 17:25:33 CET 2015
On Tue, Mar 17, 2015 at 04:15:08PM +0100, Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote a message of 4 lines which said: > It seems there is no protection against wrong prefixes? Last (I promise) remark about prefix selection. I cannot do it from the API. From the Web interface, I can select the prefix 88.176.0.0/12 and it works. But from the API, while it is accepted (I get a number, #1897919), he measurement later fails. My JSON: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of jihadmin.com from prefix 88.176.0.0/12', 'af': 4, 'query_argument': 'jihadmin.com', 'query_type': 'A', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 5, 'type': 'prefix', 'value': '88.176.0.0/12'}]} The status when querying: {u'id': 7, u'name': u'Failed'}
- Previous message (by thread): [atlas] Wrong IP prefix values accepted?
- Next message (by thread): [atlas] Wrong IP prefix values accepted?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]