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] Error: Only anchors may be targeted.
- Previous message (by thread): [atlas] Error: Only anchors may be targeted.
- Next message (by thread): [atlas] More probes with incorrect location
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vesna Manojlovic
BECHA at ripe.net
Thu Jun 28 16:11:57 CEST 2018
Hi all, On 25/06/2018 15:32, Stephane Bortzmeyer wrote: > On Mon, Jun 25, 2018 at 03:10:07PM +0200, > Guido Iaquinti <guido.iaquinti at gmail.com> wrote > a message of 16 lines which said: > >> I was discussing the above with a few friends and I understand that >> there might be some security related concerns but I think with a >> proper user policy and technical implementation they could be easily mitigated: > > It is not purely technical. There is also an ethics problem as well > <https://labs.ripe.net/Members/kistel/ethics-of-ripe-atlas-measurements> > Basically, in places where you can have trouble for your Internet > activity, HTTP is often actually monitored (which is not the case with > ICMP and DNS). Thanks Stephane! In addition to this , we have come up with a workaround: https://labs.ripe.net/Members/wilhelm/measuring-your-web-server-reachability-with-tcp-ping Please take a look, and see if this is useful for some of the items on your "wish list". Vesna
- Previous message (by thread): [atlas] Error: Only anchors may be targeted.
- Next message (by thread): [atlas] More probes with incorrect location
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]