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] Inconsistent system tags
- Previous message (by thread): [atlas] Making public probes’ IP addresses public in web interface
- Next message (by thread): [atlas] Inconsistent system tags
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Johannes Matheis
jomat+ripeatlasml at jmt.gr
Fri Sep 30 14:18:27 CEST 2016
Hello, I got IPv6 connectivity for my probe 4365 a few days ago (2016-09-26) when I first noticed the system tag "IPv6 Doesn't Work". As the system tags aren't updated more often than every four hours I started some successful IPv6 measurements on that probe and settled back for four days. Now the probe is still flagged as IPv6 not working. In the meantime I noticed the tag "v2" but the general information tab tells me the system architecture is probev1… Actually I don't know if it's a v1 or v2, but it's still an old Lantronix one, so it's not completely wrong :-) Is there a possibility to re-trigger the assignment of the system tags for this probe or some other solution? Thanks! jomat
- Previous message (by thread): [atlas] Making public probes’ IP addresses public in web interface
- Next message (by thread): [atlas] Inconsistent system tags
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]