Download presentation
Presentation is loading. Please wait.
Published byEustace Kelly Modified over 9 years ago
1
INTERNET MEASUREMENT INTERNET MAPPING OVERHEAD MINIMIZATION Intra- and inter-monitor redundancy reduction IBRAHIM ETHEM COSKUN University of Nevada, Reno M.Sc.
2
Intra –monitor redundancy Occurs when all traceroutes start from a single point Inter –monitor redundancy Occurs when multiple monitors visit the same point INTRA AND INTER –MONITOR REDUNDANCY
3
INTRA –MONITOR REDUNDANCY Monitor 1 Destination 1 Destination 2 Destination 3
4
INTER –MONITOR REDUNDANCY Monitor 1 Monitor 2 Monitor 3 Destination 1
5
PlanetLab currently consists of 1187 nodes at 582 sites AS numbers of 1047 nodes collected 111 nodes not responded Planetlab VPs
8
Archipelago (Ark for short) is CAIDA's next- generation active measurement infrastructure AS numbers of 91 nodes collected Ark VPs
10
RIPE NCC is building the largest Internet measurement network ever made AS numbers of 5373 Nodes collected 2025 different ASes RIPE NCC VPs
13
TOTAL (collected) ASN Information
14
Data downloaded from CAIDA 788.688 AS relation Compared with collected ASes which includes VPs (Ark, Planetlab, RIPE NCC) ASN Neighboring Relations
15
~500 available nodes, ~350 usable Probed 3 hops of each VP 45000 ASes in average Selected 1 IP per AS 394387 ingress points identified Gathered peering relations 74302 identified (One AS to another) Planetlab Vantage Points
16
traceroute to 223.253.8.1 (223.253.8.1), 30 hops max, 60 byte packets 1 134.197.43.254 [AS3851/AS22911] 0.500 ms 0.964 ms 1.205 ms 2 10.252.1.245 [AS65534] 0.203 ms 0.434 ms 10.251.1.245 [AS65534] 0.184 ms 3 10.255.2.250 [AS65534] 0.907 ms 0.890 ms 10.255.1.250 [AS65534] 0.879 ms 4 134.197.0.9 [AS3851/AS22911] 1.118 ms 1.099 ms 1.090 ms 5 207.197.33.69 [AS3851] 1.082 ms 1.471 ms 1.461 ms 6 137.164.23.37 [AS2152] 4.360 ms 4.267 ms 4.261 ms 7 137.164.46.80 [AS2152] 4.289 ms 4.262 ms 4.303 ms 8 137.164.47.22 [AS2152] 6.807 ms 8.088 ms 6.773 ms 9 137.164.47.18 [AS2152] 7.586 ms 7.571 ms 7.562 ms 10 198.32.176.43 [AS4637] 22.041 ms 22.030 ms 22.014 ms 11 1.208.104.201 [AS55831] 22.007 ms 203.255.234.133 [AS3786] 21.561 ms 203.255.234.145 [AS3786] 21.547 ms 12 203.233.37.73 [AS3786] 166.076 ms 203.233.52.33 [AS3786] 165.376 ms 1.208.104.93 [AS55831] 166.261 ms 13 210.120.105.214 [AS3786] 167.341 ms 167.319 ms 1.208.107.218 [AS55831] 167.291 ms 14 211.53.168.214 [AS3786] 163.802 ms 168.335 ms 169.086 ms 15 124.243.3.221 [AS9842] 168.662 ms 168.297 ms 163.744 ms 16 223.253.3.29 [AS9842] 162.751 ms 157.928 ms 157.629 ms 17 223.253.3.6 [AS9842] 173.304 ms 173.295 ms 169.098 ms 18 223.253.8.1 [AS9842] 171.442 ms 177.999 ms 166.311 ms IGRESS POINT IDENTIFICATION
17
#Ingresses - #ASes
18
Pick 12 ASes Based on: Sizes (#IPs), #Observed IPs, #Peers, Ranks 1 small, 1 medium, 1 large Probe these ASes from each VP AS ingress analysis
19
#CONNECTIONS#PEERS 129563 212917 37347 44889 53319 62529 71920 81528 91208 101019 11870 12755 13621 14548 15464 16398 17296 18312 #Peers - #Connections ASN1ASN2#CONNECTIONS 17433561824 12993356803 33563549780 174701627 1743257600 63897018585 33563257539 784310796496 209701466 64534755462 174209460 2914174433 7013549422 354918881399 7018701393 1747922363 3356701361 1741299339 33564323330 2828174328 64534323323
20
#Peers - #Connections
21
223.239.208.0/20 AS45609 BHARTI-MOBILITY-AS-AP Bharti Airtel Ltd. AS for GPRS Service,IN 223.239.240.0/20 AS45609 BHARTI-MOBILITY-AS-AP Bharti Airtel Ltd. AS for GPRS Service,IN 223.248.0.0/16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN 223.249.0.0/16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN 223.250.0.0/16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN 223.251.0.0/16 AS9812 CNNIC-CN-COLNET Oriental Cable Network Co., Ltd.,CN 223.252.160.0/24 AS58779 I4HKLIMITED-AS i4HK Limited,HK 223.252.161.0/24 AS58779 I4HKLIMITED-AS i4HK Limited,HK AS Sizes Data: http://www.cidr-report.org/as2.0/msprefix-list.html
22
#/32: 1 IP address within the subnet #/31: 2 IP addresses within the subnet #/30: 4 IP addresses within the subnet #/29: 8 IP addresses within the subnet #/28: 16 IP addresses within the subnet #/27: 32 IP addresses within the subnet #/26: 64 IP addresses within the subnet #/25: 128 IP addresses within the subnet #/24: 256 IP addresses within the subnet #/23: 512 IP address within the subnet #/22: 1024 IP addresses within the subnet #/21: 2048 IP addresses within the subnet #/20: 4096 IP addresses within the subnet #/19: 8192 IP addresses within the subnet #/18: 16384 IP addresses within the subnet #/17: 32768 IP addresses within the subnet #/16: 65536 IP addresses within the subnet #/15: 131072 IP addresses within the subnet #/14: 262144 IP address within the subnet #/13: 524288 IP addresses within the subnet #/12: 1048576 IP addresses within the subnet #/11: 2097152 IP addresses within the subnet #/10: 4194304 IP addresses within the subnet #/9: 8388608 IP addresses within the subnet #/8: 16777216 IP addresses within the subnet AS Sizes IP prefixes, #IPs
23
Announced Prefixes: …../24 …../16 …../8 /24 /24 /16 /8 /8 How to calculate AS size 256 6553616777216 + ++ + = 33620480 SIZE
24
AS Rank Data: http://as-rank.caida.org/
25
Ingress point analysis VP analysis How to reduce redundant probing?
26
Pick 2 IPs from each prefix First IP, Last IP 1.0.4.0/24 Ingress Analysis - Probing Mechanism 1.0.4.11.0.4.254 Probe these IPs If they enter the AS from the same ingress, then that means all IPs in this /24 subnet belongs to the same ingress. If they reveal different ingress points, then divide the prefix by 2 and continue probing each subnet.
27
Ingress Analysis - Probing Mechanism 1.0.4.0 First IP: 1.0.4.1 Last IP: 1.0.4.254 First IP: 1.0.4.1 Last IP: 1.0.4.126 First IP: 1.0.4.129 Last IP: 1.0.4.254 /24 Divide: 1.0.4.0 /25 || 1.0.4.128 /25 Ingress A Done! Ingress A Ingress B Continue Done! Ingress A Done! Ingress B 1.0.4.0 /25 Ingress B 1.0.4.128 /25 Ingress A
28
Which subnets reached by which ingresses Which VPs enter the target AS through which ingresses How much data we lose from recalling a VP or multiple VPs How many hops VPs traverse to trace these ASes Which VPs would be enough to trace an AS and not to cause redundant probing. Analysis
29
VP analysis Target AS Ingress router VP Target AS Other ASes
30
? QUESTIONS?
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.