Re: [atlas] Request RIPE Atlas Credit for Research

[Nick Hilliard]

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 RIPE Atlas. I have 
some credits but still need 50M more credits to carry out my study. 
unfortunately, time constraints prevent me from earning them myself.


Therefore, I am reaching out here to ask for assistance. Is there 
anyone generous enough to offer me some RIPE Atlas credits (like, 1 
million?) My account at RIPE NCC is hf...@mails.tsinghua.edu.cn.


Many thanks in advance!
Regards,
Fengyan Han




-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

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

[Nick Hilliard]

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 ?)


* No user/account should be allowed to run more than Y SW probes from 
the same IPv4/24 IPv6/48 (Y=5 ?)


* Regardless of the user/account, no more than Z SW probes should be 
allowed from the same IPv4/24 IPv6/48 (Z=10 ?)


X, Y and Z are defaults, can be changed per account. This is done in 
order to facilitate corner cases and overstepping the limits, if this is 
warranted (given a good explanation). We are also reaching out to the 
current "peak users" to understand their use cases and motivations - the 
above limits can be enforced depending on the responses.


This looks reasonable. Particularly reaching out to try to understand 
why the individuals in question are doing this. It would be interesting 
to check for any unusual probe activity which used these credits.


Nick


--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Credits Request

[Nick Hilliard]

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 credits would 
be perfect to get started on my experiments.


just transferred 10m - just drop an email to the atlas community if you 
need any more.  And we'd love to see any outcomes!


Nick


--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] RIPE measurement Credits required

[Nick Hilliard]

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 am working on. Would anybody be able to 
kindly send me some RIPE credits which I will hopefully pay back once I 
have the anchor up and running ?


just sent you 50m.

Nick

Re: [atlas] IPv6-renew

[Nick Hilliard (INEX)]

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 on the path between the provisioning 
system issuing the prefix and the end device. So in this sense it is a 
protocol issue, albeit an issue that was outside the design scope of the 
protocol.



Imagine if the mobile operator swapped your mobile phone number midstream.


mobile phone numbers are stateful. You don't need to change phone number 
every time you're handed off to a different cell.


Nick

Re: [atlas] IPv6-renew

[Nick Hilliard (INEX)]

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

[Nick Hilliard (INEX)]

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 totally lost
its config and wants DHCP now, which there isn't in this network,
or it just died)...

So knowing whether this is a more widespread issue and possible reasons
would help me to decide how much effort to invest in debugging this.


as you mention it, one of my v1 probes died on sunday:


Your probe 127 has been disconnected from the RIPE Atlas infrastructure since 
2020-05-31 21:55:58 UTC.


Did this coincide with a software update or something on the control side?

Nick

Re: [atlas] Requesting Credits for Research

[Nick Hilliard (INEX)]

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 any partial amount that gets 
us closer to that goal is welcome and greatly appreciated. My account 
is agamerog at eng.ucsd.edu 


ooh, CAIDA.  My favourite!  Just sent 100m.

Nick

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

[Nick Hilliard (INEX)]

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

[Nick Hilliard (INEX)]

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.  Lemme know if you need more.

Nick

Re: [atlas] Fwd: credit request

[Nick Hilliard (INEX)]

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 changed my 
subscription and am re-sending that email.  I apologize in advance if 
the moderator releases the original mail and you see a duplicate.  — 
Michael)



Begin forwarded message:

*From: *Michael Rabinovich >

*Subject: **credit request*
*Date: *March 21, 2019 at 2:45:45 PM EDT
*To: *ripe-atlas@ripe.net 

Folks,

I teach computer science at Case Western Reserve University.  I have a 
group of students working on a research project to characterize 
certain aspects of DNS and HTTP interactions on the Web.  To get a 
representative measurement, we need to resolve hostnames from top-1M 
websites from a large number of widely dispersed probes.  So we need a 
large amount of credits and I was wondering if I could ask folks for 
help.  My back of the envelop calculations suggest we are short of 
~200M credits.   I realize it’s a large amount, but we would take any 
help we can get and will conduct as credible measurement as we can 
with the credits we assemble!  Please note that my RIPE Atlas account 
is associated with mail alias mi...@case.edu 
 (not the default email address I am sending 
from), so please use “mi...@case.edu ” for 
credit transfer if you can help.


Many thanks in advance!
Regards,
Michael Rabinovich

Re: [atlas] Request RIPE Atlas Credit for Research

[Nick Hilliard (INEX)]

陆超逸 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 them by myself.

So I'm here to ask for help. Is it possible for anyone generous
enough to offer me some RIPE Atlas credits (like, a million)?
My account at RIPE NCC is lc...@mails.tsinghua.edu.cn


sure - just sent you 10m.

Nick

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

[Nick Hilliard]

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 problem is, inet_aton() interprets leading zeros as octal, and on
any operating system which uses the bsd socket library, the address may
get converted into octal, or may not, depending on whether the program
is using inet_aton(), which assumes octal if there are leading zeros, or
getaddrinfo(), which will interpret as decimal in all cases, because
POSIX was a bit more careful about the definition.

In other words, you have no idea a priori what someone else's code will
do, so unless you're ok about your output being interpreted as random
garbage, you should avoid zero-padding at all costs.

Nick

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

[Nick Hilliard]

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

[Nick Hilliard]

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 falls into this category.

There are no real technical reasons left for not supporting ipv6, only
policy reasons.

Nick

Re: [atlas] LLDP Support for RIPE Probes

[Nick Hilliard]

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 December 2015, Max Gebert > > wrote:
>>
>> Hey!
>>
>> I could definitely see the appeal of such a function in our network. 
>> +1 from me! 
>>
>> Best regards/ Hälsningar
>> Max Gebert
>>
>> 22 dec 2015 kl. 18:23 skrev Chris Elliott :
>>
>>> +1
>>>
>>> On Tuesday, December 22, 2015, Annika Wickert
>>>  wrote:
>>>
>>> Hi everybody,
>>>
>>> I would like to see LLDP support in the future on the RIPE probes.
>>>
>>> It would be a really helpful feature, to see on what Port the
>>> RIPE Probe resides at the moment.
>>>
>>> Cheers,
>>> Annika
>>>
>>>
>>>
>>> -- 
>>> Chris Elliott
>>> CCIE # 2013
>>>
>>> “You and I are mirages that perceive themselves”
>>> --Douglas Hofstadter
>>>
> 

Re: [atlas] Spoofing measurenments

[Nick Hilliard]

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)

[Nick Hilliard]

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