Yes, I'm sure the probe has a v6 address because it is displayed into the "Network Information" tab and I'm 100% sure that v6 is working because all the devices (computers, smartphones, etc.) connected to the same network are using v6 without problems. My v6 network is tunneled. I know that the tunnel is up because now I'm using v6 to surf the net and send you this email. I too noticed the missing system tags. Some days ago I sent a message about this issue but unfortunately I got no answer. My probe's v6 address is: 2001:1418:1a5:0:6666:b3ff:feb0:ef68 The address is also displayed when clicking on my probe on the map at this URL https://atlas.ripe.net/results/maps/network-coverage/ Thanks for your help! Matteo On Thu, Nov 6, 2014 at 1:03 PM, AlbyVA <albyva@empire.org> wrote:

Matteo:

Are you 100% sure the probe has a v6 address or if v6 is working overall? Do you have native v6 or tunneled? Not that it matters, other than the tunnel could be down. I also don't see any v6 tags on your probe's page (ie: v6 Works or Resolves AAAA Correctly).

Here is my probe with v6 working and I've got a v6 tunnel running: https://atlas.ripe.net/probes/10378/

What is your probe's v6 address? Maybe we can all see if it's pingable.

On Wed, Nov 5, 2014 at 10:10 AM, Matteo Bonora <matteo@bonora.eu> wrote:

...

Hello,

I have noticed that my probe (#14602) doesn't perform the IPv6 built-in measurements since about 5 months.

The probe has working IPv6 connectivity, so I can't understand where is the problem.

Anyone has an idea about what can I do to solve this?

(below you can see some graphs of my probe's measurements. The brief packet loss on IPv4 was due to a temporary network outage)

Thanks for your help!

Matteo

Hi, 2001:1418:1a5:0:6666:b3ff:feb0:ef68 is reachable from here! (AS199952) El 06/11/2014 13:49, Matteo Bonora escribió:

Yes, I'm sure the probe has a v6 address because it is displayed into the "Network Information" tab and I'm 100% sure that v6 is working because all the devices (computers, smartphones, etc.) connected to the same network are using v6 without problems.

My v6 network is tunneled. I know that the tunnel is up because now I'm using v6 to surf the net and send you this email.

I too noticed the missing system tags. Some days ago I sent a message about this issue but unfortunately I got no answer.

My probe's v6 address is: 2001:1418:1a5:0:6666:b3ff:feb0:ef68 The address is also displayed when clicking on my probe on the map at this URL https://atlas.ripe.net/results/maps/network-coverage/

Thanks for your help!

Matteo

On Thu, Nov 6, 2014 at 1:03 PM, AlbyVA <albyva@empire.org <mailto:albyva@empire.org>> wrote:

Matteo:

Are you 100% sure the probe has a v6 address or if v6 is working overall? Do you have native v6 or tunneled? Not that it matters, other than the tunnel could be down. I also don't see any v6 tags on your probe's page (ie: v6 Works or Resolves AAAA Correctly).

Here is my probe with v6 working and I've got a v6 tunnel running: https://atlas.ripe.net/probes/10378/

What is your probe's v6 address? Maybe we can all see if it's pingable.

On Wed, Nov 5, 2014 at 10:10 AM, Matteo Bonora <matteo@bonora.eu <mailto:matteo@bonora.eu>> wrote:

Hello,

I have noticed that my probe (#14602) doesn't perform the IPv6 built-in measurements since about 5 months.

The probe has working IPv6 connectivity, so I can't understand where is the problem.

Anyone has an idea about what can I do to solve this?

(below you can see some graphs of my probe's measurements. The brief packet loss on IPv4 was due to a temporary network outage)

Thanks for your help!

Matteo

-- Daniel Baeza Centro de Observación de Red Dpto. Red y Sistemas Television Costa Blanca S.L. Telf. 966.190.847 | Fax. 965.074.390 http://www.tvt.es | http://www.tvt-datos.es Correo: d.baeza@tvt-datos.es -- [Atención] La información contenida en este e-mail es confidencial, privilegiada y está dirigida exclusivamente a su destinatario. Cualquier revisión, difusión, distribución o copiado de este mensaje sin autorización del propietario está prohibido. Si ha recibido este e-mail por error por favor bórrelo y envíe un mensaje al remitente. [Disclaimer] The information contained in this e-mail is privileged and confidential and is intended only for its addressee. Any review, dissemination, distribution or copying of this e-mail is prohibited. If you have received it in error please delete the original message and e-mail us. (!) El medio ambiente es responsabilidad de todos. Imprime este mail si es absolutamente necesario.

Hi Philip, if the problem is internal to the probe, what can we to to solve it? There is a procedure that I can do from my side to "reset" the the probe itself? Maybe is for the same reason that the user-defined v6 measurements don't run on my probe or the system tags aren't shown on the probe's general information page. Thank you Matteo On Thu, Nov 6, 2014 at 3:13 PM, Philip Homburg <philip.homburg@ripe.net> wrote:

Hi Matteo,

On 2014/11/06 12:49 , Matteo Bonora wrote:

...

Yes, I'm sure the probe has a v6 address because it is displayed into the "Network Information" tab and I'm 100% sure that v6 is working because all the devices (computers, smartphones, etc.) connected to the same network are using v6 without problems.

It seems to be problem that is internal to the probe. At this moment, I have no idea what it is exactly. But there is no reason to assume that it has much to do with basic network connectivity.

Philip