I can add that with a tcpdump on the gateway I can see incoming and outgoing v6 traffic to/from the probe. The host that I can see regularly communicate with my probe is ctr-ams13.atlas.ripe.net. Matteo On Thu, Nov 6, 2014 at 1:49 PM, Matteo Bonora <matteo@bonora.eu> 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.
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
