November 2022 - ripe-atlas - mailman.ripe.net

Verdien 3.0.3
by Ernst J. Oud 07 Sep '23

07 Sep '23

Hi, @Chris Amin: Yes, commit c999953, version 3.0.3 completely solves this. My gratitude is larger than the losses Mr. Musk is making now that Twitter is going down the drain :-) Thanks! Regards, Ernst J. Oud

5 4

Requesting Credits for Research
by Alex Gamero-Garrido 29 Jul '23

29 Jul '23

Hi folks, 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 Thank you, Alex -- *Alex Gamero-Garrido* *PhD Student, Computer Science* Web: cseweb.ucsd.edu/~agamerog Center for Applied Internet Data Analysis (CAIDA) San Diego Supercomputer Center UC San Diego Pronouns: He/Him/His <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> I'm using Inbox When Ready <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> to protect my focus.

13 15

Probe DHCPv6 support
by Aleksi Pirttimaa 19 May '23

19 May '23

Hi! I recently received my v4 probe and I'm very happy with it. But unfortunately it doesn't support DHCPv6. I present a practical reason for implementing a DHCPv6 client on the probe. You see, my ISP doesn't send router advertisements with the prefix for stateless autoconfiguration set, and instead DHCPv6 must be used. I believe their decision could have something to do with the fact that the regulating body here requires ISP's to prevent IP address spoofing in consumer plans. And to meet that requirement my ISP may be using a feature similar to Cisco's IP source guard, where switch ports and/or mac addresses are passively associated to leased ip's or prefixes, breaking SLAAC. Unfortunately they hate letting consumers talk with their engineers so it's difficult to speculate this further. For now, I've put a stateful firewall appliance in front of the probe which provides SLAAC, it works just fine. Do you think a DHCPv6 client should be implemented?

8 13

Upcoming RIPE Atlas stream release in December
by Chris Amin 16 Dec '22

16 Dec '22

Dear colleagues, In around three weeks we will be releasing a new version of the RIPE Atlas stream (https://atlas-stream.ripe.net) with an API based on WebSockets and plain HTTP requests. The current Socket.IO interface will be maintained for backwards compatibility for the near future, but some subscription parameters will be dropped due to extremely low or no usage. These are: * Historic playback (startTime, endTime) — note that this does not include sendBacklog, which will still work as now * Arbitrary server-side filtering of fields (equalsTo, greaterThan, lessThan) — note that filtering by "prb", "msm", "type" etc will work as now We can see from the service logs that each of these parameters has either not been used at all or used by a single IP address in the past month, so the impact should be minimal. However, if you happen to be using one of these parameters then please get in touch with me. Aside from these changes, existing use cases should continue to work as they do now, and we will be monitoring closely for any issues. There will be more information on the new API, including complete documentation, closer to the time. Kind regards, Chris Amin RIPE NCC

1 1

Unknown probe in my account
by Giuseppe Macario 08 Dec '22

08 Dec '22

Hello everyone, I have a probe that works properly but, a few weeks ago, my account also started to show a probe that doesn't work and that I don't know. I contacted atlas @ripe.net to ask for clarification but I didn't get anything (apart from a semi-automated message). So could anyone delete this unknown probe? https://atlas.ripe.net/probes/63078/ Thank you.

2 4

Shiny new v5 probe reveals problem with virtual probe
by Niall O'Reilly 01 Dec '22

01 Dec '22

Hello, everyone. TL; DR: clue needed configuring Turris Omnia for virtual Atlas probe. I'm delighted to have a shiny new v5 probe, which is operation since the day before yesterday. The new probe has been automatically tagged "IPv6 Works". On account of this, I've noticed that my virtual probe, running on my Turris Omnia, has the complementary tag, "IPv6 Doesn't Work." I suspect that I've not configured firewalling on my Turris properly. If any of you have sorted this, I would appreciate some clue. Thanks in anticipation. Niall

2 2

New V5 Probe with IPv4 Discovery issues
by Nate Weibley 01 Dec '22

01 Dec '22

I received a shiny new V5 probe via post on Saturday and got it up and running yesterday on my dual-stack network. The probe in question is: https://atlas.ripe.net/probes/62490/ It has been operational for about 18 hours and quickly indicated that IPv6 connectivity was functional, but it has only momentarily indicated IPv4 connectivity was established. I can see IPv4 ICMP and UDP traffic originating from the probe passing through my opnsense router on the IPv4 WAN interface so I know IPv4 traffic is flowing. I also see the correct IPv4 DHCP lease info for my LAN on the probe's network status page. Probe address discovery does not show a valid IPv4 connection address or IP Echo Service listed, only the Local IP of my probe. I've tried power cycling the probe but it doesn't seem to impact this issue. Are there any other troubleshooting steps I should try?

2 5

Format change for index pages of RIS MRT data files and RIPE Atlas daily dataset dumps
by Robert Kisteleki 24 Nov '22

24 Nov '22

Dear RIS and RIPE Atlas users, On Wednesday, 30 November 2022 we are planning to migrate the web server at <https://data.ris.ripe.net/> as well as <https://data-store.ripe.net> from Apache httpd to nginx. This will affect how the file listings in HTML index pages are generated, including the following: * RIS MRT data files (updates and dumps) * RIPE Atlas daily dataset dumps If you rely on the format of these pages, you need to update your software. Before we do the upgrade, you could check the new format of the index pages at: https://test-data.ris.ripe.net/rrc00/ We would like to ask you to avoid relying on the specific format of the index.html files. If you are fetching BGP dump files, please use the REST API that is described at: https://ris.ripe.net/docs/40_Prototypes/15_per_rrc_dumps.html You might also consider using per-peer dump files instead: https://ris.ripe.net/docs/40_Prototypes/10_per_peer_dumps.html We want to encourage you to provide your feedback on the API, so that we could improve it and build a similar API for the update files. If you are fetching update files, please use direct URLs to files as described at: https://ris.ripe.net/docs/20_raw_data_mrt.html#name-and-location Kind regards, Oleg Muravskiy, Robert Kisteleki RIPE NCC

1 0

Magellan
by Ernst J. Oud 18 Nov '22

18 Nov '22

L.S. In the meantime I have found that there is a hardcoded 5 minute timeout for streams to end. However, after this timeout the message “Disconnected from stream” appears and the ripe-atlas process appears to “hang”, a ctrl-c appears to be the only option, python then interrupts within threading.py and client.py. What is it doing, what is it waiting for? Any solution? Regards, Ernst J. Oud

2 1

Magellan streaming and ctrl-c behavior
by Ernst J. Oud 15 Nov '22

15 Nov '22

Hi, If I use the older Docker container for the ripe atlas CLI tools (Magellan) (at https://hub.docker.com/r/anuragbhatia/ripe-atlas-tools) a newly created measurement streams its results and then Magellan exits and the container exits. Since the aforementioned image is old and displays results wrongly using erroneous Unicode conversion, which was solved in later Magellan versions, I created a new image using the latest Magellan code. Now all is well except that after results have been streamed, Magellan waits for ctrl-c. This is as per the Magellan docs of the stream command, but very annoying. I planned to automate things, sending a ctrl-c keystroke is not easy in this case. I don’t know whether the older Magellan code did not wait for ctrl-c or whether the creator of the older Docker image changed the code somewhere. It would be an idea to add an option to the the Magellan measure command whether to stop after streaming or to stop after a certain amount of results are in, like the “—limit” command for the stream command which unfortunately is not an option of the measurement command. I think the only option is to create a measurement with the —no-report option, get the measurement-ID from the URL and then use the report command, instead of streaming. Any ideas? Met vriendelijke groet / Regards, Ernst J. Oud

1 0