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] packet loss seen by probes to labs.ripe.net?
- Previous message (by thread): [atlas] packet loss seen by probes to labs.ripe.net?
- Next message (by thread): [atlas] packet loss seen by probes to labs.ripe.net?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Thu Nov 3 11:19:26 CET 2011
Robert Kisteleki wrote: [...] > I'll try to confirm this with people who know more about the Labs > architecture. But if I'm right (I think I am), then Atlas is measuring > precisely what it should... and as a by-product, also its own growth :-) Hi Robert, nice line of thought :-) Actually, from a purely technical point of view, I agree with your interpretation. >From a probe-herder's point of view, this behaviour sent me on a bounty hunt on our end, to find out why there is packet loss between our office network and the labs site :-) > Regards, > Robert I think both ends did learn a little by this :-) Wilfried. PS: please do not take away the Labs (or another dedicated for ATLAS) target "at the NCC", I consider that a nice reference point for connectivity
- Previous message (by thread): [atlas] packet loss seen by probes to labs.ripe.net?
- Next message (by thread): [atlas] packet loss seen by probes to labs.ripe.net?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]