Based in Western Europe, NL&DE mostly
Articles
Likes on articles
>>>>>>>>>>>> https://www.ripe.net/about-us/press-centre/publications/speakers/daniel-karrenberg <<<<<<<<<<<< Ample information about his past sins can be found using your favourite search engine. Following are a few additional keywords you might use, arranged by decade: 1980s: GUUG EUUG EUnet unido mcvax cwi RARE iepg RIPE; 1990s: RIPE+NCC rir iana postel terena ebone centr k.root-servers.net; 2000s: dnsmon nsd ris internet+society rssac; 2010s: ripe+labs ripestat ripe+atlas
• 6 min read
RIPE Atlas can now test packet flows from more than 1000 vantage points on the Internet. We took a quick look at anycast traffic to DNS root name servers. There is a lot of interesting signal in this data.
• 4 min read
RIPE Atlas provides a view of 128.0.0.0/16 from the data plane. Can packets actually get there and back? Please find the results in this article.
• 8 min read
RIPE Atlas has made steady progress in its first year. But we have more ambitious plans. Please read below how we are suggesting to achieve them and why we need your support.
• 4 min read
According to address policy, the experimental address allocations for RIPE RIS beacons have to be returned soon. This would mean we have to either discontinue the RIS beacons or request permanent allocations for them according to address policy. We are asking for community support to continue opera…
• 6 min read
As part of our effort to make an evolution plan for the RIPE Test Traffic Measurement service, we conducted a survey among TTM hosts. Find below the results and suggested next steps.
• 3 min read
The RIPE NCC is working on a toolbox, called RIPEstat, that will make it easier to access the various datasets maintained by the RIPE NCC. This toolbox will be developed in close cooperation with the community. There will be public demo sessions as described in this article.
• 3 min read
RIPE Atlas probes are now active on five continents. After the big run on the measurement probes during the recent RIPE Meeting, the deployment is a little slower than expected; but there is a steady stream of probes coming online. We expect to make our initial goal of 300 active probes well before…
• 8 min read
This is the next in a series of articles about the new active measurements network, which now has a name: "RIPE Atlas". In this article I will describe the current planning for the pilot. This is also a call for sponsors which will be needed to make the measurement network really big.
• 8 min read
Why YOU may want to host a small probe to help with large scale active Internet measurements.
• 8 min read
After a short service outage, I was interested to find out what happened. Please find below a case study for using public RIPE NCC Tools for this purpose.
They are suggestions, so do not take them as instructions! Especially the defaults I suggested should be subject to discussion and community feedback. As to keeping the probes visible: I do not think that this is what the typical user wants when they are interested in the topology close to the *target*. In any case what I was interested in when I used traceroutes like that was a simple representation of the topology close to the target, never mind how the packets got close. Daniel
Suggestions: a) add an option to limit to h hops from the target and then show paths from all probes providing data during the interval b) use 'network names' as a label option c) use AS 'names' as a label option d) use a colour scale (better visual resolution than greyscale) for the number of paths along an edge e) add an option to only show endgs used by at least p % of all probes providing data during the interval f) make h=4 and p=25 the default view For examples of all that see https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor Daniel
Showing 22 comment(s)