[atlas] Meaning behind "TU_BAD_ADDR" error

[Meikel Kokowski]

Good evening,

While parsing data from some of my measurements (using ripe.atlas.sagan) I 
stumbled over the “TU_BAD_ADDR” error. The error message is only “true” which 
makes it difficult to understand its  origin. Furthermore, as opposed to other 
errors, such as “timeout”, no error is indicated by the is_error method of the 
DnsResult object. Instead I can only find this in the raw_data (in the dns 
respone object).
In my measurements I send the same DNS query (using probe’s IPv6-address) to 
public resolver and the probes local resolver over UDP and TCP respectively. 
The TU_BAD_ADDR error occurred solely on measurements to the probes local 
resolver over TCP. Respective measurements using the same probes over UDP do 
not report this error. Another observation is that the source address of the 
response is not set in the majority of the cases (but that is not always the 
case).
An example measurement is #41853554 (the counter-measurement over UDP 
#41853806).

Does anyone know more about this?

Best regards,
Meikel
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] RIPE Atlas down?

[Robert Kisteleki]

Hello,

The data back-end behind RIPE Atlas, RIS and RIPEstat experienced issues 
yesterday evening; some of these are still affecting the data processing.


In particular RIPE Atlas data is experiencing result delays since around 
03:30 (CEST). The system is catching up now, but it hasn't recovered 
fully yet.


https://status.ripe.net/ has an entry about the generic problem and 
we'll put up a specific entry about this specific delay.


We apologise for the inconvenience,
Robert


On 2022-06-22 11:34, Ernst J. Oud wrote:

Hi,

I noticed that of the probes I checked here in The Netherlands, all logging 
stops at around 03:00 today (June, 22nd).

Checked a probe in Germany, same thing but stopped a couple of hours later it 
seems.

Is there some problem?

Regards,

Ernst J. Oud



--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] RIPE Atlas down?

[Stephane Bortzmeyer]

On Wed, Jun 22, 2022 at 11:34:09AM +0200,
 Ernst J. Oud  wrote 
 a message of 78 lines which said:

> Checked a probe in Germany, same thing but stopped a couple of hours later it 
> seems.
> 
> Is there some problem?

Indeed, measurements never return results
.


-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

[atlas] RIPE Atlas down?

[Ernst J. Oud]

Hi,

I noticed that of the probes I checked here in The Netherlands, all logging 
stops at around 03:00 today (June, 22nd).

Checked a probe in Germany, same thing but stopped a couple of hours later it 
seems.

Is there some problem?

Regards,

Ernst J. Oud

> On 21 Jun 2022, at 12:00, ripe-atlas-requ...@ripe.net wrote:
> 
> Send ripe-atlas mailing list submissions to
>ripe-atlas@ripe.net
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>https://lists.ripe.net/mailman/listinfo/ripe-atlas
> or, via email, send a message with subject or body 'help' to
>ripe-atlas-requ...@ripe.net
> 
> You can reach the person managing the list at
>ripe-atlas-ow...@ripe.net
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ripe-atlas digest..."
> 
> 
> Today's Topics:
> 
>   1. Re:  No data for ping to second hop? (Ernst J. Oud)
>   2. Re:  No data for ping to second hop? (Ponikierski, Grzegorz)
> 
> 
> --
> 
> Message: 1
> Date: Mon, 20 Jun 2022 19:09:01 +0200
> From: "Ernst J. Oud" 
> To: ripe-atlas@ripe.net
> Subject: Re: [atlas] No data for ping to second hop?
> Message-ID: 
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi,
> 
> Thanks for the reply. But it appears to be a common problem for Linux 
> containers in Docker Desktop for Windows. All traceroute commands only show 
> asterisks. As explained here: 
> 
> https://github.com/moby/vpnkit/pull/302
> 
> (vpnkit is used by Docker in Windows).
> 
> So I will have to install the probe in a native Linux environment instead.
> 
> Which raises another question: if I get the probe running in native Linux, 
> can I transfer my current probe ID to this new installation? Or do I have to 
> apply for a new probe (and disconnect the other)?
> 
> Regards,
> 
> Ernst
> 
>> On 20 Jun 2022, at 12:00, ripe-atlas-requ...@ripe.net wrote:
>> 
>> Re:  No data for ping to second hop?
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 
> --
> 
> Message: 2
> Date: Mon, 20 Jun 2022 17:23:33 +
> From: "Ponikierski, Grzegorz" 
> To: "Ernst J. Oud" , "ripe-atlas@ripe.net"
>
> Subject: Re: [atlas] No data for ping to second hop?
> Message-ID: <56336cc2-3243-4a99-b943-711bbc965...@akamai.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Ernst, just update SSH keys in probe?s General tab (the last Edit item on the 
> page) so probe will preserve its number.
> 
> Regards,
> Grzegorz
> 
> From: "Ernst J. Oud" 
> Date: Monday 2022-06-20 at 19:09
> To: "ripe-atlas@ripe.net" 
> Subject: Re: [atlas] No data for ping to second hop?
> 
> Hi,
> 
> Thanks for the reply. But it appears to be a common problem for Linux 
> containers in Docker Desktop for Windows. All traceroute commands only show 
> asterisks. As explained here:
> 
> https://github.com/moby/vpnkit/pull/302
> 
> (vpnkit is used by Docker in Windows).
> 
> So I will have to install the probe in a native Linux environment instead.
> 
> Which raises another question: if I get the probe running in native Linux, 
> can I transfer my current probe ID to this new installation? Or do I have to 
> apply for a new probe (and disconnect the other)?
> 
> Regards,
> 
> Ernst
> 
> 
> On 20 Jun 2022, at 12:00, ripe-atlas-requ...@ripe.net wrote:
> 
> Re:  No data for ping to second hop?
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 
> --
> 
> Subject: Digest Footer
> 
> -- 
> ripe-atlas mailing list
> ripe-atlas@ripe.net
> https://lists.ripe.net/mailman/listinfo/ripe-atlas
> 
> 
> --
> 
> End of ripe-atlas Digest, Vol 130, Issue 8
> **

-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas