Hi, This spring RIPE Atlas update [1] introduced a new feature called probe sharing. Probe sharing should work for colleagues within the same LIR and is to be set via: "My Probes" -> "Probe's Settings" -> "General Configuration" -> Select your LIR in the "Share with" field. I've set the "Share with" field to our LIR ID for all three local probes. But a colleague of mine, in spite of being able to login to the Lirportal, sees an error message below every time he tries to access the probe list at https://atlas.ripe.net/atlas/myprobes.html The error message: "You are not logged in as a RIPE NCC member". Is there anything I've missed? Possible delay in privilege propagation from the Lirportal to Atlas section? Thanks. Martin [1] https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013
Hi, This function should work in general; in order for us to look into the specifics please drop us a mail with details (probe id, your and your colleague's account/email) to atlas@ripe.net Thank you, Robert On 2013.08.08. 11:54, Martin Stanislav wrote:
Hi,
This spring RIPE Atlas update [1] introduced a new feature called probe sharing. Probe sharing should work for colleagues within the same LIR and is to be set via: "My Probes" -> "Probe's Settings" -> "General Configuration" -> Select your LIR in the "Share with" field.
I've set the "Share with" field to our LIR ID for all three local probes. But a colleague of mine, in spite of being able to login to the Lirportal, sees an error message below every time he tries to access the probe list at https://atlas.ripe.net/atlas/myprobes.html
The error message: "You are not logged in as a RIPE NCC member".
Is there anything I've missed? Possible delay in privilege propagation from the Lirportal to Atlas section?
Thanks.
Martin
[1] https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013
On 8 Aug 2013, at 11:13, Robert Kisteleki <robert@ripe.net> wrote:
This function should work in general; in order for us to look into the specifics please drop us a mail with details (probe id, your and your colleague's account/email) to atlas@ripe.net
Is this feature going to be spread wider than just LIRs ? ie to the non-RIPE regions and non-NCC networks in the RIPE region ? f
On 2013.08.08. 16:39, Fearghas McKay wrote:
On 8 Aug 2013, at 11:13, Robert Kisteleki <robert@ripe.net> wrote:
This function should work in general; in order for us to look into the specifics please drop us a mail with details (probe id, your and your colleague's account/email) to atlas@ripe.net
Is this feature going to be spread wider than just LIRs ? ie to the non-RIPE regions and non-NCC networks in the RIPE region ?
f
Hi, There's a feature on the "requested" list (see roadmap.ripe.net) about sharing the probe with ad-hoc groups. Its priority, of course, depends on how many people ask for this and how loudly, in relation to other requests :-) Cheers, Robert
Hi, On 8.8.2013 18:04, Robert Kisteleki wrote:
There's a feature on the "requested" list (see roadmap.ripe.net) about sharing the probe with ad-hoc groups. Its priority, of course, depends on how many people ask for this and how loudly, in relation to other requests :-)
Ok, here's one more request to add to that queue :-) A few days ago I installed a probe at a server facility, and would like to share all the data that is visible to me for that probe with other people present on the same network/facility. Relate to the above, is there an http link I can share that would directly lead to a certain (public) probe's measurement results/graph page? Without requiring logging in? I see there's the API system that can be used to fetch at least raw data, but can it supply rendered graphs? Also I'm having a bit of trouble getting the probe to use a statically configured IP address, when there is DHCP also available in the same network. Is this by design, by chance or is something wrong? The statically configured data should be ok, but "my probe" page says the probe is not using it. For IPv6 I'd like to be able to manually specify the address to use, but use the RAs to determine gateways. Tapio
participants (4)
-
Fearghas McKay -
Martin Stanislav -
Robert Kisteleki -
Tapio Sokura