Re: [atlas] Request RIPE Atlas Credit for Research

no problem, just sent 50m.  Hope your research goes well. Nick Rolland wrote on 18/04/2024 16:51: Hi all, I am sorry to spam this email. My name is Fengyan Han, a master's student at Tsinghua University, China. Recently, my research on RPKI requires conducting a large-scale measurement via

Re: [atlas] Possible software probe "farming" on AS47583

Robert Kisteleki wrote on 20/02/2024 15:43: Since the potential pool of software probes is almost infinite, in response to the highlighted case, we'd like to propose the following mid-term approach: * No user/account should be allowed to run more than X SW probes from the same IP (X=3 ?) *

Re: [atlas] Credits Request

Martin, Noah S wrote on 28/06/2022 19:42: I’m a new PhD student at Tufts University in Boston, and I'm starting to work on a cloud latency project. If anyone has credits to spare, donations would be greatly appreciated! My account is noah.mar...@tufts.edu  100k

Re: [atlas] RIPE measurement Credits required

Mccherry, Paul (Student) wrote on 27/10/2021 21:02: I have applied and been granted to install an Anchor at my University to generate credits to make measurements, this is taking some time to prepare the equipment etc.  In the meantime I need to carry out some measurement tests for a paper I

Re: [atlas] IPv6-renew

Ole Troan wrote on 21/06/2021 11:11: To be correct; it's an operational issue. SLAAC works as designed with IPv6 renumbering. slaac - being stateless 'n all - was not designed with flash renumbering in mind because flash renumbering needs some degree of state synchronisation on all devices

Re: [atlas] IPv6-renew

Marco Davids (IETF) via ripe-atlas wrote on 21/06/2021 07:20: Is this a flaw, or is it by design? this is a known protocol issue with slaac. There's some discussion about it in rfc8978 and draft-ietf-6man-slaac-renum. Nick

Re: [atlas] dead v1 probe

Gert Doering wrote on 02/06/2020 19:28: have there been software updates for v1 probes recently? I've heard about a few v1 probes that have died "just last week" - mine among them (#461), fell off the net with "Firewall Problems Suspected", but it's no longer even ARPing properly (= either it

Re: [atlas] Requesting Credits for Research

Alex Gamero-Garrido wrote on 11/03/2020 09:02: My name is Alexander Gamero-Garrido and I'm a 5th year PhD student at CAIDA, UC San Diego. We're soon launching a large traceroute campaign for research and could use your generous donation of credits. We'll need about 150 million credits, but

Re: [atlas] Probes were incorrectly not tagged with the stability tags

Chris Amin wrote on 21/02/2020 12:43: Just for clarity, we do not yet tag probes as being stable over IPv5. best to be prepared all the same. Nick

Re: [atlas] Looking for RIPE Atlas credits

Nils Rodday wrote on 25/10/2019 08:26: Dear RIPE Atlas users, I am a PhD-student and would need RIPE Atlas credits in order to perform large-scale traceroute experiments. If you have credits to share, I would appreciate it. Recipient: nils.rod...@unibw.de Hi Nils, just transferred 50m.

Re: [atlas] Fwd: credit request

Sure - just transferred 200m. Enjoy! Nick Michael Rabinovich wrote on 21/03/2019 20:30: (I previously subscribed to this list using the same mail alias as used for my RIPE Atlas account, and the mail below was held up for moderation since it came from  a non-matching email address.  I now

Re: [atlas] Request RIPE Atlas Credit for Research

陆超逸 wrote on 06/03/2019 11:41: Greetings! I'm a PhD student at Tsinghua University, China. Recently a large-scale measurement via RIPE Atlas is needed for my research. However, as a new user I don't have any credit to proceed, and unfortunately the time doesn't allow me to earn

Re: [atlas] IPv4 leading zeroes and weird interface behaviour

Max Grobecker wrote: > Now I'm puzzled: Of course, writing IPv4 octets with leading zeroes is not > very common. > But: Is it officially prohibited or discouraged? It was never defined in the rfcs, but by rfc convention, leading zeros should probably be interpreted as decimal (e.g. rfc790). The

Re: [atlas] New on RIPE Labs: The Next Generation of RIPE Atlas Anchors

Jean-Michel Pouré wrote: > You should go with the APU2. do PC engines provide a rack-mounting kit for their enclosures? Nick

Re: [atlas] IPv4-only Anchors Now Supported

Peter Koch wrote: > the article says "However, we will only support IPv4-only anchors hosted > in ASNs that cannot announce IPv6 for technical reasons.". > Could the NCC share examples (respectfully anonymized) of such > _technical_ (as opposed to "technical") reasons? anything in Iran probably

Re: [atlas] LLDP Support for RIPE Probes

yes. YES! Nick Daniel Suchy wrote: > +1 > > On 22.12.2015 22:31, Rickard Östman wrote: >> awesome idea. >> >> another useful feature would be to let the probe share via the atlas >> portal what device and port it's connected to. To the owner alone, that is. >> >> /Rickard >> >> On Tuesday, 22

Re: [atlas] Spoofing measurenments

On 23/11/2015 12:03, Daniel Karrenberg wrote: > Why exactly do we need to know the exact amount of this problem? it would be useful to know the sources of the problem. Nick

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)

On 10/11/2015 13:01, Colin Johnston wrote: > A well managed vm this is the key point. the ripe atlas people have no control over the hypervisor management, which is important from a measurement point of view. Nick