ripe atlas

38
RIPE Atlas Serge Radovcic RIPE NCC [email protected]

Upload: ripe-ncc

Post on 30-May-2015

803 views

Category:

Career


0 download

DESCRIPTION

Presentation given by Serge Radovicic in Apricot 2012

TRANSCRIPT

Page 2: RIPE Atlas

2

IntroductionRIPE Atlas:• So what is an Atlas? = a collection of Maps!• That’s why we called it Atlas, RIPE Atlas• A next generation Internet measurement network

- To scale to thousands of measurement nodes- Potentially “be everywhere” and ready to run different measurements for YOU

- We started in Nov 2010, and we are still building it and continually exploring the possibilities of it

2

Page 3: RIPE Atlas

3

Light Map of Europe (thanks to NASA)

3

Page 4: RIPE Atlas

4

IntroductionSo how many probes do we need?• To gauge the sort of network that we would need!

- We took a look at all the IP prefixes that RIPE NCC has allocated and then geolocated them

- We then created a script to randomly plot some dots on a map of those IP prefixes

- We randomly colored those dots from green to red- With an emphasis on highlighting one IP prefix- And we got the following results........

Page 5: RIPE Atlas

5

Intuition: 1000 Probes

Page 6: RIPE Atlas

6

Intuition: 5000 Probes

Page 7: RIPE Atlas

7

Intuition: 10k Probes

Page 8: RIPE Atlas

8

Intuition: 20k Probes

Page 9: RIPE Atlas

9

Intuition: 50k Probes

Page 10: RIPE Atlas

10

Intuition: 10k Probes & 1 AS

Page 11: RIPE Atlas

11

Ambitious Community Effort

Instead of building small, separate, individual & private infrastructures, why not build a huge common

infrastructure that serves both the private goals

and the community goals.

Page 12: RIPE Atlas

12

Ambitious Community Effort

• Individual Benefits- Less expensive than rolling your own- More vantage points available- More data available

• Community Benefits- Unprecedented situational awareness- Wealth of data, …

Page 13: RIPE Atlas

13

Why not deploy a SW version?• Many of the host machines will not run

continuously (24/7) over long periods

• The measurements would be influenced by sharing systems and network resources with other applications on the host computer

• Software can cause host machines to crash

• SW may be easier to tamper with

Page 14: RIPE Atlas

14

Intuition -> Plan• For accurate maps we need lots of probes• Deploying very many TTM boxes is too expensive• Smaller probes • Easily deployable• USB powered• 24 x 365 capable

Page 15: RIPE Atlas

15

Probe Deployments

Page 16: RIPE Atlas

16

RIPE Atlas - Overall Architecture

Page 17: RIPE Atlas

17

RIPE Atlas - Security aspects• Probes have hardwired trust material

(registration server addresses / keys)• The probes don’t have any open ports, they only

initiate connections- This works fine with NATs too

• Probes don’t listen to local traffic, there are no passive measurements running- There’s no snooping around

• And if in doubt, you can always just pull the plug!

Page 18: RIPE Atlas

18

Network extent

updated hourly on

Today, about 1,300

probes “Up”

Page 19: RIPE Atlas

19

Network extent - Global - Feb 2011

Page 20: RIPE Atlas

20

Network extent - Europe - Feb 2011

Page 21: RIPE Atlas

21

Network extent - Europe - Feb 2012

Page 22: RIPE Atlas

22

Network extent - Around India

Page 23: RIPE Atlas

23

So what do they currently measure?• Built in probe measurements to all root servers:

- Shows which root DNS server instance the probe ends up querying

- Shows the response time to all root server instances and one can compare their performance

• RTT to specific targets

Page 24: RIPE Atlas

Speed of connections to ns.ripe.net

24

ns.ripe.net (Amsterdam)

Page 25: RIPE Atlas

Speed of connections to ns.ripe.net

25

Page 26: RIPE Atlas

K-root instance query comparison (Berlin, DE)

26

Page 27: RIPE Atlas

Root server response comparison

27

Page 28: RIPE Atlas

28

User Defined Measurement (UDM)- Let’s you, the host, take control

- You define your measurements and we role them out for you

- You don’t just measure from your probe, but potentially, any of the probes on the infrastructure

- Yes, any of the thousands of probes spread all across the globe - and we store all these measurements in our DB!

Page 29: RIPE Atlas

• Currently:– Ping (v4/v6)– Traceroute (v4/v6)

• Upcoming:– DNS query

UDM (beta): Type of Measurement

29

Page 30: RIPE Atlas

UDM (beta): Choosing the “Origin” • Currently:

– Worldwide– Region– Country– Probe

• Upcoming:– AS– Prefix

30

Page 31: RIPE Atlas

UDM (beta): and more...... – Target– Start– End– # Probes– more...

31

Page 32: RIPE Atlas

UDM (beta): Visualisation

32

Page 33: RIPE Atlas

33

So what do you see?RTT per probe

Packet loss per probe

Page 34: RIPE Atlas

34

Hosting = Credits = Measurements

Page 35: RIPE Atlas

35

Sponsorship = Credits = Measurements

Page 36: RIPE Atlas

36

Sponsorship = Credits = Measurements

Page 37: RIPE Atlas

37

So what’s next?- More features, more measurements, more UDM capabilities and refining the credit system

- The current plan is to give all our members access to the UDMs whether they are hosts or not

- More probes hosts

- More sponsors

- And me getting off the stage!!

Page 38: RIPE Atlas

Questions?