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] Proble locations (Changed because of Geo-IP)
- Previous message (by thread): [atlas] New on RIPE Labs: Stopping Support for Internet Explorer 8 on Windows XP in RIPE Atlas and RIPEstat
- Next message (by thread): [atlas] Proble locations (Changed because of Geo-IP)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Martin Winter
mwinter at noaccess.com
Wed Feb 25 08:28:37 CET 2015
So I've noticed that (at least some) probes got the location automatically updated based on Geo IP. However, this is frequently fundamentially broken. One of my probe moved from San Jose, CA to somewhere in the middle of Texas. (Broken Geo-IP location for AT&T DSL users). (The example I talk about is proble #10770) Kind of sad... not sure how many had this happening. Specially as I took care to put the exact lat/lon in the User interface in the past. Now I can only reposition it by dragging on a map - and that seems to be broken as well (at least it fails to save when I try to correct this probes location on Chrome) I wonder how many and why there was a decision to change the location. I think the location were much better before they got force-changed. - Martin Winter
- Previous message (by thread): [atlas] New on RIPE Labs: Stopping Support for Internet Explorer 8 on Windows XP in RIPE Atlas and RIPEstat
- Next message (by thread): [atlas] Proble locations (Changed because of Geo-IP)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]