multipath detection with ripe atlas
play

Multipath Detection with RIPE Atlas Stephen Strowes - PowerPoint PPT Presentation

Multipath Detection with RIPE Atlas Stephen Strowes <sds@ripe.net> | March 14th, 2018 | AIMS 2018 a.k.a. cant we just use RIPE Atlas for this? Stephen Strowes <sds@ripe.net> | March 14th, 2018 | AIMS 2018


  1. Multipath Detection with RIPE Atlas Stephen Strowes <sds@ripe.net> | March 14th, 2018 | AIMS 2018

  2. a.k.a. can’t we just use RIPE Atlas for this? Stephen Strowes <sds@ripe.net> | March 14th, 2018 | AIMS 2018

  3. 
 
 
 
 
 
 
 Paris Traceroute on Atlas • API docs: 
 • default: 16 Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 3

  4. Paris Traceroute on Atlas • Atlas can cycle through [0 .. 64] distinct flow IDs • Modifies: - destination port field in UDP - checksum field in ICMP • Of course a measurement can define an address family (4/6) and transport (ICMP, UDP, TCP) Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 4

  5. Regardless… • Multipath observations on Atlas? • Rough comparison: - Choosing targets to match Kevin’s measurements - Using an Atlas probe within a matching ASN as above - What do we see? Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 5

  6. Apples to Apples part I • From: probe 6278 • To: 125.155.82.17 • Full cycle of flow IDs • UDP transport Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 6

  7. probe 6278 -> 31.13.64.6 • UDP: 91 IPs in path observed, 165 edges - ~80% of the IPs without being smart - ~20-25% of edges • No alias resolution etc • 4600 traceroute probes sent • [ICMP sees fewer of the above] Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 7

  8. Apples to Apples part II • From: probe 6278 • To: 31.13.64.6 • Full cycle of flow IDs • UDP transport Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 8

  9. probe 6278 -> 125.155.82.17 • UDP: 87 IPs in path observed, 147 edges - ~72% of the IPs - ~20% of the edges • 2900 traceroute probes sent • [ICMP sees a straight line] Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 9

  10. Shortcomings • Current implementation is slow to iterate • Can iterate measurements to get pretty far with the Atlas API, but it’s a lot of work • We cycle through a small set of flow IDs, with no configuration for other fields to modify Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 10

  11. Shortcomings • No smarts built-in to avoid repeatedly measuring hops with only one link • You can throw away your statistical guarantees • Finally, 70% of Atlas platform is behind a NAT Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 11

  12. Ongoing • Investigating more structured approaches to performing multipath detection with Atlas • Expand the set of paris IDs available • … up to a smarter MDA measurement type? Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 12

  13. Q Stephen Strowes <sds@ripe.net> | AIMS 2018 | March 14th 2018 13

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend