INTERNET MEASUREMENT INTERNET MAPPING OVERHEAD MINIMIZATION Intra- and inter-monitor redundancy reduction IBRAHIM ETHEM COSKUN University of Nevada, Reno M.Sc.
Detect ingress points of a target AS Announced IP Subnets (routeviews) Find which ingress point is passed through to reach an IP Subnet in the target AS Directly start probing from ingresses Analyze VPs to efficiently probe a target AS IDEA
traceroute to ( ), 30 hops max, 60 byte packets [AS3851/AS22911] ms ms ms [AS65534] ms ms [AS65534] ms [AS65534] ms ms [AS65534] ms [AS3851/AS22911] ms ms ms [AS3851] ms ms ms [AS2152] ms ms ms [AS2152] ms ms ms [AS2152] ms ms ms [AS2152] ms ms ms [AS4637] ms ms ms [AS55831] ms [AS3786] ms [AS3786] ms [AS3786] ms [AS3786] ms [AS55831] ms [AS3786] ms ms [AS55831] ms [AS3786] ms ms ms [AS9842] ms ms ms [AS9842] ms ms ms [AS9842] ms ms ms [AS9842] ms ms ms IGRESS POINT IDENTIFICATION
Pick 12 ASes Based on: Sizes (#IPs), #Ingresses, #Peers, Ranks 1 small, 1 medium, 1 large Probe these ASes from each VP AS ingress analysis
SIZE (#IPs) SMALL, ASN: 65222, SIZE: 32 SIZE (#IPs) MID, ASN: 1301, SIZE: 9728 SIZE (#IPs) LARGE, ASN: 4134, SIZE: INGRESS SMALL, ASN: 610, #Ingresses: 1 INGRESS MID, ASN: 4366, #Ingresses: 71 INGRESS LARGE, ASN: 701, #Ingresses: 2510 RANK SMALL, ASN: 9989, RANK: 9088 RANK MID, ASN: 9207, RANK: 8714 RANK LARGE, ASN: 3356, RANK: 1 PEER SMALL, ASN: 9253, #Peers: 1 PEER MID, ASN: 8697, #Peers: 34 PEER LARGE, ASN: 174, #Peers: AS ingress analysis
Ingress point analysis VP analysis How to reduce redundant probing?
Pick 2 IPs from each prefix First IP, Last IP /24 Ingress Analysis - Probing Mechanism 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 subnet in two and continue probing each subnet.
Ingress Analysis - Probing Mechanism First IP: Last IP: First IP: Last IP: First IP: Last IP: /24 Divide: /25 || /25 Ingress A Done! Ingress A Ingress B Continue Done! Ingress A Done! Ingress B /25 Ingress B /25 Ingress A
Program probes every subnet that each AS announces Program selects a subnet from the target AS's list randomly and probes first and last IPs of that subnet. If the actual entrance point of the target AS cannot be identified, then the entrance point for the target AS is predicted. Ingress Analysis - Probing Mechanism
Predicted Entrance Routers: 1.If the trace ends before revealing the target AS, and if there are some unresponsive hops: traceroute [( :33456) -> ( :33457)], protocol icmp, algo hopbyhop ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ---> predicted entrance router 10 * * * 11 * * * 12 * * * :33456 Ingress Analysis - Probing Mechanism
If the target AS is revealed, however some number of hops before the target did not respond then the entrance is predicted as the last responsive hop before the target: traceroute [( :33456) -> ( :33457)], protocol icmp, algo hopbyhop ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ----> (ASN X) predicted entrance router 13 * * * 14 * * * 15 * * * ms ms ms --- > (ASN T) Target AS revealed :33456 Ingress Analysis - Probing Mechanism
If the trace ends before revealing the target AS, and if there is no unresponsive hops at the end, then this is considered as "NO_ENTRANCE_INFO": traceroute [( :33456) -> ( :33457)], protocol icmp, algo hopbyhop ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms !H ms !H ms !H :33456 Ingress Analysis - Probing Mechanism
Tried to use 550 Planetlab Nodes 350 of the nodes are usable Got results from only 225 Nodes Utilized from Paris-traceroute Ingress Analysis - Probing Mechanism
Some nodes do not allow users to use ‘sudo’ command through ssh connection Nodes are not consistent SSH connection to nodes was interrupted while getting the results Nodes cannot SSH to our servers in UNR Need to use a server outside the firewall of the UNR Campus PROBLEMS!
VP Node Name: static.oxfr.ma.charter.com Target AS: 174 ENTR: ENTR_AS: ENTR: ENTR_AS: 3356 (Divided Subnet: /30) ENTR: ENTR_AS: Target AS: 3356 ENTR: ENTR_AS: 3561 very small amount ENTR: ENTR_AS: Target AS: 701 ENTR: ENTR_AS: 174 VP Node Name: ampelos.ipv6.lip6.fr Target AS: 3356 ENTR: ENTR_AS: 1273 ENTR: ENTR_AS: PRE_ENTR: ENTR_AS: PRE_ENTR: ENTR_AS: PRE_ENTR: ENTR_AS: 3549 Target AS: 174 ENTR: ENTR_AS: 1273 ENTR: ENTR_AS: 1273 PARTIAL RESULTS
VP Node Name: planetlab1.net.in.tum.de Target AS: 701 ENTR: ENTR_AS: 3356 ENTR: ENTR_AS: 3549 very small amount VP Node Name: planetlab2.informatik.uni-erlangen.de Target AS: 174 ENTR: ENTR_AS: 680 Target AS: 4134 ENTR: ENTR_AS: 3356 ENTR: ENTR_AS: 3356 VP Node Name: static.oxfr.ma.charter.com Target AS: 4134 ENTR: ENTR_AS: ENTR: ENTR_AS: small amount PRE_ENTR: ENTR_AS: 4837 PARTIAL RESULTS
Probe target AS IPs starting from the entrance router of the target AS. -f option of paris-traceroute allows to set the TTL value of the first packet Reduce the redundant probing through target AS START PROBING FROM ENTRANCE ROUTER
Target IP VP 3 VP 2 VP 1 Entrance Point A Entrance Point B AS X AS Y AS T AS R AS Z Directly start probing from entrance points
Ant Census Data Starting in 2003, researchers at ISI have been collecting data about the Internet address space. ~ IP addresses that response to ping Parse the data Which IPs belong to which AS Subnets Get the min hop number of the entrance point from the first probing results Probe the target IP starting from the entrance router hop number START PROBING FROM ENTRANCE ROUTER
Entrance Point Hop number: traceroute [( :33456) -> ( :33457)], protocol icmp, algo hopbyhop ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms ms 11 * ms ms ms ms ms ms ms ms > Entrance IP(AS -X) Hop Number: 13 ms * ms > Target IP(AS -T) START PROBING FROM ENTRANCE ROUTER
VP analysis Target AS Ingress router VP Target AS Other ASes
? QUESTIONS?