[atlas] [Request] System tags for DNS resolution

[Stephane Bortzmeyer]

[Is there a better way to record enhancement requests for Atlas? Atlas
has no public issue tracker, if I'm correct?]

It would be cool to have system (automatic) tags for DNS resolution
because some probes are using broken DNS resolvers. For instance,

system-dns-works (modeled on IPv6's system tag) would be fine. Or may
be system-dns-resolver-works (longer but more accurate).

For instance, probes 16659, 17072, 17620, 17854 use a resolver which
yields a REFUSED for any request and probe 19948, 20065 one with
systematic SERVFAIL.

[Is the maintainer of the probe automatically notified when there is
such an issue?]

[atlas] Any way to select the probes from upstream AS (not origin AS)?

[Stephane Bortzmeyer]

Is there an easy way to select probes, not on the origin AS, but on an
AS upstream? Example: probe 23865, IP prefix announced by AS 56339
which currently has only one provider, AS 16080. Currently, Atlas
tells me there are no probes in AS 16080...

Re: [atlas] VM probes

[Stephane Bortzmeyer]

On Mon, Nov 09, 2015 at 12:49:19PM +,
 Colin Johnston  wrote 
 a message of 30 lines which said:

> one vote for vmware virtualisation

Strong -1 against any proprietary technology. Free software or
nothing. (But, like most people here, I'm not interested in VM probes
and even less in VM anchors.)

Re: [atlas] Any way to select the probes from upstream AS (not origin AS)?

[Stephane Bortzmeyer]

On Wed, Nov 11, 2015 at 04:43:49PM +0100,
 Robert Kisteleki  wrote 
 a message of 14 lines which said:

> No, we don't have direct support for this. I guess one could
> download latest traceroute results for a (random) built-in
> measurement, map IPs to ASNs and use that -- but I have to admit
> it's not easy.

I understand. Also, a probe has one origin AS but may have several
upstream AS and you don't know which one will be used when the probe
fires a packet to the target.

Re: [atlas] Any way to select the probes from upstream AS (not origin AS)?

[Robert Kisteleki]

On 2015-11-11 16:32, Stephane Bortzmeyer wrote:
> Is there an easy way to select probes, not on the origin AS, but on an
> AS upstream? Example: probe 23865, IP prefix announced by AS 56339
> which currently has only one provider, AS 16080. Currently, Atlas
> tells me there are no probes in AS 16080...

Hi,

No, we don't have direct support for this. I guess one could download latest
traceroute results for a (random) built-in measurement, map IPs to ASNs and
use that -- but I have to admit it's not easy.

Regards,
Robert