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/ripe-atlas@ripe.net/
[atlas] Problem with new Openipmap
- Previous message (by thread): [atlas] Problem with new Openipmap
- Next message (by thread): [atlas] Problem with new Openipmap
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel AJ Sokolov
listclient at sokolov.eu.org
Tue Dec 5 23:13:49 CET 2017
He makes good points. I think there should be at 100 traces, not just 10. That's just to small a sample. BR Daniel AJ On 5 December 2017 14:01:20 GMT-08:00, Klaus Darilion <klaus.mailinglists at pernau.at> wrote: >Hi! > >I just noticed the new interface of Openipmap. Nice, but unfortunately >not as useful as the old one: > >1. clicking on the graph does not show the trace >2. it does not show 50 traces as the last one (I need plenty of >traceroutes for network optimization, not only 10) >3. there should be a possibillity to mark a location as wrong. > >E.g. see https://atlas.ripe.net/measurements/10418213/#!openipmap > >Openipmap display Warsaw as target where all this traces terminate in >New York as this IP address is an Anycast IP address and therefore it >must no be mapped to a single location. > >hence, for Anycast IPs there should be feature to mark the IP as >Anycast. Then the final target is usually the location of the IP >address >before. > >regards >Klaus Sent from mobile phone. Please excuse my brevity.
- Previous message (by thread): [atlas] Problem with new Openipmap
- Next message (by thread): [atlas] Problem with new Openipmap
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]